| |||||||||||
PyWeek - Windows Vista & OpenGL.. OUCHI've heard the rumors about Vista and openGL, but this is pretty unbelievable.. A geforce 8800GTS on a core2 duo with nvidia's latest beta drivers is getting 14 frames per second on our game, while a radeon9800 on an athlon xp 2500 is getting the full 60. I can understand them having to adapt to a new driver model, but that seems a little bit extreme! Has anybody else experienced Vista silliness? *SLEEP NOW!*— skaro on 2007/04/07 08:00 of Blancmange: Kid Bandyhoot's Adventures (in cylindrical coordinate space) Comments: (log in to comment) |
Last Challenge
September 2008 [entries, ratings] Previous March 2008 [entries, ratings] September 2007 [entries, ratings] > April 2007 [entries, ratings] September 2006 [entries, ratings] March 2006 [entries, ratings] (June 2006) August 2005 [entries, ratings] Not logged in Login | ||||||||||
By skaro on 2007/04/07 08:05:
*the radeon/athlon is running XP by the way*By skaro on 2007/04/08 16:10:
Seems to work when I use an older PyOpenGL.. ha! Ohwell!By lucio on 2007/04/11 17:32:
i could not make the game run on macosx, any ideas?setEngine() File "/Users/lucio/Desktop/pyweek-4-finals/Blancmange/KidBandyhootsCrazyAdventures-v1.0/lib/main.py", line 46, in setEngine gameEngine= glengine.GlEngine() File "/Users/lucio/Desktop/pyweek-4-finals/Blancmange/KidBandyhootsCrazyAdventures-v1.0/lib/glengine.py", line 44, in __init__ self.gameMap=GameMap() File "/Users/lucio/Desktop/pyweek-4-finals/Blancmange/KidBandyhootsCrazyAdventures-v1.0/lib/gamemap.py", line 15, in __init__ self.initLevel1() File "/Users/lucio/Desktop/pyweek-4-finals/Blancmange/KidBandyhootsCrazyAdventures-v1.0/lib/gamemap.py", line 135, in initLevel1 targetFunc=enemyactor.EnemyActor.targetPlayer) File "/Users/lucio/Desktop/pyweek-4-finals/Blancmange/KidBandyhootsCrazyAdventures-v1.0/lib/enemyactor.py", line 179, in __init__ targetFunc=CannonActor.cannonTargetFunc, TypeError: __init__() got multiple values for keyword argument 'targetFunc'By erik on 2007/04/11 17:59:
The handy wiki: http://nekapuzer.at/wiki/Pyweek4LinuxTold me to remove **kw from line 179 from enemyactor.py.
(Python 2.4 vs 2.5 problem maybe?)
By skaro on 2007/04/11 23:57:
I'm thinking it is a 2.4 and 2.5 issue.. We developed on 2.4, and it seems like it might be a bit more lenient about the keyword argument duplication.. Thanks for the bug reports, these will make it into a post judging release :)By alecu on 2007/04/13 04:34:
Small bug, when an enemy is too close:Traceback (most recent call last): File "run_game.py", line 12, in ? main.main() File "/home/alecu/Desktop/pyweek-4-finals/Blancmange/KidBandyhootsCrazyAdventures-v1.0/lib/main.py", line 81, in main gameEngine.doFrame() File "/home/alecu/Desktop/pyweek-4-finals/Blancmange/KidBandyhootsCrazyAdventures-v1.0/lib/glengine.py", line 101, in doFrame self.gameMap.thinkAll() File "/home/alecu/Desktop/pyweek-4-finals/Blancmange/KidBandyhootsCrazyAdventures-v1.0/lib/gamemap.py", line 42, in thinkAll actor.think() File "/home/alecu/Desktop/pyweek-4-finals/Blancmange/KidBandyhootsCrazyAdventures-v1.0/lib/enemyactor.py", line 55, in think self.volleyFunc(self) File "/home/alecu/Desktop/pyweek-4-finals/Blancmange/KidBandyhootsCrazyAdventures-v1.0/lib/enemyactor.py", line 100, in singleVolley self.shootFunc(self,self.targetFunc(self)) File "/home/alecu/Desktop/pyweek-4-finals/Blancmange/KidBandyhootsCrazyAdventures-v1.0/lib/enemyactor.py", line 67, in targDirPlayer playerDir = sign(circv(self.position, self.map.playerActor.position)[0]) File "/home/alecu/Desktop/pyweek-4-finals/Blancmange/KidBandyhootsCrazyAdventures-v1.0/lib/vecops.py", line 56, in circv return dirv(a,b) File "/home/alecu/Desktop/pyweek-4-finals/Blancmange/KidBandyhootsCrazyAdventures-v1.0/lib/vecops.py", line 70, in dirv mag=1/hypot(xd,yd) ZeroDivisionError: float divisionBy donal.h on 2007/04/16 19:44:
alecu,If you wouldn't run through the enemies right as they are targeting you, then it wouldn't be a problem. Thanks for the bug report. If player position is the same as the enemy's position at the exact time that the enemy decides to shoot then it will most definitely divide by zero and that's mathematical challenge. It's fixed in our dev stream as of a couple of minutes ago though.
Thinking of our dev stream, it has actually been worked on a little post-comp. Hoping to maybe even build a second level and maybe some more enemy types. I'd like to get some powerups too. Fun stuff. I've even made a couple sprites and they don't look aweful.