Replies: 2 comments 2 replies
-
For some reason I cannot see what asdqwe told you, but I played with SetTargetFPS quite a lot. My advice: call SetTargetFPS(60) in the beginning. Otherwise 1) if you don't use FLAG_VSYNC_HINT you will see multiple screen tearing (on multiple levels on the screen) if your app is simple enough and your GPU is powerful enough 2) if you do use FLAG_VSYNC_HINT then you will most likely see actual FPS worse than 60 (assuming your monitor refresh rate is 60) plus some microstuttering (I kind of understood why it happens but not well enough to try to explain it, just test it for yourself). SetTargetFPS basically adds additional wait to cap FPS at whatever value you pass. But you can use frameTime for physics calculations regardless of calling SetTargetFPS. |
Beta Was this translation helpful? Give feedback.
-
What does that function do exactly?
is it more of a "maximum" allowable fps?
or does it dynamically change the resolution/quality to maintain the target fps so it doesnt go above or below?
also, what happens if I do not set a target fps?
Beta Was this translation helpful? Give feedback.
All reactions