3.1 Beta reminder

I would like to clarify a few things about how these beta builds work.

We are trying to fix all major bugs as we, and you, the users, find them, and as time allows. In order to do this, we must be able to replicate the issue, and without a good way to replicate it, it is a big (time-consuming) guessing game.

This means that we need every bit of information that you can supply us, as well as crash report files and or savegames, so we can fix as many bugs as possible before the release of 3.1.0.

Here are the locations of the crash report files, and savegames, as well as anything else. FileLocations#Crashdumps

  • All bugs should be reported here: http://developer.wz2100.net/newticket.
    Don’t make the mistake that someone else will report the issue, usually, people don’t report it, or they don’t give enough information to replicate the issue.
  • You can search for the same kind of bug you have, and there might be a ticket that is closed with the "need info" response. That means we don’t have enough information to replicate the issue at hand. Feel free to add information to that ticket, so we can all debug what is going on, and hopefully solve the issue.
  • Feel free to add relevant information to open tickets as well, but adding a "me too" response does nothing to help us. We need to find a way to replicate the issue.

Warzone 2100 can’t cause your system to crash. It does not have kernel level access.
When your system crashes (reboots on windows / or a BSOD) that is the result of video drivers, or perhaps sound, it can also be because your system is unstable.

  • The way to check for system stability is to run memtest86+ (free) http://www.memtest.org, and you can install that onto a USB flash drive. Then once that is done, let it run overnight, and hopefully you will have 0 errors. If you have errors, that means your RAM needs replacing, or the timings are set incorrectly.
  • Another tool (windows only) for testing for CPU/heat issues is http://www.ocbase.com/perestroika_en/index.php?Download it is also free. You only need to run this for 1-2 hours, and usually, that is enough to see if your CPU is stable or not.
  • Another popular tester is prime95, (free, for Windows, Mac OS and Linux), get it here: http://www.mersenne.org/freesoft/

You should try newer (and sometimes older) video/sound drivers, since those also have bugs, once you verify that the issue is with the video drivers, and not system stability.

(11 comments)

Comments are closed.