Read Me or Die
wezu on 2013/09/07 21:39
of Wezu
In his game You get to pilot a futuristic spaceship in an asteroid filed between the Moon and Earth. If you’re asking why is there a asteroid field between the Moon and Earth… well, it’s complicated and it’s the future after all – a lot of things could happen.
Your goal is to make it across the asteroid field as fast as you can without running out of fuel. A set of ‘gates’ and some ‘green flying things’ will mark the way.
Move your mouse to rotate the camera and the mouse-wheel to zoom in and out.
The left mouse button is there to fire up the engines and the right mouse button for reverse thrust.
Use W-S-A-D keys to rotate your spaceship, but keep in mind that the direction you actually movie will only change when the engines are on!
In the top left corner of the screen you will see a timer, the faster you can get to the other side of the field the better (try to beat 3 minutes!)
In the lower left corner there’s the fuel gauge (a set of lines), when all the lines are faded you will run out of fuel and most likely crash. Next to it you will find a display showing your current speed.
Refer to the config.txt file for all the configuration options.
You will probably need a ‘modern’ computer to run this, I didn’t make all the needed optimalisations duo to lack of time and a change of concept around day #3.
To run the sourcecode you will need the Panda3D SDK: http://www.panda3d.org/download.php?sdk&version=1.8.1
When running the binary for the first time you may (or may not) need a internet connection, to download some engine components.
When running from the multiplatform p3d file you will need the Panda3D runtime installed:
http://www.panda3d.org/download.php?runtime
The music is by Mathew Pablo: http://www.matthewpablo.com/
The voice is based on the Google Voice: http://ctrlq.org/listen/
(log in to comment)
Comments
reidrac on
2013/09/09 18:20:
Install complete.
A window opens, just black and nothing happens. Linux 32-bit :(
wezu on
2013/09/10 19:07:
I could be that your gpu doesn't support some advanced stuff I put into the game. First thing try in the config.txt setting 'bloom 0' and 'lens-flare 0' then I'd try 'antialias 0' and 'use-shaders 0' if all else fails.
If that's still no good... would you be willing to run it from sourcecode (Panda sdk needed for that, link above)? The message seems to complain about not being able to set some windows properties - you could try to comment-out that part - it's line 43 in main.py just change wp.setFixedSize(True) to #wp.setFixedSize(True)
I don't have a Linux machine at this time, so it's kind of hard for me to tell what's wrong.
reidrac on
2013/09/10 19:18:
I disabled "all" but nothing. Basically it hangs (in fact I have to kill the process). I was a little bit WAT after downloading 145 something MBs of runtime!
So your dev platform is Windows?
reidrac on
2013/09/10 19:19:
wezu on
2013/09/11 09:40:
otus on
2013/09/11 10:05:
otus on
2013/09/11 10:10:
wezu on
2013/09/11 14:56:
It doesn't look like I'm going to score high if the game fail to run :(
reidrac on
2013/09/11 15:02:
This is just my 4th PyWeek but it looks like the entries using plain PyGame or pyglet tend to be more portable. Panda3D will get there too, obviously :)
otus on
2013/09/11 18:08:
(I've hidden my username and home directory, but that's it.)
wezu on
2013/09/11 20:00:
Adding audio-library-name null to the config.txt was my last idea.
I'd rather have a low but honest and constructive grade then 'did-not-run', but well, not much I can do, I'll ask around the Panda3D forum.
jerith on
2013/09/17 18:55:
You can make ship (and camera) control much friendlier by rotating relative to the local frame of reference instead of the absolute frame. Instead of setting an absolute angle like this:
self.ship.setH(self.ship.getH() + 140 * time)
set an angle relative to the object itself, like this:
self.ship.setH(self.ship, 140 * time)
Panda3d will take care of the rest.
wezu on
2013/09/18 15:24:
jerith on
2013/09/22 08:36:
By setting heading/pitch/roll relative to the object itself you're using axes based on the current orientation of the ship. This means that a change in heading always has the same apparent effect no matter where the ship is facing.
If you use the absolute axes, all your rotation is relative to the starting orientation of the ship instead of the current orientation. This means that a change in heading has different apparent effects depending on which direction you're facing, because the ship's axes don't match the absolute axes.
The most obvious effect of this is that if you do a 180 degree pitch change (which you can do from the starting position by holding up or down until you're facing the sun instead of the asteroids) and the make heading changes, left and right appear to be reversed because the ship's axes are upside down relative to the absolute axes. If you only make a 90 degree pitch change the axis difference means that the absolute heading axis is aligned with the ship's roll axis and the heading controls spin the ship instead of turning it. (The pitch axis always behaves as expected because without rotating around the roll axis you're never breaking its alignment between the two sets of axes.)
Why not just say it's "space junk" (AKA satellite debris, which is a growing problem and could be possibly appear like an asteroid field in the future)?
But still, sounds cool !