tl;dr: We have new guidelines for requesting technical support
The FLIP Fluids addon has recently passed 800 (!) sales and we are incredibly grateful for the support that we have received from the Blender community. We had always expected that the addon would be well received, but we never expected to reach this amount of sales in just over two months. Your support has allowed us to keep doing what we are passionate about and that is to continue development of the FLIP Fluids addon and work on new features.
This post will be an update on the current status of the FLIP Fluids addon. Lately we have had some worries that we have stopped development of the addon (we haven’t!) and some complaints about delays in support requests, so this post will also address these issues.
With the growing userbase of the FLIP Fluids addon, we have recently had some trouble keeping up with the increased volume of support requests. Ideally, we would like to respond to all support requests within 24 hours, but lately there have been some days where there is a large influx of messages and we have not been able to respond as quick as we’d have liked.
A problem that we are having is that we have been responding to support requests over a wide variety of platforms (Blender Market, GitHub, Email, Blender Artists, Facebook, Twitter, YouTube, Discord). Handling support requests over all of these platforms was not a problem with a smaller userbase, but at this point, juggling requests and handling issues spread across these sites had become unmanageable.
Another problem that we have been facing is that we have not had a set of guidelines for how to submit bugs, request troubleshooting support, request features, and submit questions/comments. With the lack of guidelines, there has been no way for users to know the most effective method of communicating issues to us. We have often had to ask for additional information, which has led to an increased amount of time to resolve issues.
Guidelines for Technical Support
We have made some changes to the way we offer technical support for the FLIP Fluids addon. We have recently added detailed guidelines for how to request technical support. Since offering support across a large number of platforms has been unsustainable, we have also changed which platforms for which we will offer technical support. Technical support requests will primarily be received through the Blender Market messaging system, with GitHub as an alternative for submitting bug reports, and email ([email protected]) as an alternative for submitting questions/comments.
You may view the new guidelines for requesting technical support here:
The purpose of these guidelines is to streamline the process of reporting bugs/issues, troubleshooting scene issues, requesting features, and submitting questions/comments so that we have all of the necessary information in your request in order to help you as quickly as possible. Before requesting support, please read through the relevant guidelines. If your request for technical support does not adhere to the guidelines, your request may take longer to fulfill, or you may be asked to resubmit your request.
What is the purpose of this Blender Artists thread?
This thread is still an appropriate place to discuss the addon and troubleshoot issues with other users. This thread is not the best platform for requesting direct support from us as it is quite a long read and many questions and issues that come up are repeats from earlier in the thread history that can be difficult to find. I will still be checking in with this thread often and offering support and input when possible, but if you need support urgently, it would be best to contact us through the officially supported channels.
We have received some concerns that we have stopped developing the addon since we have not released version update in over a month (last: June 1st, v1.0.3). I can assure you that we have not stopped development and are continuing to add new updates, features, and bug fixes.
We did not expect the next version (1.0.4) to take this long to release, but there have been some large delays in development for us recently that has caused very slow progress in the past month. The recent issues stated above of offering an unstructured technical support service has largely cut into development time. Dennis and I have also been quite busy in our personal lives. We are both currently in the process of moving homes (Myself within Canada, and Dennis within Germany), which has also cut into development time.
There have been concerns about how long it is taking us to implement new features. We have seen some misunderstandings about how large the FLIP Fluids team is, that we should be developing at a much faster pace, and this is another reason why it may appear we have stopped development. We are actually just a small team of two and have just a single programmer. As we are a small team, it can take some time until feature requests are added to the product and we thank you for your patience.
Here is the current changelog of version 1.0.4:
- Added support for baking from the command line (issue #329)
- Added debug functionality to visualize the true domain bounds (issue #299)
- Added functionality to restrict viewport/render fluid display from the ‘FLIP Fluid’ physics button (issue #222)
- Added Inflow option to constrain fluid inside of the inflow object to match the inflow emission velocity. Allows inflow to work when submerged (issue #322). Allows low velocity values to have the effect of slowing down inflow emission (issue #90)
- Fixed bug that would require reloading a scene if an invalid cache directory was set before baking (issue #330)
- Addon will now display popup error message when exporting a preset package to an invalid directory (issue #320)
- Fixed bug where surface motion blur rendering would show a ‘hard edge’ of the object that was not properly blurred (issue #87)
- Fixed bug that would trigger an error if a deformable inflow was located outside of the domain
- Fixed UI issue to disable ability to insert keyframes into ‘Hold Frame’ option
- Removed ‘Invert Surface-Contact Normals’ option in ‘FLIP Fluid Surface’ settings. This option does not work as intended and is not useful.
- Fixed bug where whitewater particles would be killed when boundary behaviour was set to ‘Ballistic’ (issue #354)
There is still some more bugfixes, performance enhancements, and feature requessts to finish up version 1.0.4, and it may be a few more weeks until this version is ready. The next version should be released by August 11th at the latest.
Hope this gives you an adequate look into the current state of development for the FLIP Fluids addon! We thank you for your support and patience!