Early demo game needs some testing
Pages: 1 2
Terry Swanborough (61) 152 posts |
@Druck Thanks for trying the program,the output from the Vsync program as below:- Using a PI2B+ Perhaps I’m barking up the wrong tree but I get fairly consistent results Getting average Vsync Time average Time in uS is 16690 (59.9161174Hz) Upper Limit (average+3%) 17190 Calculating Vsyncs Please Wait! 60 17294 60 17310 60 17316 60 17317 60 17294 60 17300 60 17312 60 17285 60 17293 60 17339 60 17353 60 17286 60 17329 60 17339 60 17346 60 17326Average time between Vsync Errors 60Hz |
Terry Swanborough (61) 152 posts |
@DavidS Ok thanks for the reply. I think its worth trying to finish the BASIC version, as nobody, (so far) Thanks to all that tried the demo. |
Andreas Skyman (8677) 170 posts |
Late to the party, but here are my results using a Pi1:
It varies a little bit though, roughly betwenn 16 and 18 errors. |
Terry Swanborough (61) 152 posts |
I tried another PI2B+ in work today and also got errors If you look at the output when the Vsync varies the incorrect Vsyncs The variation might be the BASIC program it was something I knocked up on the quick. I meant to try the program on the Iyonix I have in work but I had real work to do so got distracted :-) I have an Iyonix here at home I will set it up and try it. Like I said before I get no errors on the Titanium?. Perhaps its only certain PIs that have the Vsync error?. Its just very strange that scanning a 1000 Vsyncs only shows errors @ approx the refresh rate?. |
Terry Swanborough (61) 152 posts |
It locks on to the Vsync the way it works is very simple:- FOR I%=0 TO 1000 In the FOR loop is counts the number of Vsync between each incorrect reading and also records the time?. |
Pages: 1 2