Send Simulation to Backburner error

Phoenix Issues
1

I keep getting this error when trying to submit to BB. No idea why.

.jpg.jpg
.jpg.jpg887×564 84.1 KB

2

Hmm, Max 2019 sounds like it should be okay. I honestly don’t remember a time when I had to submit to Backburner and did not have to uninstall and reinstall it again before it can start working, so as a last resort, maybe try that. Also, make sure the Backburner and 3ds Max versions are the same - if you have installed a new Max, or Maya, it could have messed things up…

3

All of my backburner versions are the same across all nodes. I get the same message with the attached scene. For low res Phoenix simulation work, my workstation is fine. It’s when I crank up the resolution that it would be nice to use the other nodes on the farm.
tyflow pheonix test.zip (291 KB)

4

Hey,

I can’t seem to reproduce it in here. Does it help if you uninstall and then reinstall Backburner?

5

Hey, so if it quits after 1 frame, this might be due to a wrong output path. Where does your Output cache path point?

6

Hey,

Simulations are sequential. Each simulation frame depends on the previous one. Unlike rendering, you can’t split the simulation sequence into 4 parts. You could run 4 simulations in parallel with different settings and pick the best looking one, or run 4 completely different scenes. If you can break apart your simulation into separate grids which don’t have to interact with one another, then you can send these to different machines, but it has to be the entire sequence.

The remote machines should still be able to write their caches successfully though - what is expected is that only the machine starting from frame 0 would give you the result you like, while the other 3 should simulate, but won’t be correct. In case the 4 machines start writing to the same caches, then this might be the reason for your problems. If even the machine starting from frame 0 quits immediately, then if you have installed a Phoenix nightly from around last week or so, I’ve added some more debug logging to the Phoenix log, so it would help pinpoint the issue - can you check the Phoenix log on the Windows drive /PhoenixFD on any one of the remote machines and see if there are any or messages there, or even send the log over?