Dropped Redshift Material

[Tony Bexley]

When rendering this scene, we get 1 of the materials to not work randomly on certain machines for a batch of frames but on other machines it's fine. And sometimes itll work later on the same machine.  

There's no errors in the redshift logs AFAIK except " rdware-accelerated GPU scheduling not enabled" but I don't think that should effect anything.

Can someone tel me what's going on here? Attached the log, guessing something with the "NodeSystemClassImpl call to InstantiateImpl didn't succeed for (com.redshift3d.redshift4c4d.nodes.core.incandescent, net.maxon.node.class.nodesystembasedtemplate, (nullptr)): Couldn't open file. (file:///C:/Users/xvAdmin/AppData/Roaming/Maxon/Maxon Cinema 4D 2025_789E552B_x/dc/builtinrepository/com.redshift3d.redshift4c4d.nodes.core.incandescent/net.maxon.asset.previewimageurl.derived)

R214|   Cause: Errno #13: Permission denied"

We randomly have this issue, not sure if a redshift or a royal render issue... 

Thank you!

[Tony Bexley]

Hello...?

[RR, Schoenberger]

Hi

 

The render log file does not contain any error that is caused by RR.
The only error messages are these “Cause: Errno #13: Permission denied” messages

and a missing plugin “HDRI Link Plus”.

Have you asked in the Redshift forum what this error message means?
Does the folder c:\Users\ xvAdmin\AppData\Roaming\Maxon\Maxon Cinema 4D 2025_789E552B_x\dc\builtinrepository\ exist on Render-McRender?
If not, does it help to create that folder?

 

 

You can try to see if the logfile of Redshift contains more error/information.

Please replace the files in these 2 folders with the attached file

RR\render_apps\_config\     

RR\render_apps\_config\rr_original

 

rrControl should then show the Redshift log files as well.

 

 

 

 

regards,
Holger Schönberger

 

Please use the rrKnights Tavern
or our support system for new questions.

[Tony Bexley]

Sort of figured this out, awhile ago but have time to post about it now:

I worked with a collegue (who uses c4d wiuth deadline) and we figured it this error happens when two C4D command lines try to access the same redshift plugin files at the same time (could be incandescent/noise/AO/whatever). It only happens when the two or more command lines precisely try to access the same files at the same time, so the speed of the machine and size of the scene can change if this error happens or not, and certain scenes are more prone to it.

So the fix would be letting the user add a custom offset between render threads so they don't simultaneously start at the same time. Is there such a setting? I saw in the rrConfig per client under misc: "wait xx seconds after a new job before requesting a job for an other thread" but that wouldn't apply for the same job, correct?

here is a link to the issue happening with deadline but it's the same issue for royal render: 

https://forums.thinkboxsoftware.com/t/frames-randomly-render-with-clay-material/33766

Any thoughts?

[RR, Schoenberger]

Hi

 

> So the fix would be letting the user add a custom offset between render threads so they don't simultaneously start at the same time. Is there such a setting?

> I saw in the rrConfig per client under misc: "wait xx seconds after a new job before requesting a job for an other thread" but that wouldn't apply for the same job, correct?

 

Yes, this is the setting you are searching for.

Just curious: What’s your current setting?

 

 

C4D startup time is about 20s.

Scene load time: 0:00:52  h:m:s.

 

But note that this does not mean that the Redshift startup is done the whole time, it has to load geometry as well and I assume the C4D startup does not count.

 

 

regards,
Holger Schönberger

Craftsman and Keeper of the Royal Render Flame