You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was double-checking some problem I had with camera location and lookat export to POVRay.
The problem I am suspecting is that the camera location shifting which can be done by CTRL+Mousedrag
does not make it into the POVRay export. During that I wanted to confirm that the camera location export
to clipboard (menu: "Tools" / "Show View Info...") works correctly. And voila:
there the same problem occurs: if you shift the camera by CTRL-Mousedrag, this change is not reflected in the camera data which is copied to
the clipboard. I was able to reproduce this bug also in the currently official release 4.3.
The text was updated successfully, but these errors were encountered:
The "Show View Info..." dialog does not support arbitrary camera positioning. This is in fact documented in LDView's help. The reason for this is that LDView doesn't support arbitrary camera positioning from the command line. It probably won't ever.
The POV export does support arbitrary camera positioning. Steffen, if you can provide me with a set of steps where this isn't working properly, please do. Please note that in order to be sure that it isn't working properly, you must use View->Standard Sizes in LDView to select an aspect ratio that matches your aspect ratio in POV-Ray.
From Steffen on forums.ldraw.org:
I was double-checking some problem I had with camera location and lookat export to POVRay.
The problem I am suspecting is that the camera location shifting which can be done by CTRL+Mousedrag
does not make it into the POVRay export. During that I wanted to confirm that the camera location export
to clipboard (menu: "Tools" / "Show View Info...") works correctly. And voila:
there the same problem occurs: if you shift the camera by CTRL-Mousedrag, this change is not reflected in the camera data which is copied to
the clipboard. I was able to reproduce this bug also in the currently official release 4.3.
The text was updated successfully, but these errors were encountered: