I rendered out an animation in 640x360 with no problems. When i rendered out exactly the same in 1600x900 i got some unwanted heavy camera shaking.
The first one was with the same computer on backburner. the 1600 version used two computers. i don’t know if this is the reason?
Any idea?
I use vray physical camera.
Vray version 1.5 SP3a
Vray DLL version 1.70.00
do you have an example of the “shaking”?
Sorry, forgot to post those.
the ok one:
the shaky one:
I had the same problem in some backburner rendered animations with the same vray version on vista and xp 64 bit, max 2010.
In some frames the vray physical camera jumped a few meters up.
I wasn’t able to reproduce it so i did’t post it under bugs.
The base scene was super large with lots of geometry, particles, and proxies.
It never happened in smaller scenes so its maybe memory related?
i’m on 32bit XP, max 2009.
memory might have something to do with it? Beeing that it doesn’t happen on small format output. but it’s not a very large scene. i have a few tree-proxies though, but nothing fancy.
I noticed that when i rendered out on 1024 x 576 it also shaked, but not on the same frames. i’ll try to render out 1024 format on a single computer tonight.
I’ve had this happen before, was random though and only happened on one job.
I think it may have had something to do with the scale, but i’m not sure it was properly resolved. We just rendered those frames again as it only happened a couple of times.
I think such bugs are a nightmare to fix if you can’t reproduce them easily.
I rendered the same scene again and there was not a single jump this time.
Its a ghost bug ▼↔▼
how far from 0,0,0 is your camera?
There has been a max issue since v2 or v3 that if your camera is too far from 0,0,0 then it starts shaking.
its about (1m,2m,1m) from center of the grid.
one unit = 0,01m
display unit = meters
i ran a series of 1024 renders on backburner, but with only one pc. the problem isn’t showing.
could the problem be with backburner? i have used two pc’s. both with XP. been using these for 1 year now, never seen this before.
on a short note : beeing far from the origin is not a max bug or issue but a general precision problem with floating point math (basically the more digits before the comma the less digits behind it = lower precision for bigger numbers).
As a second note maybe different locale settings on the renderslaves ? this might lead to inconsitencies if comma or dot are used as delimiters.
Just a shot in the dark.
Regards,
Thorsten
what kind of local settings do you mean?
sounds a bit strange that this all of a sudden should cause problems.
locale, not local 
The language settings wich also determine if it is 10.5 or 10,5
as said was just a shot in the dark.
Regards,
Thorsten
i dont know anything about these settings.
But i have run another test now, and it is definetly one computer that renders out the problem frames. But not all frames are bad. but what i noticed now was that the first few frames was ok, but later at night it started rendering bad ones. I run virus scan and backup at night, so it might be a memory issue.
(I’m on 32bit XP, with 4Gb Ram)
new test: Private Group Photo & Video Sharing
It seems like the camera changes zoom, focus distance, or aperture or something like that.
Maybe Vlado or anyone can answer if they know of any bugs like this?
it does sound like the region settings of one of the machines is different as thorsten has mentioned
Which settings are these, and where do i change them?
But wouldn’t all the frames from that pc be bad then? And not only a few?
go to your control panel, regional and language options and just make sure that the different machines match each other
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
they match.
any other thoughts on this?
could it be a memory issue that makes the camera change zoom\focal length or something like that?
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.