On Wed, Oct 28, 2009 at 8:45 AM, Stu.Axon <[email protected]> wrote:
> > Hi, > I had the same problem but couldn't find your report. I've reported > it on the cocos list as it affected 51 of the cocos demos that I > tested. > > > http://code.google.com/p/los-cocos/issues/detail?id=130&colspec=ID%20Type%20Status%20Priority%20Milestone%20Owner%20Summary%20Component > > On Sep 7, 10:16 pm, Dave Horner <[email protected]> wrote: > > Hello there, > > > > I actually first posted this question cocos2d mailing list, but I now > > realize this more looks like a pyglet issue... > > > > I was going through the cocos2d samples today and I am getting the > > following > > in tetrico. > > The tetrico game starts fine, options, and score work as they should. > > (though I do not hear any sounds) When I select 'New Game' it gives > > me this: > > > > C:\working\cocos.samples.trunk\tetrico>python tetrico.py > > Traceback (most recent call last): > > File "tetrico.py", line 256, in <module> > > director.run( scene ) > > File "C:\Python26\lib\site-packages\cocos2d-0.3.0-py2.6.egg\cocos > > \director.py", line 287, in run > > event_loop.run() > [ snip extralong intermediate traceback ] > > File "build\bdist.win32\egg\pyglet\app\win32.py", line 63, in run > > File "build\bdist.win32\egg\pyglet\gl\lib_wgl.py", line 94, in > > __call__ > > File "build\bdist.win32\egg\pyglet\gl\lib.py", line 105, in errcheck > > pyglet.gl.lib.GLException: None > > > > I'm running windows vista 64 with python2.6 and using easy_install > > cocos2d. I am running a 32 bit python...on my vista64. > > > > C:\working\cocos.samples.trunk>python > > Python 2.6.2 (r262:71605, Apr 14 2009, 22:40:02) [MSC v.1500 32 bit > > (Intel)] on win32 > > > > It is strange cause it does work quite well in some ways...for > > instance demo_sprites.py works great. > > > > I'm excited to get this resolved so I can start on a game. :) > > > > Thanks so much! > > --davehttp://dave.thehorners.com/ > not a dev but: just in case, you can try with the latest pyglet from svn: http://code.google.com/p/pyglet/source/checkout and, probably, running the pyglet tests an examples could signal with more approximation where the problem lies ( and give shorter tracebacks to investigate ) -- claudio --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "pyglet-users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/pyglet-users?hl=en -~----------~----~----~----~------~----~------~--~---
