all of a sudden...

[voltron7]

Okay, I think this issue is here somewhere, but i couldn't find it.
Anyway, using max2013 64, and vray and today one of my scenes started to act corrupted.
Basically, the rendering almost ignores the physical camera. It all looks normal in the VP, but in the vfb, it's like a totally different viewing angle/position.
Not just a slight vertical shift or distortion, but the entire view is different and not even close to matching what is seen in the VP.

This just started happening today, so I updated to latest stable 2.4 (230300) and the problem is still happening after updating.

I will next try to restart max, and then I will try to merge my objects into anew scene...but is this a bug or what?
It would be good if the scene would not suddenly start to act buggy. All I was doing was adding some more (physical) cameras and setting up a batch of views for BB.

-it happens with DR, DR+BB, and just BB (on the main WS.)
-seems okay rendering from the main WS without BB and without DR, so that is not good.

Thanks in advance

edit: trying to upload example images...

edit:
and here it is working properly with just the main workstation, no BB, no DR....

[Svetlozar Draganov]

Hello voltron7

Thank you very much for your feedback.
Would it be possible to send us this scene for investigation ?
It would be very helpful if you have saved previous version of the scene where the issue doesn't exist.
Have you made any changes to your system recently ? Any new plug-ins or installations ?

[voltron7]

Still a problem

Still happening, although not every time, probably 95% it is screwing up.
Now, when I render with DR, the slave doesn't join, and the rendering comes out okay.
If I use BB (with and without DR) it makes the problem happen.
This is really killing workflow, so if anyone has a fix for this, please let it be known
Thanks

[voltron7]

Hello voltron7

Thank you very much for your feedback.
Would it be possible to send us this scene for investigation ?
It would be very helpful if you have saved previous version of the scene where the issue doesn't exist.
Have you made any changes to your system recently ? Any new plug-ins or installations ?

Hi Svetlozar...only recent addition was Laubwerk plants, although it is not used on this job. I can't send the scene, at least not any time soon.
But I will try to go back to a version that works properly, to see if I can track it down.
Today I also will try to merge into new scene, although I don't usually like to do that on larger scenes.

As for plug-ins, there is Forest Pro, Railclone (problem exists both version 1 and 2.) and Autograss. All of these have been in use for a long time
on many jobs, before this problem arose...
Also, because this has happened for this scene alone, on a few different V-ray builds, I am starting to think it may just be a "corrupt" max scene for no known reason.
Also odd that no one else seems to be getting this issue...

[vlado]

Do you happen to have two cameras with the same name in your scene? In any case, it would be best if you can get us at least a part of the scene to take a look at.

Best regards,
Vlado

[voltron7]

Just checked and all cameras have unique names. I found one object that had a duplicate name. I renamed it and am trying it again with DR, and not BB...
Thanks again

[voltron7]

merge-fix

Well, I still don't know what caused that, but merging into a new scene resolved the issue. Thankfully, whatever it was did not come along in the merge!
Thanks Vlado and Svetlozar

[vlado]

Ok then, glad it's sorted out.

Best regards,
Vlado