I’m sure some of you have seen my other thread regarding render node issues and that they were rendering only the HDRI (with incorrect mapping/FOV).
Now one of the nodes started working, but the FOV problem has spread to the local machine too!
This is what I see in the viewport, and previously rendered correctly on max 2016. When I opened the file in 2017 it was apparent all the cameras vertical tilt had corrupted so I recreated all of the cameras by snapping to pivot points, etc.
This is what subsequently rendered, despite looking fine in the viewport:
It appears to be rendering a 180 degree (or similar) FOV, even though the camera focal length is a mere 30 degrees.
I’ve just merged into a new scene - thankfully my file structure means I’m only rendering a scene with lights and cameras in it, everything else is a reference. Have tried rebooting all machines - am at the point now that I am considering formatting both nodes.
Hmm, maybe try rendering without camera and with exposure control (just to see if the problem persists). If it doesn’t happen it could mean the problem is with the Max Phys camera.
And now they’re rendering the perspective view just fine (in terms of FOV), but SOME references are missing - even though others that are in the same folder are being rendered. This is a nightmare, the problem changes from render to render.
Someone had changed the file path by adding a space to the name of the project(!) and not told anyone. For whatever reason my local machine was still managing to find and load assets, including references - but the nodes were not. However why this should present itself as a change in camera angle, or that sometimes things would render and other times they wouldn’t is beyond me.
There is a bug with vertical shift and the physical camera in 2017 which causes the viewport to not match the renders, but if you’re using a vray camera you should be fine. Sounds like you already have it worked out though.
Merging into a new scene?
