Ortho camera
Moderator: face_off
This could be automated, however at the moment there is not a good match between the Modo and Octane Ortho camera scales - so it is currently an explicit setting to turn on the Octane Ortho camera. The conversion of the Modo Camera scale to the Octane scale is a function of the Modo Camera "Film Width", "Film Height", "Angle of View" and "Film Fit" and I was not able to work out the formula for the Ortho camera.
Thanks
Paul
Thanks
Paul
Win7/Win10/Mavericks/Mint 17 - GTX550Ti/GT640M
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
Octane Plugin Support : Poser, ArchiCAD, Revit, Inventor, AutoCAD, Rhino, Modo, Nuke
Pls read before submitting a support question
i noticed the difference in scale and assumed it was down to something technical
i think it would still be useful to link the camera types so at least that bit is automated. it's easy enough to render something and realise later it'd perspective and not ortho
i think it would still be useful to link the camera types so at least that bit is automated. it's easy enough to render something and realise later it'd perspective and not ortho
I had a quick look at this and it should be fixable.
The problem seems to be that the plugin is using "target distance" in the conversion (which should not be used since modo changes this constantly as you "move" in the GL camera view), while modo is actually using the "focal distance" channel.
I have attached an example scene. If you set the "target distance" to 1.5, to match the value in "focal distance", the render looks correct
While this manual workaround works, it will break as soon as you "move" the camera in the gl view, which changes the target distance (eg. "a" to fit all).
The problem seems to be that the plugin is using "target distance" in the conversion (which should not be used since modo changes this constantly as you "move" in the GL camera view), while modo is actually using the "focal distance" channel.
I have attached an example scene. If you set the "target distance" to 1.5, to match the value in "focal distance", the render looks correct
While this manual workaround works, it will break as soon as you "move" the camera in the gl view, which changes the target distance (eg. "a" to fit all).
- Attachments
-
- ortho_cam_issue_01.7z
- (32.78 KiB) Downloaded 67 times
Win10 Pro / Ryzen 5950X / 128GB / RTX 4090 / MODO
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ
"I am the resurrection, and the life: he that believeth in me, though he were dead, yet shall he live" - Jesus Christ