We'll receive bug reports, as usual, and if the reported issues with fglrx can be worked around we'll be releasing maintenance versions as r2, r3 and so on.

We're using OpenSUSE's Build Service (OBS for short), and the packages are there already, so if you installed from OBS you should be able to update rather easily (hopefully, even with delta rpms ) - not all repos have been tested, so if you're on one of the unlucky ones to spot a packaging bug, please post on the bug tracker ASAP.

vegastrike-music and vegastrike-speech were unchanged so you don't have to update. "Updated" versions are there since r1 is the first official (non-beta) release.

Linux

You can look for the packages in OBS' search interface, or you can set up the repos from the urls below (which is the best way to get updates):

For the most popular linux distros (available in OBS), we have zypper/deb repos:

Most RPM-based distros use yum or yum-compatible tools, so you just have to download the repo description into the proper path: "sudo wget {repository path}/{repo name}.repo -O /etc/yum.repos.d/{repo name}.repo" (for openSuse, it's /etc/zypp/repos.d). You'll probably have to browse the repository to find the "repo name" (it's not evident from the above links, derived from OBS project settings).

It should prompt whether to import the repo key next time you update metadata, with zypper refresh or yum update.

Other distros

If your distro is not on the list, source tar balls and data packages can be downloaded directly from sourceforge:

Many distros (not all) have a vegastrike-debuginfo or vegastrike-dbg package you can use to install debugging info and provide better stacktraces for bug reporting - please, when reporting a crash-type bug, install that package and run vegastrike through gdb:

Also include all information about which distro and platform you're running, GPU brand and model, driver versions, the output of the "glxinfo" command, the captured output of vegastrike itself (stderr.txt from the above commands), all of which could potentially include useful information for tracking down the bugs.

No way to find out? I had to setup a new account on download.com to get a new release up. Never heard back from ace123 for the account info for it. I also setup a facebook page for us as the only other one I found was from the wikipedia page.

Because of YOU Arbiter, MY kids? can't get enough gas. OR NIPPLE! How does that mkae you feeeel? ~ Halo

@klaussI am wondering if one could create is a graphics benchmark mission to get Vegastrike into Phoronix test suite. Maybe there is already one? You've got some nice heavy planet shaders, just find a configuration which runs with mesa drivers without triggering a fallback. It would increase the exposure of the game and get a few contributors maybe.

So what I did:Go to the 11.04 link posted here above, downloaded from folder 'i396' the VS deb package, installed, then downloaded form folder 'all' the vs data all package, and installed, and as I said the console show me this:libboost_python-py27.so.1.42.0: cannot open shared object file: No such file or directory

I dont find that with synapticWhat I'm doing wrong? I guess that is the way

PD: now I have the launcher on my menu but nothing happens when I click it

You know you have been raytracing too long when ...... You take a photo course just to learn how to get the lighting right.

Next issue:Some dependencies can not be resolved: libswscale0, ..., libavformat52. Available versions are libswscale2, ..., libavformat53. Anyone an idea where to get the older libs from for Ubuntu 11.10. Atm I am inclined to compile vs from source.