# Should the frame rate be consistent or is it normal for it to jump around?

As I commented on a post, I started wondering if it was correct or not (the comment, not the answer). And I'd like to straighten that out.

Although not needed as info, here's the link to the question: Scene management for 3D editor

My comment: "Wouldn't mind that much about the framerate, as long as it stays above 60. you can get away with 30 even."

Still I think if the frame rate is over 30, the real time rendering stays as a good animation. But sometimes I read that people restrict the render() to 60fps or 30fps for performance. This could/would remove all unneccecary calculation wich we can't see anyway. Although true, they (sometimes) claim it is an optimization.

When a scene will render more objects, the fps will drop. Think that is normal.

So what's the deal with fps, should it stay more or less the same even when you turn the camera 90 or 180 degrees, or only when keeping (almost) the same view?

• Hey, update() has nothing to do with rendering. Did you mean render() or draw()? – jcora Aug 5 '12 at 11:47
• The render(), you're right although the context would be the same. Will update() it so the question renders() correct. – user18479 Aug 5 '12 at 11:52
• Cool. (Also, what do you mean "the context would be the same"?) – jcora Aug 5 '12 at 12:59
• The update is the part wich does the culling and affects the fps, the update just merely draws the scene. However, those cliams I mentioned are about the restricting the update. But the two functions comes in - imho - a pair where you first collect information (update) and then send (render) the data. – user18479 Aug 5 '12 at 18:27