Good News, I finally got pyglet (and thus, cocos2d) to work! I think in the end it really was just the Graphics Drivers update. When I updated them the first time, I don't think I actually uninstalled the old one before installing the new one, so maybe that's why it didn't work. Or perhaps I didn't install the latest one like I thought.
After struggling with it more, I decided to start from scratch and used ATI's autodetect program to select the driver for me and I used that (and properly uninstalled the existing one, rebooting in between). I'm on 12.3 and all of the pyglet and cocos2d examples now work. Thanks again for the help! For Posterity and completion's sake, here's more info: >Just to eliminate obvious things: when you run those samples, you see some traceback or error message in the console window ? Sometimes it is easy to miss, because the pyglet window overlaps the console window ? When it was erroring, noisy.py did not produce any traceback or error messages in the console window. Just a black screen with "Press space to add a ball, backspace to remove" at the bottom. And I could hear the beeps everytime the invisible balls hit the walls. >Could you clarify what ati hardware have you ? The mail I answered mentioned an ATI 9650 (which should be fairly old), but a later mail states 6950 ( released dec 2010 I think ) 6950. Specifically: http://www.newegg.com/Product/Product.aspx?Item=N82E16814150524 I don't know why I keep transposing the first two digits. Additionally, I found the following StackOverflow and pyglet issue that was able to help me get pyglet working on catalyst drivers 11.8 by replacing the v2i function calls in pyglet with v2f. http://stackoverflow.com/questions/9369357/pyglet-vertex-list-not-rendered-amd-driver http://code.google.com/p/pyglet/issues/detail?id=544#c3 could come in handy in the future if AMD breaks the drivers again :/ Thanks again. Now that I can actually play with it, cocos2d is really impressing me. I'm very excited to start working with it! On Wed, Apr 18, 2012 at 10:40 AM, claudio canepa <[email protected]>wrote: > > > On Wed, Apr 18, 2012 at 12:20 PM, Johnstein <[email protected]> wrote: > >> Thank you for the reply. >> >> I installed catalyst 11.5 and ran some of the pyglet examples. >> noisy.py, animation.py, and events.py all showed blank or black screens. >> >> > Just to eliminate obvious things: when you run those samples, you see some > traceback or error message in the console window ? Sometimes it is easy to > miss, because the pyglet window overlaps the console window ? > > >> And I can't believe I left out these details: >> Win 7, 64 bit >> python: v 2.7.2, 32 bit >> cocos2d: 0.5.0 >> pyglet: 1.1.4 >> >> > Could you clarify what ati hardware have you ? The mail I answered > mentioned an ATI 9650 (which should be fairly old), but a later mail states > 6950 ( released dec 2010 I think ) > > >> I think what I'm going to do after work tonight (unless someone else >> other ideas for me to try) is to completely remove python and do a fresh >> install. In the process of trying to find a solid 2d python framework I >> installed a lot of packages and since I'm not yet a python master, perhaps >> I got something crossed up. >> >> > Seems unlikely, because pyglet graphics depends only on PIL (python image > library) package, but who knows. > > I suggest you post to the pyglet list the problems with pyglet samples, > with al the relevant details. > That list has more subscriptors, hence you have better chances of more > specific help. > > > >> Thanks again for the help so far. >> >> > Glad to help, > > claudio > > -- > > -- > You received this message because you are subscribed to the Google Groups > "cocos2d discuss" 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/cocos-discuss?hl=en. > -- You received this message because you are subscribed to the Google Groups "cocos2d discuss" 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/cocos-discuss?hl=en.
