We are progressing towards 2.0.6 and want you to test our work before giving it to the public.
Please check whether the bugs you reported and we said we fixed are really fixed, if the exe works on all systems (Win98 e.g.) or if any annoying new bugs appeared. You don't need to go into excessive debugging, just tell is if you encounter any anomalies when normally running this exe.
If you get these exes to crash:
- On Windows you will get a popup window which asks you to save a diagnostic file. Please choose yes and send us the file. It is very helpful for us.
- On Linux Warzone will automatically save a textfile into /tmp/warzone2100.gdmp. Please also send us this file. (It is very helpful if you have GDB installed. You don't have to run Warzone through it, as Warzone can start it automatically on a crash.)
Note: These files contain informations about your system and the crash. They should be completely anonymous...
The Linux textfile is, for sure, you can control that yourself.
The Windows Minidump should be also, but as of it's binary nature Microsoft might hide something in it. At least in my tests I wasn't able to discover anything unusual and you can be sure that we wouldn't use those informations for any malicious things if we could access that info at all.
warzone2100.exe.7z is the Windows binary
warzone2100.7z is the Linux binary
Both are 7zip compressed: http://7zip.org/
Just extract them to your Warzone directory and override the old exe/binary. (You might want to save a backup of the old exe, though.)
On Systems older than Windows XP you need to download the dbghelp.dll.7z and extract it to your Warzone folder. Make sure you read the license.txt as this DLL is not GPLed!
Sorry for the inconvenience...
Thank you for your efforts!
ChangeLog since 2.0.5: wrote:0000-00-00: Version 2.0.6
* New: New exceptionhandler allows better bugreports by saving memory dumps (On Windows and Linux)
* Fix: Windows 98 is supported again
* Fix: Saving of config should work correctly for all settings again
* Fix: Missing transport in Campaign 2 Mission 1 and Campaign 3 Mission 1 arrives again
* Fix: Various crashes
* New: Translucent selection-box from version 1.x restored
* Change: Make cutscene texts more easily readable
* Fix: Wrongly displayed tileset in Campaign 2 Mission 1 and Campaign 3 Mission 1 properly fixed
* Fix: Camera now properly displayed on radar
* Fix: Gamma control support improved
* Fix: Colors on Mac corrected
* Fix: No more invalid OpenAL errors
* Commandline options:
* Fix: --resolution works as expect now
* Build system:
* New: Docs can now be installed in Autotools builds
* New: You can now control the installation dir for the icon and .desktop file by passing --icondir and --applicationdir to configure
* New: MSVC project file now supports automated building of lexers/parsers
* Change: Generation of lexers/parsers changed
* Change: Data is now build by default
* Change: Automated building of NSIS installer is now supported on Linux and Windows
(You will have to set --with-makensis --with-installer-libdir and --with-installer-version)
* Fix: Autotool build: Cleaning and uninstallation has been fixed (and generally Automake's features are used better)
Updated binaries to r909. This should fix several additional crashes and also changes the cutscenes further:
Update to the ChangeLog wrote: * Cutscenes (still text only):
* Change: Make texts more easily readable
* Change: Proceed faster so it does not look as if Warzone hangs
* Change: Exit by pressing left mouse button
Fixed crashes were: (list not necessarily complete)
- Empty config file
- Mac OpenGL
- Victory in beta campaign