07-10-2019, 08:14 PM
(This post was last modified: 08-10-2019, 03:39 PM by billmccrary.)
Another weird one - getting closer to release means all the fun weird bugs start popping up...
We have a slow flowing fluid, that on app starts works like we want. However, after some period of time (~15-30 mins), the behavior changes. For example, the fluid simply stops flowing like it should and 'sticks'.
We're looking on our end now to see if we're not turning something on or off when needed.
Question - is there some life cycle calls or other 'cleanup' utility methods we can or should be calling to keep things tidy? For example, if I'm emitting fluid from one solver/emitter pair, then I want to turn that off and turn on another one, is there some 'reset' process we should be doing in our scripts? I didn't see this documented explicitly but maybe we're missing it.
Also - any chance you can shed some light on what this ObiSolver.ResetSimulationTime() method does?
http://obi.virtualmethodstudio.com/docs/...0f0e4957f7
Thanks in advance!
We have a slow flowing fluid, that on app starts works like we want. However, after some period of time (~15-30 mins), the behavior changes. For example, the fluid simply stops flowing like it should and 'sticks'.
We're looking on our end now to see if we're not turning something on or off when needed.
Question - is there some life cycle calls or other 'cleanup' utility methods we can or should be calling to keep things tidy? For example, if I'm emitting fluid from one solver/emitter pair, then I want to turn that off and turn on another one, is there some 'reset' process we should be doing in our scripts? I didn't see this documented explicitly but maybe we're missing it.
Also - any chance you can shed some light on what this ObiSolver.ResetSimulationTime() method does?
http://obi.virtualmethodstudio.com/docs/...0f0e4957f7
Thanks in advance!