I know there is little documentation for RT so i might have some setup issues but so far i’m unable to get DR working for RT.
my additional machine has the latest RT installed and render slave launched with the correct license config’d. However when i start ipr on my local machine the render slave begins to render or at least it says it’s Rendering the image but there is no processor activity and the clock just keeps ticking..
Meanwhile my local machine is maxed out and working with RT fine..
Hm, ok. How did you run the RT render servers? The command needs to be something likevray -server -rtengine=1 -portnumber=20207The regular short cut in the start menu does not add the -rtengine=1 part.
Interesting. Was there documentation that mentioned running that flag? Or is this the first I could have heard about it?
Is there a way to use that flag when running vray as a service on the farm? Seems that the service parameters don’t pass that flag on to vray.exe. I’ve never used the vrayconfig.xml that I’ve read exists… how would I configure that, if it would work?
Also, when running the flag on starting renderslave, an error pops up: “procedure entry point not found”
Thus we don’t feel comfortable having that start up on windows boot. (instead of using the service option).
Next to the beta downloads for V-Ray RT, there is a link to the release notes for the RT where this is mentioned.
Is there a way to use that flag when running vray as a service on the farm? Seems that the service parameters don’t pass that flag on to vray.exe. I’ve never used the vrayconfig.xml that I’ve read exists… how would I configure that, if it would work?Eventually the flag will go away for render servers. Right now it tells the V-Ray render server if it will be used for RT rendering, or for regular DR rendering (this can’t be changed on the fly for the moment).
Also, when running the flag on starting renderslave, an error pops up: "procedure entry point not found"Do you get any error messages in the console with that?
Thus we don’t feel comfortable having that start up on windows boot. (instead of using the service option).Yes, definitely not a good idea
Ah, ok. You can safely delete that file (vray_LightAmbient.dll) It has probably remained there from a very old version of V-Ray - it is no longer needed. Ideally, the uninstaller of the older version should have removed it, but apparently sometimes it stays behind.
Great thanks for that, all working now.
I did see the release notes but i had read it was for Linux and Mac OS so i didn’t pay much attention..sorry
cheers