- User Since
- Apr 24 2019, 1:22 PM (111 w, 5 d)
Apr 13 2021
Loading the above file in Blender 2.79b produces the expected result (where one cube is accelerated upwards and the other down). Opening in 2.93Alpha produces unexpected results (with both cubes being affected by both forces - despite the file being loaded with the different forces and cubes being in different collections (so the loading of the layers works into separate collections but those collections aren't being interpreted in the same way as previously).
Feb 18 2021
Sep 22 2020
The example (using a rotating inflow) is just to demonstrate the problem - I wasn't actually aiming for realistic tangential flow. The point is that the inflow isn't using the previous frame to determine the velocity but is actually using the *last frame that the inflow was switched on*. So in the first 'emission' in the above case (in the "12-o'clock" position) the fluid has no velocity - not because the inflow wasn't moving but purely because it's the first frame of emission of fluid (so it seems the calculation doesn't have a 'start' position to determine the offset).
Sep 16 2020
Jul 28 2020
Jul 19 2020
Jul 15 2020
I see what you mean - at the latest 2.90 it's not initialising on any now. I originally found the problem in 2.83.2 and it does seem to have the described behaviour there. However, at 2.90 it seems to initialize in neither situation - until you change something in the Domain following the above setup. eg, Clicking on the Resolution Divisions and simply pressing Enter to accept the details - then it creates the fluid particles. When re-testing at 2.90 I must have made an extra click by mistake - sorry for the confusion with that part... so the behaviour is slightly different between 2.83.2 (where it works one way around) and 2.90 (where it doesn't init in either case).
Sep 18 2019
I've downloaded the latest 2.81 daily build (previously I'd used the 2.80 official build as I couldn't install later versions on my system) and this does appear to be working as you have found. Looks like the issue has been resolved in 2.81. Apologies.