DR render problems

[olejka2k]

Ondra , any idea about my problem ? Really want to use corona but this problem kills that in root.. :(

[olejka2k]

Guys sorry to bump this again but we really want to resolve this. I've tested this on another completely different PC's on another network not related to those ones - the problem still is there. And looks that thing is that it cannot find renderer. The "renderer" row is empty in MaxLog when i am rendering via BackBurner. If i will have some time i will test it with Deadline free version but i am pretty sure that it should be fine , as this is BackBurner related , and i want to use this with BackBurner.

[Ondra]

this will be probably simpler to solve over skype, can you contact me?

[olejka2k]

Sure , my skype is infected_3d

[Frood]

Just as a hint: In our network in a similar setup like described by olejka2k here in this thread as reply #9 the problem seems to be that a dr slave when used as a BB-Job-slave does not even receive the scene to render ("received_scene_[hash]" in drData directory).

This leads to the "Camera [cam_name_here] defined but not found" entry in drData\MaxLog.txt. At least here it´s reproducable. Maybe it´s the same problem.

And maybe it´s the same issue described by fobus in this post without going deeper into detail or checking logfiles.

Good luck!

[olejka2k]

Thanks for the hint, Frood. And yes you are correct - scene is not being transferred, it has 0 size. Though i solved the "Camera [cam_name_here] defined but not found" thing by making Free camera with Corona mod on top (it was VRayCamera with mod on top) and this line disappeared , though main problem was not solved.

[Frood]

That´s more than I can achieve here, drServer doesn´t even create any max file in drData :/ I will submit that to the Bugtracker when I find some time to test some remaining options.

Good luck!

[Dippndots]

Sorry to resurrect an old thread, but I am having the same issue, has this been solved?

[maru]

Hi, first please take a look at this guide if you haven't done it already and check some of the suggested solutions:
https://coronarenderer.freshdesk.com/support/solutions/articles/5000501666
If nothing helps, please do this:

completely remove the content of DrData folder, run unsuccessful rendering again, and then send us the freshly-created log files

And send us a support ticket with the content of DrData:
https://coronarenderer.freshdesk.com/support/tickets/new

We are also working on an extensive DR fix, which should solve most known problems.

[naikku]

Just I very very minor suggestion - I had the same problem with DR before:
I saw that from my 3ds max asset tracking, some bitmaps had only a file name but not a folder where they are.
This made my DR-images become "striped", 30% darker etc.. After I fixed the paths: no problems.

I use Gamma 2.2on my workstation and in my farm computers there is just 3ds max & corona 1.2.1 installed, I havent started 3ds max there and I havent played with the gamma controls on them.
But is it possible that if my workstation sends a DR-file to the farm computers, could they somehow be rendering with Gamma 1? (When I had the stripe-problem I wrote about it and someone said to check the Gamma values...)