I'm not sure if it's OK to resurrect a year old thread, but I have the same issue described above.
The code I am trying to run is the sample samples/demo_sprites.py When it runs, I only see the text, not the sprites. I can advance the tests, but I don't see anything: screenshot-> http://i.imgur.com/fS8fJ.png When I run the samples/demo_flag3d.py program, it all works. screenshot->http://i.imgur.com/ls8qw.png I just updated my video card driver, radeon 9650, but I didn't see any difference. the tetrico demo seems to work. I can play it, though I don't see any boundaries at the sides, so I'm not sure if I'm missing something there. screenshot->http://i.imgur.com/7sMFJ.png I downloaded cocos2d less than a week ago and I haven't changed any of the source code. Any thoughts on how to go about debugging this? Thank You On Wednesday, April 20, 2011 5:35:50 AM UTC-7, Enerccio wrote: > > Nevermind, but thanks for the reply. > It was the fault of the open source radeon driver. > Now it work well! > > On Apr 16, 5:37 am, claudio canepa <[email protected]> wrote: > > On Fri, Apr 15, 2011 at 10:40 PM, Enerccio <[email protected]> wrote: > > > Hello. > > > I have trouble with cocos. > > > I am unable to get the sprite to show on the screen at all. > > > The director will run, it will show empty screen, then even transition > > > seems to be working (I get the pause for the duration), yet the screen > > > is black (with only FPS updating). > > > > > Here is my code, did I miss anything with the layer?? > > > > >http://paste.pound-python.org/show/5272/ > > > > Is hard to tell without a runable sample, I dont see how you are > > initializing the cocos director, or launching the first scene, or how > you > > instantiate your custom scene. If you can provide a runnable sample it > would > > help heaps to diagnose. > > > > Also, how you launched your app ? from an operating system console, > typing > > something like > > $python script_name.py > > ? > > > > Any traceback message in the console ? > > > > Seems that the flow will go to the line > > raw_input() > > > > that is for console input, which generally dont mix well with windowed > > aplications. > > What happens if you remove that ? > > > > Also I noticed you dont specify z when adding the background and the > sprite > > to the scene. What if you specify z=0 for background and z=1 for sprite > ? > > > > > I also tried just this in the python idle: > > >http://paste.pound-python.org/show/5273/ > > > > > Which didnt work too. > > > > Interactive interpreters are tricky to interact with other windowed > > applications, generally a fight between the repective events loop breaks > > all. > > > > If you want some interactive exploration for cocos, you can try the > built in > > InterpreterLayer: > > start a script, give ctrl+i , this brings up a translucid layer with a > > working interpreter. > > you could explore: > > > > >>>director > > > > < cocos.director.Director object at ....> #this is the current director > > instance > > > > so>>>director.scene > > > > will bring the current scene, from there you can explore at will > > > > -- > > claudio -- You received this message because you are subscribed to the Google Groups "cocos2d discuss" group. To view this discussion on the web visit https://groups.google.com/d/msg/cocos-discuss/-/T_YPa_400hkJ. 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.
