1. You need the libsdl, libsdl-mixer, libsdl-image, and libsdl-gfx libraries installed via your distribution's package manager. 2. If the game complains about libsdl_gfx not found, it will give you the option at the command line to choose between several restarts. Choose CONTINUE and it should work. 3. If you get errors about paths and configuration when trying to start up, see these notes for a fix. In particular, you can add a line like:
to a file called .xe2rc in your home directory. We are working on fixing this bug. 4. If you get no sound, you may need to install the pulseaudio version of SDL-MIXER from your distribution's package library. This will replace the raw ALSA version of SDL-MIXER and fix the problem. The package name you want on Ubuntu Karmic is libsdl1.2debian- pulseaudio 5. If you still can't get any of the binaries running, or if there is no binary for your system, see the developer's install guide for instructions on making your own binary.
> 1. You need the libsdl, libsdl-mixer, libsdl-image, and libsdl-gfx > libraries installed via your distribution's package manager. > 2. If the game complains about libsdl_gfx not found, it will give > you the option at the command line to choose between several restarts. > Choose CONTINUE and it should work. > 3. If you get errors about paths and configuration when trying to > start up, see these notes for a fix. In particular, you can add a line > like:
> to a file called .xe2rc in your home directory. We are working > on fixing this bug. > 4. If you get no sound, you may need to install the pulseaudio > version of SDL-MIXER from your distribution's package library. This > will replace the raw ALSA version of SDL-MIXER and fix the problem. > The package name you want on Ubuntu Karmic is libsdl1.2debian- > pulseaudio > 5. If you still can't get any of the binaries running, or if there > is no binary for your system, see the developer's install guide for > instructions on making your own binary.
> > 1. You need the libsdl, libsdl-mixer, libsdl-image, and libsdl-gfx > > libraries installed via your distribution's package manager. > > 2. If the game complains about libsdl_gfx not found, it will give > > you the option at the command line to choose between several restarts. > > Choose CONTINUE and it should work. > > 3. If you get errors about paths and configuration when trying to > > start up, see these notes for a fix. In particular, you can add a line > > like:
> > to a file called .xe2rc in your home directory. We are working > > on fixing this bug. > > 4. If you get no sound, you may need to install the pulseaudio > > version of SDL-MIXER from your distribution's package library. This > > will replace the raw ALSA version of SDL-MIXER and fix the problem. > > The package name you want on Ubuntu Karmic is libsdl1.2debian- > > pulseaudio > > 5. If you still can't get any of the binaries running, or if there > > is no binary for your system, see the developer's install guide for > > instructions on making your own binary.
>Windows users: >Right now there is no fancy installer, but you can still download and run the game with a few clicks. >First, your browser will probably ask you whether to Open the download, or Save it to disk. CHOOSE SAVE TO DISK and put it wherever you want. If you are just trying out the game, you can put it on your Windows desktop. >Second, RIGHT-CLICK the XIOTANK-win32.zip file and choose EXTRACT or EXPAND or UNZIP (this may vary depending on your version of Windows.) If it asks for a destination folder, choose the Desktop. >Third and finally, DOUBLE-CLICK the xiotank-win32 folder that should now be on the Desktop. The folder should open into an Explorer window. Scroll down to XIOTANK.EXE and double-click it. That's it! Sorry, we are working on improving the installer.
You seem to have a very low opinion of Windows users...
Control-P seems to register two keystrokes in a row most of the time (so it pauses and then immediately unpauses; or vice versa).
The game is interesting, but hard - I keep getting killed by the drones so I don't have much time to explore the mechanics...
On Mar 16, 6:06 pm, hmp <humpo...@gmail.com> wrote:
> You seem to have a very low opinion of Windows users...
No, I didn't mean to sound like that. I was trying to make complete detailed instructions on running the game. I am trying to make my game accessible to whomever comes across it, and since several steps are involved, I thought it was a good idea to explain the whole process in case they weren't familiar with unzipping stuff. I copy this text across all my game pages because most of my game downloads are Windows people :) and I want to make sure obvious annoyances (like my not having a proper installer/uninstaller) can be addressed in the help file. The Mac version has a nice installer so I don't have to help the mac users... this is why the mac notes section is short.
Also, I used to write technical help stuff for Windows and tested Windows software, and wrote Windows software testing plans, and executed them as well. So I tend to flesh out the instructions I write with more detail than is probably neccessary.
Here is an emoticon to correct any error in tone I may have made :)
> Control-P seems to register two keystrokes in a row most of the time > (so it pauses and then immediately unpauses; or vice versa).
This is a bug. Will be fixed for version 1.2 (perhaps next week?)
> The game is interesting, but hard - I keep getting killed by the > drones so I don't have much time to explore the mechanics...
It needs some balancing, and also because of the time constraints I could not flesh out the puzzles fully. So I emphasized combat more after that point.
The game has had 30+ downloads so far, and I am collecting many bug reports (mostly the same few). We are also working on an improved control scheme because the current controls are fudgy. But people are finding it fun, including me :)
> On Mar 16, 6:06 pm, hmp <humpo...@gmail.com> wrote:
> > You seem to have a very low opinion of Windows users...
> No, I didn't mean to sound like that. I was trying to make complete > detailed instructions on running the game. I am trying to make my game > accessible to whomever comes across it, and since several steps are > involved, I thought it was a good idea to explain the whole process in > case they weren't familiar with unzipping stuff. I copy this text > across all my game pages because most of my game downloads are Windows > people :) and I want to make sure obvious annoyances (like my not > having a proper installer/uninstaller) can be addressed in the help > file. The Mac version has a nice installer so I don't have to help > the mac users... this is why the mac notes section is short.
> Also, I used to write technical help stuff for Windows and tested > Windows software, and wrote Windows software testing plans, and > executed them as well. So I tend to flesh out the instructions I write > with more detail than is probably neccessary.
> Here is an emoticon to correct any error in tone I may have made :)
> > Control-P seems to register two keystrokes in a row most of the time > > (so it pauses and then immediately unpauses; or vice versa).
> This is a bug. Will be fixed for version 1.2 (perhaps next week?)
> > The game is interesting, but hard - I keep getting killed by the > > drones so I don't have much time to explore the mechanics...
> It needs some balancing, and also because of the time constraints I > could not flesh out the puzzles fully. So I emphasized combat more > after that point.
> The game has had 30+ downloads so far, and I am collecting many bug > reports (mostly the same few). We are also working on an improved > control scheme because the current controls are fudgy. But people are > finding it fun, including me :)
It is always better to have too detailed instructions than too sparse ones.
