RealFlow Official Forum

A user is having a problem with the LE and I'm having the same with Standard.

The command line is making 1kb files.

It seems to be an issue with initial states.

I had an initial state and it gave me 1kb files. I turned off initial state and it worked ok. I turned initial state back on and simmed. It created files correctly. However, it didn't run from the inital state and started from scratch.

Ok, there is a problem with the command line and initial states.

Here is a scene ChristianZ made so unless it's only happening with me, there is a bug:

https://dl.dropboxusercontent.com/u/768 ... netest.rar

Speed is at 2. Run the sim for about 40 frames.

It'll make correct files in the particles folder. Set an initial state for the last frame.

Sim from frame 0 again. It'll make files. However, load in the cache and you'll see that the command line hasn't started from the initial state. It has started from scratch.

Now, set your speed to 0 and start from initial state again. It'll make files but they'll be 1kb because it's not running from the initial state and you aren't emitting anything cos you have your speed at 0.

Hey,

You are right. It is a bug. We'll fix it.

Thanks for reporting

luisM.

There is a workaround for this.

Check out you have the reset to initial state option activated. Move the timeline to a frame different of zero. It doesn't matter if you can't see anything in the viewport, and now simulate by commandline with reset to inital state activated. Now it should works.

luisM.

Yup, that works. Good to know. So, it's an issue with the start of the timeline then (frame 0) ?

Otuama wrote:Yup, that works. Good to know. So, it's an issue with the start of the timeline then (frame 0) ?

It seems like the command line version is only performing the reset action when it is not already on the first frame.

I think I have a reason for that...... Maybe.

I brought this up with Gus when doing internal testing before the release.

There seems to be a -/+ discrepancy with the command line. It's printing that a frame is being started when it has already finished it.

http://grab.by/mMuG

So, the command line says it's starting frame 0 when really it's starting frame 1.

What may be happening is the command line is trying to sim frame -1, and that's screwing things up.

I e noticed that in command line as well. It says for example: Frame 2 Started, however frame 2 is complete. My best guess is that it means its starting to simulate the particles from frame 2 to frame 3. I don't know if this would mix things up for Realflow though.