Page 1 of 1

Initial State ...

Posted: Mon Mar 11, 2013 7:21 pm
by mdonovan
Hey Guys,

I am trying submit a job to a remote node using the job manager. It gets submitted no problem ... the problem is that its ignoring that fact that the scene has an initial state.

Thoughts ?

I am using Job Manager build ...



Re: Initial State ...

Posted: Tue Mar 12, 2013 1:57 pm
by FlorianK

Is that just when sending the job via Job Manager or also if you log in remotely to the machine in question and sned the job via command line?

If so- did you already check if your nodes are able to read all network paths possibly affected with that scene, if all drive letters are the same for each machine (if using any). I've had a situation where there was a problem with IniStates and the geometry path. Finally, (if possible) try using a different geometry objects.

You might also try to trick Realflow and use an Initial State without actually using an Initial State. I am not sure if this will work with the Job Manager and cannot test it right now.

1. Set your Initial State for a scene.

2. Simulate one Frame, starting with the Initial State.

3. Deactivate the Initial State and simulate from that first simulated frame on.

Re: Initial State ...

Posted: Sat Mar 16, 2013 4:46 pm
by mdonovan
Florian ... thanks !!!!!!!

I ended up saving the initial state. Creating a new scene that used the initial state. Simulating 2 frames. Then submitting to the Job Manager via the Job manager ... NOT the sendscene command. In the Job manager submission I stated the start frame as frame 2, use cache.

seems to work.

I hope 2013 addresses the infancy of the Job Manager.