Ratings (show detail)
10% of respondents wished to disqualify the entry.
|4.2 MB||alex||2007/04/07 19:15|
|99.1 KB||alex||2007/04/06 01:53|
A large-handed baddie.
|42.0 KB||alex||2007/04/04 16:04|
They go up...
|16.9 KB||alex||2007/04/01 02:22|
Some after-deadline fixes were made to pyglet. These fix the core dump on Windows during the credit sequence, and the mouse inversion and miscellaneous warnings on Mac. You can get the patched game to resolve these issues.
Some screenshots from the completed game:
The definitive PyWeek/delta-v/pyglet post-mortem to come, following sleep recovery. Looking forward to playing all the other games!
The pink structure is just the collision geometry at the moment; replacing this with the real visual model will be today's focus.
Also managed to add the cutscene, health display, a crosshair (ok, that was all of 4 seconds work), the skyboxes and particle emitters.
Level design happens
The game won't really be playable until the baddie AI is in, which I'm thinking is going to be tricky; don't really know how to go about it.
Used a spare hour in between classes today to draw up the baddie model:
As of tomorrow I'm on holidays so hopefully I'll catch up.
Almost on track
On the gameplay side of things, a bit of refactor means I now have a really clean split between game code, graphics code and the fps dynamics code... this is something that's always eluded me in the past. (In my previous two pyweek entries the "gameplay" was bolted on only in the final few hours).
Gameplay now lets the player shoot the baddies (not with a gun though... I'm not that predictable), bump into the baddies (ellipsoid/ellipsoid) and lose health.
I initially tried to do the shooting test with a ray/ellipsoid intersection, but couldn't get it working. Then I (slowly, I know) realised that I'd need to test against the walls as well. Then (finally) I realised that I could just use the selection buffer, which is really cool (I've never used it before).
Schedule for the rest of the week:
- Weds: Draw up the levels, implement the rest of the game logic
- Thurs: Make it pretty.
- Fri: Menu screens, more prettiness.
- Sat: Package/test. Futilely attempt to implement pyglet sound on Mac and Windows (Linux is already implemented, sort of).
- Sun: Deadline is 10am for me, just enough time to wake up and accomplish nothing.
Things that go bump.
Today I rewrote all the collision and it works perfectly: line-segement/polygon collision for finding the floor and ellipsoid/polygon collision for bumping into things. The dynamics need a bit of tweaking to feel like a "real" FPS, but all the basics are there: ramps, stairs, sliding along walls, jumping, falling, hitting your head on the ceiling, etc.
I also came up with a game design today, which makes me happy. I'm not going to share it yet though, 'cos it's a surprise :-)
[To the commentators: it's a model of the stairs, not procedurally generated.]