PDA

View Full Version : Is Maya stupid ?


Winner
08-18-2006, 08:37 PM
I have a simple creature scene im working on right now...

I put the playback settings to 'play every frame' and i get a nice clean 30.8 fps.

I then put the settings on 'realtime 30fps' and i get a crap, choppy, 18 fps..


where is the logic in that ?

StefanStavrev
08-18-2006, 09:14 PM
Not sure what your problem is, but maya is definetly not stupid :)

RobertoOrtiz
08-18-2006, 09:27 PM
I would not let Maya do my taxes, but it is definetly not stupid.

:)

Anyway can anyone give the man a hand?

-R

Winner
08-18-2006, 09:35 PM
haha sure.. I`m a shameless maya fanboy so you dont need to tell me...

i just dont get whats going on under the hood there ?

as i understand it, `play every frame` is where maya will essentially try and playback consecutive frames, at the fastest frame rate in can reach, for every calculation needed in each frame...

whereas, 'realtime 30fps' will drop frames, so maya will playback at that actual rate at the expense of those missed frames.

so then... why the hell does it play totally smoothly at 30.8fps on `play every frame`, but then drop to 18fps on `realtime 30fps` .. when its just shown me its perfectly able to playback at my desired frame rate ?

azshall
08-18-2006, 09:36 PM
I have a simple creature scene im working on right now...

I then put the settings on 'realtime 30fps' and i get a crap, choppy, 18 fps..


where is the logic in that ?

Maya only does what its told :) ... If its getting stupid instructions, then they must be coming from a stupid source ...
:shrug:

Winner
08-18-2006, 09:56 PM
lol azshall,

but all im doing is choosing a preference setting, theres no stupidity in that .. theres nothing I can actually be doing wrong there...

Jozvex
08-18-2006, 10:11 PM
It depends on what's in your scene!

Some things like particles/dynamics/fluids, jiggle deformers or probably some other things rely on the previous frames information to move on. In skipping frames they perhaps have to think harder in order to give the correct result?

That would be my guess anyway.

Exo7
08-18-2006, 11:45 PM
Me think that's because at full throttle your computer delivers 30.8fps, but adding a constraint puts a deadline in calculations (e.g. drop frames). With a faster proc that should'nt happen for the same scene. Me thought.

CGTalk Moderation
08-18-2006, 11:45 PM
This thread has been automatically closed as it remained inactive for 12 months. If you wish to continue the discussion, please create a new thread in the appropriate forum.