Camera Shaking Problem

[jacksc02]

go to your control panel, regional and language options and just make sure that the different machines match each other

[instinct]

well a possible explanation for not all frames beeing bad would be non fractional values.

so for example on the bad maschine a value of 1,31 might be truncated to 1 because of the different regional setting. a value of 1 will still be 1 i guess.

That's a complete shot in the dark and i am not sure it actually behaves like this.

Regards,
Thorsten

[Wingman3d]

they match.

[Wingman3d]

any other thoughts on this?
could it be a memory issue that makes the camera change zoom\focal length or something like that?

[David H]

Sorry if I'm dragging up an old thread. But I just want to make a note that I have also encountered this issue, but it was not related to Vray (vray wasn't even installed).

The camera would do a vertical nodal pan on seemingly random frames. And only on the rendernodes, not on the workstations. The random pan was always the same amount which makes me feel that the 1.31 vs 1,31 could be the issue.
Our regional settings mean we use "," for decimal notation which is buggy in max (can be noticed in the trackview). So I usually change this to "." which is much more logical when you do a lot of scripting.

I'll see if I can confirm this and submit a bug report to autodesk.


..we we're using hair & fur on that project, but I don't remember if the problem was specific to the furpass.

[vlado]

Ah, good to know, thanks for the info!

Best regards,
Vlado

[Wingman3d]

Its good that you drag up this old thread, because i havent found the solution. Any news on this issue with Autodesk?
i am now having similar problems, but yet its very different. i just posted a thread here:
http://www.chaosgroup.com/forums/vbu...357#post422357
i guess i'll switch to "." just to see if it makes a difference, but i cant see that to be the solution to this new example when its ok again just by turning the render off and on again in the queue monitor.

[Wingman3d]

by the way, what would a change in the regional settings from "," to "." affect? Will i notice this in use of other programs?

[Wingman3d]

so i think i have found the solution to this.
i changed my regional settings to ".", and i'm not sure that this may have taken care of the small changes in camera angles. but lately i have also had problems with major random camera movements during rendering, as i mentioned in this thread: http://www.chaosgroup.com/forums/vbu...357#post422357
I thought maybe it could be backburner related, but i ran a lot of tests without backburner, and it still appeared.
But what i saw then when it had finished rendering was that the camera in the scene had moved. When i run backburner i usually close down the max i'm working on to save RAM. And when i am not using backburner, the active viewport has to be the one with the camera you are rendering.
So my theory is that its my 3Dconnexion SpacePilot 3D mouse that's the sinner. because when the camera is the active viewport, the spacepilot can be used to move the camera itself.
And i have experienced that the SpacePilot sometimes makes a little "jump" in the viewport, without me touching it, which doesn't matter much when its not a camera.
But what puzzles me is that these camera changes are picked up during rendering;
1. when rendering without backburner i cannot work with max, so if i wanted to couldn't move the camera. But it seems like the SpacePilot can move things anyway from "within".
2. when rendering with backburner, i close down the max with the scenefile, so only the rendernode-max is open. How can that pick up changes from the SpacePilot? I thought the whole job with all the frames was sent at once, and still if they are sent one frame at a time, how can the SpacePilot interfere with this when scene-file max is closed?

One thing is for sure, that when i removed the Spacepilot i rendered without these errors.
I would really appreciate if you could let me know if you have any similar problems.

[Bechstein]

hey wingman3d!
i've carefully read all threads were problems with randomly cam shakes occur. cause i faced with this problem too.
it's only the workstation who produce these cam shakes and after a little move all following frames are also wrong.
and here it comes: i have a 3dconnexion spaceexplorer!
after reading your last post i'll give it a try and remove the spaceexlporer before i render a sequence again.
when it comes to this i will post my experience.
with the spaceexplorer i've found another strange behaviors. if your active viewport is a vray physical camera with a shifted lence and you touch the spaceexplorer you can never undo this mistake. this cam is broken until you restart max. strange!