Guys,
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.
![Click image for larger version
Name: Viewport.jpg
Views: 1
Size: 520.6 KB
ID: 885672](filedata/fetch?id=885672&d=1709944809)
![Click image for larger version
Name: 5919 - Honeybourne Place - Camera 001 - 01-08-2016.jpg
Views: 1
Size: 519.3 KB
ID: 885674](filedata/fetch?id=885674&d=1709944809)
This is what subsequently rendered, despite looking fine in the viewport:
![Click image for larger version
Name: Render.jpg
Views: 1
Size: 495.4 KB
ID: 885673](filedata/fetch?id=885673&d=1709944809)
It appears to be rendering a 180 degree (or similar) FOV, even though the camera focal length is a mere 30 degrees.
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.
Comment