Cannot render in DRserver

[khazuma]

When I use DRserver, the main machine starts rendering without any problem, but the rendering on the Server side never starts, and the moment it enters the “parsing scene” stage, it goes back to “starting”, and then the “parsing scene” stage starts again. stage and back again... The “parsing scene” stage is not started, and the moment it enters the “parsing scene” stage, it reverts back to “starting”, goes to the “parsing scene” stage again, goes back, and so on.
The solution to this problem is to create a new CoronaCamera and render it again, which sometimes solves the problem, and I have been able to work around it.

[Avi]

DR issues can be tricky, and they can be caused by a lot of factors so it would be best to start a ticket with us so we can try to troubleshoot the issue for you.

https://support.chaos.com/hc/en-us/requests/new

[khazuma]

Thank you very much!
I'll ask over there.

[Avi]

Thanks for sending the ticket.

This is now handled in ticket #314186

[theredmage333]

Hey, suddenly having the same issue, was this ticket resolved? If so what was the issue? All of a sudden we are having issues staying connected to our DR machines. Whether thats 1 or all of them. We havent updated anything except for the usual windows forced updates recently...

2024-11-18 12:59:06   Received sampling focus mask (region 0 0 4200 2333)
2024-11-18 12:59:35   Closing loopback manager
2024-11-18 12:59:36   DR is finished
2024-11-18 12:59:36   Ready for new connection

We get this on repeat or this

2024-11-18 13:00:21   Received sampling focus mask (region 0 0 4200 2333)
2024-11-18 13:00:34   Got a message from remote: terminate_soft
2024-11-18 13:00:51   Sending command to slave: <root><DataType>0</DataType><Command>terminate_soft</Command></root>
2024-11-18 13:00:51   Closing loopback manager
2024-11-18 13:02:35   DR is finished
2024-11-18 13:02:35   Ready for new connection

[Avi]

Yes, it was solved and the user found the solution themselves by moving all the textures used in the scene to a single local folder and relinking them. After doing this, the DR worked fine without any problems.

The issue seemed to be related to the texture paths being set as network paths (NAS-based), which caused issues for the user during the rendering process, even though the scene was rendering fine on one machine without showing any "Missing Texture" errors.

If you are also getting some DR related issues, then it would be best to start a ticket with us so we can help in troubleshooting the issue.

[theredmage333]

Hi Avi, after hours down in the trenches I found that our problem was related to Adobe Substance. Any objects or materials found in the scene with SBAR seem to cause issues with DR staying connected. It's beyond me why suddenly this has become an issue, not all of our artists/scenes use it so maybe its been a thing but we didn't notice it, there were a few Adobe updates maybe a week or two ago but not sure how that relates to Substance plugin and 3DS Max. We are currently using 3DS Max 2025.2 with Corona 12 Hot Fix 1 and Adobe Substance plugin was at 3.0.2, I upgraded it to 3.0.4 to see if that helped and no.

Once the SBAR are removed from the scene the rendering goes as expected. I will eventually upgrade us to 2025.3 and install the latest Corona 12 Update 1 version that just came out to see if that resolves the issue.

[Avi]

Hi,

Thank you for your test and sharing this info with us.

Is it possible for you to send your scene to us so we can try to reproduce the same issue on our end?

https://support.chaos.com/hc/en-us/requests/new