When a physcam is created the targets pivot is aligned to world instead of matching the camera’s, making the target’s local transform useless.
as a workaround, but i am sure you know that, to move it along the view direction, you can use the view controls.
Yep, another option is to use the “pick” transform and pick the camera itself
Would be nice though if it worked like a regular max camera and inherited the camera’s transform orientation.
eh, yes indeed.
it always behaved somewhat differently from the standard max camera.
think i found a vray bug. with a max line when your creating it you can use shift to lock the direction you draw the line, with a max target camera when you create the camera then try to create the target holding shift does nothing. with a vray camera holding shift will crash max. did it each time for me in max8. can anyone else confirm?
Da_elf,
Tried this in max 9, no crash but it instantly ends the vray camera creation process and the target is positioned where ever you cursor was when you held down shift.
vrayphysicalcamera creation has been since the very begining very hard to manage…to me at least!
Agreed…!
I should add that something vaguely similar happens with vray lights.
It’s not noticeable during the daily work, but once i got scripting a plugin for them (barn doors), it resulted impossible to add a third mouse gesture (say, click, drag, click, drag again).
The action would just not work, and would stop after light creation, no matter what.
Minor, but still…
For me in max 8 it seems to freeze max for a bit, but after a couple of seconds I can click in another viewport and continue on. The vray camera goes away too. But if I right click after the freeze, the new vray camera stays and max comes back to life. Very strange.