@Banshee,
NO.
At some frequencies its right, but most of the time it cannot be garenteed to have waited the lenght of time you wanted. (but its a piddleing difference, so... not really important.
@GFK, I know you have gone for 10HZ, but why not tie the timer to the screen sycn. OK so you would have a lot of "Null" loops, but you are more lickly to keep sync. I only ask, because I use a timer to flip, so cannot use sync, but if I was fullscreening, then I would concider the screen sync to be my timer and run from that. (if you see what I mean, I either tell the comp when to sync, or take the sycn to tell the program what to do)
Do Timers() bypass/correct this in some way
NO.
At some frequencies its right, but most of the time it cannot be garenteed to have waited the lenght of time you wanted. (but its a piddleing difference, so... not really important.
@GFK, I know you have gone for 10HZ, but why not tie the timer to the screen sycn. OK so you would have a lot of "Null" loops, but you are more lickly to keep sync. I only ask, because I use a timer to flip, so cannot use sync, but if I was fullscreening, then I would concider the screen sync to be my timer and run from that. (if you see what I mean, I either tell the comp when to sync, or take the sycn to tell the program what to do)