[nappy]

Hey guys,

this never happened to me before.

I am in the "Back" viewport of rhino and I press render..and once maxwell loads up the view is no longer the "Back" view that i see in rhino..but a skewed perspectival, zoomed out view.

Anyone know how to fix this? This was not happening to me before...

thanks!

[JDHill]

The problem is that those viewports use parallel projection, which the Maxwell camera does not support. To render something similar, you would want to use a perspective viewport, but set it up with a very long lens.

[kami]

it's working quite well this was. eg. with a lens of 1000mm one can barely notice any difference to a planar view
but make sure the focus point sits correctly

[nappy]

Thanks for the responses..what i tried to do is export the render file to MXST and then choose the "back" camera setting..is that a valid way to do it?

ty

[JDHill]

You can do that, but what I'd do is this (in Rhino):

- open Object Properties
- click in the desired viewport (Top, for example)
- set Projection to Perspective
- set Lens Length to something like 1000mm, like Kami said
- set Target X/Y/Z to 0.0
- set Camera X/Y to 0.0

[nappy]

alright thanks kami and jdhill..yeah that seems a lot easier.

[polynurb]

- set Target X/Y/Z to 0.0
- set Camera X/Y to 0.0

..hmm i have to interrupt here... haven't you ever had problems with setting x/y for camera & target to the identical values in rhino or studio?

..i noticed that first in studio too, that when i emulated a parallel view and set x/y values the same to target &camera the camera would loose the "upvector" and spin crazy around Z axis ?

further i noticed the same problem in rhino..

i did a series of ground plan z-clip renders recently and wehenever i set the target of the camera to the next level in Z it would spin around Z...

i then changed target to XX.286 instead of XX.285 and it would be fine .. just coincidenting xy target and xy camera may work fine initially (setting the view via command) but changing any values in object properties mess it up later..

im not often using studio, but i think there is a similar issue i observed..

hope it is clear what i mean...

[JDHill]

Yes, it's probably due to a basic problem that can happen in 3D, depending on the implementation; here's a short explanation: http://www.anticz.com/eularqua.htm

[polynurb]

..i knew it was Euler's fault..


thanks for the link!