Release Notes
Fluid Flux has received numerous updates, all provided free of charge to existing users.
| Version | Highlights |
|---|---|
| Fluid Flux 3.0 | Underwater glass and lights |
| Fluid Flux 2.0 | Coastline and wave break effects |
| Fluid Flux 1.1 | Performance and usability improvements |
Before installing a new version, follow the Updating process.
Planned updates
You can keep track of the current progress of improvements on Trello. Numerous updates are planned, but I don’t have a specific timeframe. It’s essential to base your purchasing decisions on the product demonstrated in the demo rather than relying solely on my promises.
Please note that I don’t sell promises, future versions, free time, or lifetime updates. I also don’t work for marketplace customers. I sell the products ‘as is,’ and customers should base their decision on the product’s current state (demo and feature set), not on future expectations or unreleased features.
Every update is an additional effort driven by my passion for creating. Being obligated to complete something by a specific deadline can cause stress, and I prefer to avoid it.
C++ Plugin
A new C++ version, called the Fluid Flux Plugin, is currently being developed. Its release is planned for mid-2027. For now, I can only present a short list of differences in the first release of the Plugin:
- Improved usability, enhanced editor tools, and better integration with Unreal Engine UI
- Simulation domain implemented in Niagara and a new spline modifier
- Whole blueprint code rewritten to C++ (GitHub access)
- Improved performance (mainly CPU-related)
- Better sequencer support
The Fluid Flux Plugin will primarily target larger studios and experienced developers and will be released as a separate product on Fab. While it’s not exclusive, modifying the C++ version will require programming skills and extra work to transfer existing projects, which I did not want to impose on current Fluid Flux users.
Many developers ask about the future of the Blueprint version. The good news is that a new programmer has joined to work on C++, so I can still focus on updating the Blueprint version. I plan to continue adding new features and enhancing tools as long as possible.
However, I cannot tell how long I can support two different product branches. I will evaluate the situation one year after the Plugin release. A possible scenario is that I will switch focus to the C++ version and only provide minor improvements and engine-related updates to the blueprints. However, my final decision depends on many factors, such as:
- Interest in the Plugin compared to the Blueprint version. If most users decide to switch to the plugin, there is no reason to continue development.
- Whether the Blueprint version can still evolve – blueprint limitations block many features, and at some point, adding another workaround may be too problematic.
- The complexity of transferring asset-related changes between the two versions. It grows significantly as the differences between the two branches increase.
This information may concern those who have already invested in the Blueprints version of my product and are now interested in using the Plugin. I understand, and I am looking into potential discounts for current Fluid Flux owners.
