command line & timeline lock
command line & timeline lock
Could some form of safeguard be added where if the timeline is locked and the command line is enabled the simulation won't take place? A warning could be shown asking the user to either unlock the timeline or turn off command line.
Otuama - Vimeo
'Strength does not come from physical capacity. It comes from an indomitable will.' - Gandhi
'Strength does not come from physical capacity. It comes from an indomitable will.' - Gandhi
Re: command line & timeline lock
Hi Sean,
Why would you want to do that exactly?
There are cases in which I personally use the cmd with the lock feature to have a preroll.
Am I missing something? Perhaps did not get the question correctly.
Cheers,
g-)
Why would you want to do that exactly?
There are cases in which I personally use the cmd with the lock feature to have a preroll.
Am I missing something? Perhaps did not get the question correctly.
Cheers,
g-)
...........Gus Sánchez-Pérez..........
RealFlow Product Manager
Next Limit Technologies
RealFlow Product Manager
Next Limit Technologies
Re: command line & timeline lock
Hi.
Say, for example, I'm filling a bottle that I'll eventually want to use as an initial state.
When the timeline lock is turned on (and frame countdown isn't being used), Rf doesn't export files.
So, if the timeline is locked and the command line is used, when you close the command line, there is no way to use the particles the command line has simmed because they won't be displayed in Rf (because the command line was used) and no files would have been created because the timeline lock was used.
That make more sense? Maybe I'm just going mad and am talking (typing) rubbish.
Say, for example, I'm filling a bottle that I'll eventually want to use as an initial state.
When the timeline lock is turned on (and frame countdown isn't being used), Rf doesn't export files.
So, if the timeline is locked and the command line is used, when you close the command line, there is no way to use the particles the command line has simmed because they won't be displayed in Rf (because the command line was used) and no files would have been created because the timeline lock was used.
That make more sense? Maybe I'm just going mad and am talking (typing) rubbish.
Otuama - Vimeo
'Strength does not come from physical capacity. It comes from an indomitable will.' - Gandhi
'Strength does not come from physical capacity. It comes from an indomitable will.' - Gandhi
Re: command line & timeline lock
Ok. I see what you are saying now.
I think, and I believe we have talked about this internally a couple of times, that what we can add there in the future is the ability to save the initial state during the countdown (kinda saving files every n frames, like autobackup).
Definitely food for thought.
Thanks for reminding us.
g-)
I think, and I believe we have talked about this internally a couple of times, that what we can add there in the future is the ability to save the initial state during the countdown (kinda saving files every n frames, like autobackup).
Definitely food for thought.
Thanks for reminding us.
g-)
...........Gus Sánchez-Pérez..........
RealFlow Product Manager
Next Limit Technologies
RealFlow Product Manager
Next Limit Technologies
Re: command line & timeline lock
I'm glad you guys are thinking about adding this! cmd line sim doesnt work when you start from frame zero unless you're emitting particles over time, the only way I can get any kind of "initial state" to work with cmd line is to simulate to frame 1 with the GUI, then start the cmd line sim from that frame. It would be nice if initial state .bins and volume emitters would load in cmd line too.