Phoenix FD for Max failing Backburner Sim

[jeffbrown]

Odd problem that is happening with only a current job: I am not able to render a Phoenix simulation via Backburner. I have successfully rendered other sims, and just today rendered the Chaos "Fireplace" sample file via Backburner.
I am using Phoenix FD 3, VRay Next, Max 2019. Just upgraded all machines to Phoenix 31104 (max2019_vray4), still have the same issue: Job gets submitted via Phoenix "render sim" menu, goes to BB okay, then renders light cache (no sim) for one frame, and considers itself complete. Weird, yes?
This happens using a renderfarm machine, or using the workstation in server mode. And, yes,I do still have (2) simulation licenses :>)
I have attached the file I'm testing with in case it helps (has just the sim components). Thanks to anyone who might help on this one.

[George Barzinski]

Hi,

You must have the 3ds Max Load/Save Scene Scripts option enabled from Customize → Preferences → MAXScript → Startup in order for the Phoenix Backburner submission to work. Also, make sure you use full paths for caches files and rendered images.

Cheerz!

[jeffbrown]

Thank you George. I do have that option enabled -- I was able to simulate the "Fireplace" sample OK via Backburner. Just not my scene :>P

[George Barzinski]

Hmm, really interesting because I was performing a test with your scene too. I'll check it again and write to you again.

[jeffbrown]

OK--. More curious! It could certainly be "user error" of some sort. Thanks for looking into this.

[jeffbrown]

Just thought of a possible cause (?): I'm using the Linux version of Backburner Manager. I'll find some time after hours to see if using a Windows Manager fixes the issue.

[George Barzinski]

The BB version which I use is 2019.0.0.5. Make the test again and it renders more than one frame for sure. Can you try with the Windows version just to be sure?

[jeffbrown]

Tried the Windows manager (both Win and Linux are version 2019.0.0.5), unfortunately, same result: One frame (in vRay frame buffer) rendered, then job termination.
Just to double-check, I created a new sim in a reset Max scene. That simulates OK. Must be something I "broke" in setting up that particular scene (I did start with importing existing sim components from another scene). I do have working simulations from the local/workstation run.
So, I won't ask you to gnaw on this any more, unless you are curious. In that case, let me know if I can do anything else to help.

[Svetlin.Nikolov]

Hey,

Can you check the Phoenix log file on the machine where the job fails - are there any error messages there?

Cheers!

[jeffbrown]

I don't see any apparent errors, but attached are 2 logs: one successful, one not. I am suspecting that I mis-managed the merging of the FireSim components, though why it works on your machines and fails on mine is certainly a mystery. As I mentioned, this is not causing any production problems for me, but I am happy to help you troubleshoot if you like.

[Svetlin.Nikolov]

Ah, the problem should be resolved by deleting the "PhoenixBackburnerHelper" object from the scene - it's a hack used to transfer data to the remote machines since Backburner is so limited.

This should allow the scene to be submitted safely

Cheers!

[jeffbrown]

For the win! You're correct, that was the offending item. Good to know, and thank you for the support.

[Svetlin.Nikolov]

Yay, glad that was it - with newer Phienix builds such nodes will not accidentally remain in the scenes.

Cheers!

[George Barzinski]

Ah, yes these helpers... I deleted them just forgot about that. Sorry!