I've updated the basic physics and gameplay of cellular to produce a decent playable game. This includes basic movement, enemy creation, object collision detection, vector/vector collision physics, and user input. My next goals are to refactor my code, hopefully by the end Wed PST. Thur will be graphics and more complex algorithms, and Fri will be Title Screen, Story, packaging, and User Presentation. I'm hopeful for a completion date by the deadline.

Once you get you simulation up and running, you stop programming, and waste all your time messing with the world and saying "Neat!"

Just a random thought while I was programming: Hopefully pyweek.org will not be slashdotted any time soon, or else this competition would be ruined due to the Slashdot Effect- pyweek would most likely be knocked offline by all those visits for about a day; if pyweek is slashdotted on the last day, no one would be able to upload their submissions :-(

I have no will to write stuff, too tired, I'll post in the morning. Just a little comment - TreeForm and team are actually managing an MMORPG...That's SICK...Keep on the good work (Not only their team, everyone :))...

I can't seem to get the steering for my ship to work right. Here's the problem:

1. I want to use glRotate() to rotate the ship around the y-axis a certain number of degrees so that the ship faces the direction (in the x-z plane) it's traveling.
2. I have two vectors: the direction vector represents the direction I'm currently going, and the goal vector represents the direction I want to go.
3. I want to calculate the angle (in degrees) between the two vectors. This is the angle I need to rotate the ship.

Here's how I'm doing the calculation:

   old_direction = direction.normalize()
   direction = goal.normalize()
   angle = math.acos(old_direction.dot(direction)) * (180.0 / 3.1415927)

   if steer_left:
      rot.y += angle * -1
   else:
      rot.y += angle

   glRotate(rot.y, 0, 1, 0)
   # Draw the ship

When I do this, the rotatation of the ship lags behind the direction it's actually moving. Any ideas about what I'm doing wrong?

Century of the fruitbat is proud to announce the moment you have all been waiting for - the very first super special early release trial of our wonderous crowning acheivement "Up Up and Away," starring the stickmen performance troupe and paid for by your favorite restaurant in the multiverse: "Harga's House of Ribs". You know you want some.

The link for this amazing masterpiece is located below, but as this is a special early preview version, we ask that you keep it secret - we don't want to build up hype too much yet.

secret link, don't click unless you belong to the fruitbat secret society

I've started coding, using the GooeyPy library by Joey Marshall. I haven't gotten very far yet...

It's the end of Day 3, and I've only One other improvement I'd really like to do, but know I won't have time, is to tart the graphics up a little. Some prettier platforms, a background and a couple of animated sprites for the player and the level exit would make a world of difference. That's what I'd have done with the remaining time if I had the chance.

That'll teach me not to arrange to visit family during PyWeek! Need to prioritize better! ;)

Not everybody wants to risk getting distracted during the week by playing someone else's prototype, which has no doubt just become playable enough to be vaguely fun (otherwise why would they upload it?). Also, I reasoned that anything that gets our little contest a tiny amount of free publicity can't be a bad thing.

Here we go then: instead of uploading a prototype of my game, I recorded myself playing for a minute or so using XVidCap, and uploaded it to YouTube here. The actual game is slightly faster (XVidCap CPU usage gets in the way) and smoother, obviously, but there you have it.

Now, if I can tear myself away from flying through tunnels for long enough, it's time to add some enemies. Oh, and a respawn action would be nice, too. ;)

As usually it is fun to code game engine. I hope that the needed fun gameplay will come later (somehow).