Warzone 2100 2.0.8 RC 1 released

[DevUrandom]

Hello everyone!
Version 2.0.8 RC 1 is eagerly awaiting to be tested by everyone.
2.0.8 is, like 2.0.7 was, a bugfix only release. There are no new features, just a bunch of old bugs fixed.

Summary of changes:

• Protocol-selection removed from "Host Game", since the only option was "Internet"
• In the "Join Game" menu you can now choose between "IP" (same as the old "Internet" option) and "Lobby" (directly proceed to the Lobbyserver)
• Remove invalid references to software renderer textures (caused crashes between campaign 1-2 and 2-3)
• Improve POSIX exception handler reliability (GDB could have had trouble locating the executable)
• Textures where not properly reloaded when finishing a campaign and continueing with the next

For a more detailed list of changes you should have a look into the ChangeLog.

You can get the files from our downloads page.

Sidenote:
We now use MojoSetup for the Linux installer since AutoPackage was a bit problematic, especially for x86_64 systems.
The installer is a binary you have to execute from a terminal (chmod +x warzone2100-2.0.8_rc1.mojo && ./warzone2100-2.0.8_rc1.mojo), and not a shell script with a graphical menu like the AutoPackage was. It is still being built with the AutoPackage build tools (apbuild/apgcc), though.
Please tell us your (good or bad) experiences with the Warzone 2100 MojoSetup Linux installer!

[Cool1987]

thanks I love you all  ;D

[Giel]

thanks I love you all  ;D

Please, tell me that you're a female!

[mcdebugger]

Heh, good news (i'm speaking about changelog)
Than'x a lot, devs'! 

[Nixu__]

Thanks very much!!!

[Sonsalt]

Yehhhaaaa wonderfull, thanks for the great effort.

I truly admire your work

[Kamaze]

error:      loadFile2: file images/frend4.png could not be found!
error:      resLoadFile: Unable to retreive resource - images/frend4.png
error:      resLoad: failed to parse wrf/frontend.wrf
error:      Shutting down after failure

Grims mod.

[DevUrandom]

Grr... I apparently included the wrong grim.wz... (Or did you mix trunk with 2.0?) Fix will from my side probably not happen before monday, since I am not at home till then.

[Kamaze]

No, fresh installed.

[Kayiaxo]

Thanks for the release !
Will try it out ASAP.

[sander79]

great, but I don't hear anything >:(
Sound is not working !
also with the current SVN
No error messages, nothing

[Serman]

The key-repeat feature was long-awaited in warzone 2100.

Thanks alot.  ;D

Though, did you fix the MP game going out of sync after about 2 hours? Becahse this is what me and mertens have been expecting for awhile.

Also, what is a release candidate?

Great work guys, I hope the upcoming major release will be an instant hit.  ;D

[Delphinio]

something is wrong ^^
joining games:

lobby = dont know but not the lobby ^^
empty ip field = lobby like before

[Giel]

Though, did you fix the MP game going out of sync after about 2 hours? Becahse this is what me and mertens have been expecting for awhile.

Nope this is not fixed, and will most likely not be fixed in the 2.0.x series. This is due to the fact that this is a very, very complicated problem (and as such it's solution will be difficult to develop as well). Expect it somewhere in 2.1. For more details see our roadmap.

Also, what is a release candidate?

Exactly what the name suggests, a candidate to possibly become an "official" release.

something is wrong ^^
joining games:

lobby = dont know but not the lobby ^^
empty ip field = lobby like before

This is filed as bug #10184.

[Deathguise]

Cool nice work !! Thank you

Anyway im currently on mission 5 and warzone is running very smoothly in campaign and skirmish(under vista 32 bit home premium), however when assigning units the sub command return fire as soon as an enemy unit attacks the unit it defaults back to fire at will - this occurs during skirmish and campaign play.

Other than that ive not encountered any other nasties.