Simulator Names for Deadline Simulation with Max Mode

[Joelaff]

It seems that when submitting a Deadline job using Max (rather than Standalone simscene mode) you need to name your simulator "PhoenixFDToSimulate". I did not see this in the docs anywhere. Was that supposed to be auto named when submitting? Because it was not.

Perhaps this should be in there on this page: https://docs.chaos.com/display/PHX4M...ine+Simulation

Also, right now submitting a scene to Deadline for simulation resets the frame range to frame 1 to 1, and does not set the range back to the original values.

[Svetlin.Nikolov]

Huh, there is no requirement to name a simulator in any particular way. Could you tell us more about the situation - what you have in the scene, what steps you take and what results you get?

We will look into the frame range issue - is that the render settings range?

[georgi.zhekov]

We reproduced the frame range issue - we're on it. Thanks for the report!

[Joelaff]

Well, I was looking at this when tired... I saw this line of code the in the .ms script:

local thePhoenixFD = execute (du.GetJobInfoEntry "PhoenixFDToSimulate")

But I realize now that is the deadline utility object, and has nothing to do with simulator names

The reason I suspected that was because the first few times I tried to simulate using Max through Deadline (using your submitter-- I have yet to try the SMTD submitter for Phoenix) I got the simulation started and finished messages in the log, but it was super fast, like it did nothing. (finished in 0.5 sec or somesuch). So then I got to thinking that it must not be simulating for some reason and started skimming the code for some sort of name limitation. That was when I saw that string, but in re-examining it it's clearly got nothing to do with it.

It must be coincidental with some other change, but when I renamed the simulator to that string it did work. The previous simulator name was just the default name.

So I still don't know why it didn't simulate the first few times. There was nothing in the deadline logs other than the simulation started and simulation finished messages.


On a separate note would it be possible to get the standalone simulator window (cmd.exe) you launch from the Phoenix simscene exporter to wait to close. I was trying to use standalone, but it was failing for some reason, and I could not see the error message. Or maybe it could only stay open if there is a non-zero result code (assuming the simulator returns something). I guess there is a log file someplace too?

[georgi.zhekov]

The frame range issue should be fixed in the latest nightly builds. Thanks for reporting it!

As for the the standalone console to stay open after completion - it's in the to do list. Adding your vote for it.

The log file is written in a file, yes - by default it goes to C:\ChaosPhoenix or you can open the log file location through the Phoenix prefences in the top PhoenixFD menu.

No sure what happened with your simulator name though. If you still keep the scene we can take a look and check if it reproduces on our side.

[Joelaff]

Let me see if I can find the one that had the issue. It's the same scene that has the issue with the standalone in the other thread (with both the warnings and the errors). So you probably want to look at it anyway. If I get some time I will send via the ticket system, as it is private to the client.

[georgi.zhekov]

Thanks a ton!

[Joelaff]

Conveniently, Deadline stores the actual scene file. So I have sent it along via email to support and referenced this thread. Ticket # 105608

I did not include external files, but I don't think you should need them. Let me know if you do.

This is specifically the scene file that would start to simulate and finish instantly when sent to Deadline as a Max job through the Submit Simulation to Deadline option in the Phoenix menu.

After renaming the simulator it did simulate fine in Max (but never in standalone). I suppose it is possible something else got changed. I can try to send along the next version of the file that DID simulate if that helps. Not sure if you have some easy way to diff them.



This also has that Push modifier on the geometry used in the PHXSource. It is the same scene file that failed when sent to standalone as well (via the Phoenix menu again). I know the geo is self-intersecting and junk because of the push modifier, but it was working in Max; so I rolled with it because it achieved my goals and I had no time left.

The script that Deadline copied over is included in what I am sending you. It appears unmodified.

This is client proprietary so please do not post any images here. Thanks.


Max 2023.3 Win 10Pro
PHX version is :Phoenix 5.10.01 Nightly, Build ID: 2023012631862 for 3ds Max 2023 from Jan 26 2023
(I know, I need to update, been too busy...)

2023-04-11 15:00:28: 0: INFO: Render Tasks called

2023-04-11 15:00:28: 0: INFO: Executing script: C:\ProgramData\Thinkbox\Deadline10\workers\spot\jobsData\6435bc2492343b8b244e7952\PhoenixFDSimulateDeadline.ms

2023-04-11 15:00:29: 0: INFO: Starting Phoenix Simulation Job...

2023-04-11 15:00:29: 0: INFO: Finished Phoenix Simulation Job in 0.656 sec.

2023-04-11 15:00:29: 0: Done executing plugin command of type 'Render Task'
​

[Svetlin.Nikolov]

Huh, I thought I made the console stay open already, maybe it was for the cache converter, or I was dreaming. In any case, will take care of it over the next few days and will check the other issues too. Thank you!

[georgi.zhekov]

Thanks a lot for the scene - it was super helpful!

In the Scene Interaction rollout of the Phoenix simulator you have excluded the tyCache node. Using the nightly build you have installed, this will work in Max, but won't work with Phoenix Standalone as at this point the option wasn't ported for Phoenix Standalone.
Since the option was ignored in Phoenix Standalone - the tyCache node was exported and there was an error about it having no geometry aand when Deadline sees the error it aborts the job.

If you get a newer nightly build (you can try this one for example - https://nightlies.chaos.com/main#/ph...ghtly/20230420) - the Scene interaction rollout now is exported correctly to the simscenes and the scene should be working.
Note that your scene will look different when simmed with Phoenix Standalone compared to what you get in Max as you have noise textures plugged in the Phoenix source and a Turbulence force. We still have to add support for textures and forces for Phoenix Standalone.

Cheers!