sorry for stating the obvious Jim. i should have known that's what you had used. it's kind of hard to help w/o code to look at.
one thing i did notice is that the kernel processing percentage for the SS goes from about 1/2 to 3/4 when selecting the "limit framerate to 60" option. so the app is doing "something" many more times "inside" the os with the option on than w/o it. if that's the Sleep call, then something must be causing it to stay inside the api code but not actually "sleep".
now i can see why you say Prolific has been working on this for a while. weird!
|