Thanks, Juan. So, I started having problems again, but I've figured it out. Vsync was working temporarily, but after a restart, it was locking the framerate at 32 fps. Kind of odd, I thought. I couldn't get it to run at 60 fps, where it should've been. I tried putting it in fullscreen. Tada! 60 fps. So I thought it was just a quirk of the window or something. But no, soon the fullscreen mode was running at 32 fps. What the hell was going on?
It turns out that the Nvidia control panel defaults to letting applications choose to run on either the GPU or CPU. For whatever reason, the script was arbitrarily choosing between the two. On the CPU it locks it at 32 fps (I have no idea why...). Changing the setting to prefer to use the GPU causes it to run correctly at 60 fps. On Friday, June 20, 2014 12:28:22 PM UTC-4, Juan J. Martínez wrote: > > On 20/06/14 16:25, Ryan Mailey wrote: > > Okay, so this is very strange indeed. > > > > I sat down today and opened up my script. I wanted to look at it after > > sleeping on the problem. Nothing unusual. I tried running it again, > > expecting vsync to still be messing up. It works! > > > > Wat. > > > > I didn't change anything and it is just spontaneously working now. :/ > > Cool! > > I'm glad it's working now :) > > Regards, > > Juan > > -- > jjm's home: http://www.usebox.net/jjm/ > blackshell: http://blackshell.usebox.net/ > -- You received this message because you are subscribed to the Google Groups "pyglet-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/pyglet-users. For more options, visit https://groups.google.com/d/optout.
