PyWeek - Python Space - feedback
Fun | Prod | Inno | Disq | N/W | Comments |
---|---|---|---|---|---|
1 | 1 | 1 | yes | <pre> File "run_game.py", line 573, in <module> |
|
2 | 2 | 2 | pyweek solo is impossible if you dont limit yourself |
||
1 | 1 | 1 | yes | Game did not work for me. |
|
1 | 1 | 1 | yes | The screen flickered and it printed out: |
|
1 | 1 | 1 | yes | "Fatal Python error: (pygame parachute) Segmentation Fault" System - Ubuntu 8.10 amd64. Ran |
|
1 | 2 | 1 | I don't know why, but game was running too slow to be playable. |
||
1 | 2 | 2 | Had to change several calls to glEnable and glDisable to glEnableClientState and glDisableClientState (the ones for vertex arrays, etc.) to get it to run. Afer that it ran at about 4fps on my system (MacOSX 10.4, PPC G4, ATI Radeon 9000 Pro). |
||
3 | 3 | 3 | yes | python run_game.py |
|
1 | 1 | 1 | Debugging was kind of fun and lasted a good while (you have to add "OpenGL.GL.glDisable( OpenGL.GL.GL_NORMAL_ARRAY )" to draw_rectangle() to avoid crash on start on my Windows XP and glScale in displayer() has to be changed to glScalef to avoid crash later on), but the game itself was a letdown. |
||
1 | 1 | 1 | yes | C:\Games\pyweek\May2009\extracted\ohmg>python run_game.py |
|
1 | 1 | 1 | yes | Game tries to start but python crahses right away (no traceback, sadly). Python 2.5, Pygame 1.8.1, WinXP. - No Dependencies were listed in the readme, so I assume that I had all I needed. |