(06-28-2009, 05:27 PM)Iulius Wrote: reason : the function where framelimiter sits is now called more often then the cpu actually calculated a frame as more frames are pushed out when only 1 frame has been calculated.
Oh
So are you going to fix it?
Obviously you need to throw the code in where the frame actually starts...