It shouldn't.
Leaving off the hertz is the same as specifying 60
Adding 0 is supposed to take the default hertz for that particular resolution on your machine.
This might help...
skunk wrote:
Ideally choosing a refresh rate of zero will pick the host os desired refresh rate for that resolution, -not- 60.
If I wanted 60, I'd put 60 in the box, wouldn't I?
Earlier, skidracer wrote:
skunk, the docs need updating, if you set the hz value in Graphics to 0 (it defaults to 60) windows WILL pick the default refresh rate for that resolution.
Graphics 640,480,32 is the same as Graphics 640,480,32,60 which is not the same as Graphics 640,480,32,0
Sybixsus wrote:
It's still decidedly unclear to me exactly how to do this properly, as it's also unclear exactly what the hz setting is doing. Is it setting the monitor hertz? Is it setting up BMax internal timing? Is it doing both? From the comments I've seen from BRL and users, it appears to be doing both.
Earlier, marksibly wrote:
It tries to use vsync if possible. If not, it disables vsync and uses an internal timing system. This makes for much smoother graphics than if the vsync is left enabled and 'fighting' the update rate. It also provides surprisingly flicker-free results for systems with no vsync.
See mod/brl.mod/glmax2d.mod/glmax2d.bmx for how it all works.
This only applies to the Graphics/Flip mechanism. If you want to avoid the timing mechanism, use bglSwapBuffers instead of Flip.
taken from
Proper Game Timing