Vray Distributed Rendering Bucket Problem

[andrewdavidyoung]

I have set up my scene states to switch cameras and render different views.   When I do distributed rendering, it gets really confused on only TWO of the cameras (out of 5).  

It's rendering some buckets with a massively distorted field of view and other perfectly fine.  I believe the local render bucket is rendering correctly, but the other distributed ones are incredible wonky. 

This has a drastic effect on my work flow as I need to rely on overnight renders to be correct.  

[Alfred.DeFlaminis]

Hello @andrewdavidyoung,

I'd like to help with this issue if possible.  Which version of 3ds Max are you currently using?  Do all your render nodes have the same service pack of 3ds Max?

If I created a private folder for you, could I check out the file?  Does this issue persist if you were to choose a different renderer?  (Not a solution, just a test.) Thanks for the information!

Best Regards,

[Alfred.DeFlaminis]

Hello @andrewdavidyoung,

I just wanted to follow up here, any progress on this issue?

Best Regards,

[andrewdavidyoung]

Hi Alfred, thanks for the help.

Sorry for the delayed response, continued hectic work week.  I am using 3ds Max 2017 with each one updated to the latest service pack.  Everything is setup in Vray using their Vrayspawner and not backburner so testing with a different renderer doesn't really work out.

It seems like 3ds max has an issue with which viewports are being used and the state sets get confused on the cameras.   My physical camera has a FOV of 75 and the local buckets render the image accurately, but the distributed render buckets look like they have dropped the physical camera FOV down to 0.  Its like that information isn't getting delivered to the distributed render scene. 

I am on windows 10, connected through a domain with 2 render servers, both updated and on windows 10 as well. 

[Alfred.DeFlaminis]

Hello @andrewdavidyoung,

Thank you for the information.  I have some questions that may help here, and if this is a bug I want to collect as much info as possible so I can log it.  I don't have any bugs logged for this issue.  A few questions:

1) Are you on the nightlies version of Vray?  Which version are you on, regardless of version? 

2) Are you using a VrayCamera, standard camera, or a 3ds Max physical camera?  

3) If I were to create a private folder, would it be possible to share a scene with this issue?  (any scene, use any objects, just need the malfunctioning present.)  

Thank you for taking the time to answer those questions, and for the clear information in your previous post.

Best Regards,

[Alfred.DeFlaminis]

Hello @andrewdavidyoung,

I just wanted to follow up here, any chance I could take a look at an offending file?  I know you have deadlines but I didn't want you to think I had forgotten about you.  Thanks!

Best Regards,

[andrewdavidyoung]

Hi Alfred,  No worries, you are incredibly quick at responding.

1. I am not on the nightlies, I'm still on the previous build of Vray 3.40.02, on all 3 machines. I have not updated to the latest .03 build, but this issue is not exclusive to this build, It has happened prior.   

2.  I'm using 3ds max's Physical Camera.

3. Yes, i can uploaded the file to a private folder. The file is about 100mb but I have to ask that you keep the file confidential. 

Thanks for your Help.

[Alfred.DeFlaminis]

Hello @andrewdavidyoung,

I've been spending some time looking into this, and another user mentioned in another thread that he had this same issue and uninstalling SP1 fixed it for him.  Before I create a folder, any confirmation about that would be good enough and there would be no need to share the file.  It would always be confidential but if you don't mind I'd like to try to see if you could uninstall sp1 on just 1 render node and 1 dev machine and see if the problem goes away.  This way I don't have to put you in that position.

If that fails, a file would be great but you can remove the major objects so there's nothing to worry about.  Again, always confidential regardless.  Thanks for taking the time to try that.

Best Regards,

[andrewdavidyoung]

Thanks.  I will give it a shot when I get a moment to, and let you know if it works. 

[Alfred.DeFlaminis]

Thank you @andrewdavidyoung.

[andrewdavidyoung]

Unfortunately, it did not solve the problem. 

I reverted all the service packs, and brought it back to before 2017.1  with no avail.

It did bring up a second issue, involving the viewport display.  When I install 2017.1 patch, Standard w/ default shading in the viewport makes my objects disappear.  I cannot see them until i switch it to facets.  When i stepped back a version to regular 2017, the issue disappeared.

I deleted some models and brought the file size down to 20mb.

~Andrew 

[Alfred.DeFlaminis]

Hello @andrewdavidyoung,

Thanks for the update.  I did come across a thread on the Chaosgroup forums that may be related, I have linked it here.  It's a long shot...

The objects disappearing might be due to either an unsupported graphics card or your user settings may need to be reset.  Please let me know if either helps.  

Best Regards,