This is weird I am having the same problem as above, and last week everything was working fine? My V-Ray is DR fine...
29/12/2015 00:05:56; CORONA: Corona is up and running. Corona version: 1.3, netrender mode: on, slave mode: on, quiet mode: on, Max gamma (display/input/output): 2.2/2.2/2.2
29/12/2015 00:06:45; Max is ready
29/12/2015 00:06:45; Frame 0 assigned
29/12/2015 00:06:45; Error creating Bitmap
29/12/2015 00:06:45; Render Error (Initializing Renderer)
29/12/2015 00:06:45; Error rendering frame 0: Render Error (Initializing Renderer)
29/12/2015 00:06:45; Send End of Job command to Max
29/12/2015 00:06:46; Job Completed with Error(s) - see above
29/12/2015 00:06:46; Total elapsed time 00:00:01
29/12/2015 00:06:46; Scene C:\Program Files (x86)\Corona\DrServer/drData//received_scene_3593816877.max completed.
29/12/2015 00:06:56; Error occured while rendering job.
FIXED:
After half a day narrowing the errors I found out that the main machine was causing the error not the DR/Slaves Machines for some reason. I just removed all the 3ds Max settings and it worked:
1 - Close 3Ds Max
2 - Go to C:\Users\[YourName]\AppData\Local\Autodesk\3dsMax\2016 - 64bit
3 - Delete ENU folder
4 - Restart 3Ds Max
--
Update!
So after testing with small scenes DR worked fine but after going back to my existing large scene the same thing happened again.
The thing is when I go back to my small test scene DR wont work now. same error as above. Even new scene with a box only.
So my guess would be 3Ds Max Settings and then woala:
It was because of one small tick in the settings
Preference Settings --> Files ---> Save File Properties ( This need to be ticked )
If I un-tick it the Slaves crash but If I have it ticked everything works fine.
Hope this will help someone in the future :)
« Last Edit: 2015-12-29, 14:24:23 by seiq »
Logged
3D Visualiser - London UK