Warzone 2100 Forums

I could beta test as well.
Just give me the version needed. ;D

Tucalipe wrote: I could beta test as well.
Just give me the version needed. ;D

If you are on windows look here.

One more thing: don't use save games from beta 1 and older, they can cause problems with the current version.

do we want the debug version or non-debug version?

DEBUG!! Otherwise any crash reports are next to useless as the don't have the info the devs need to fix the problems.

Also the debug version has extra crashes (well asserts actually) that happen if something starts doing something it shouldn't, or has an unexpected value.
This is to help the devs find problems that might otherwise go unnoticed.

So get the Debug version if your gonna help beta test!!!

Yes, Debug version is the way to go.

do these allow me to play the campaign with double turret heavy tanks?

and do you guys mind if a debug info from crashes is a bit older then the latest build? (as i only get once every week with a bit luck on a pc with inet) so if at all i can only betaplay the latest i loaded (just downthemall'ed the entire files from the latest nightly builds server)

Andariel wrote: do these allow me to play the campaign with double turret heavy tanks?

No, afaik it won't, we try not to alter the campaign data.

Andariel wrote: and do you guys mind if a debug info from crashes is a bit older then the latest build? (as i only get once every week with a bit luck on a pc with inet) so if at all i can only betaplay the latest i loaded (just downthemall'ed the entire files from the latest nightly builds server)

If your revision is >= 4613  then it should be fine. But of course the newer the better.

Should I report bugs in this topic, or should I open a new one?

Devil12 wrote: Should I report bugs in this topic, or should I open a new one?

It would be ideal if you could add bugs to the bug tracker if for whatever reason you can't do this a separate topic will work too, we can sticky it then.

edit : Damm.... You beat me to it.

Troman wrote: It would be ideal if you could add bugs to the bug tracker if for whatever reason you can't do this a separate topic will work too, we can sticky it then.

Yea, if you find (or think you found) a bug you should first check the bug-tracker to see if its already there, then add it to the tracker.

Also if your unsure if its a bug or not, you can start a post about it on the forums, and add it to the tracker later if needed.

Just a quick report: I've finished the Western Campagin without bugs (apart from the pathfinding bug, which is present since the last good version )

I finished alpha campaign yesterday using svn trunk code after finding lots of bugs that were promply fixed by the brave developers. I will continue testing and hope to help releasing the best warzone 2100 2.1 version possible. Thanks to all developers.

Yeah, i will help ya beta test it for ya
Used to do it all the time for Microsoft, did it for vista and sp3
Glad to help ya all
Cya


Current hardware:
Graphics card or chip:Intel G965 GPU
Sound: Sound audigy 8.2

Current OS: Windows Xp Vortex SP3
There the only things vital to cause stability issues with this game tbh, if you want loads more detail just ask ;D

Could anyone test the last campaign?

We are more or less done with first one and the second one is being tested by at least one beta tester at the moment. It would be ideal for us if someone could already start testing the last campaign.

Thanks again to all beta testers.

EDIT:
to make Warzone start campaign 2 or 3 when you launch it use these command line parameters:
for the second campaign or for the third campaign.

I think it's worth to mention that we should do cross plattform testing for campaigns too. I did only test on Linux/AMD64 and had at least one bug that didn't occur on a developer's M$ Windows box. So in addition to Troman's request to test the last campaign, which is surely of highest priority, the other campaigns should be tested completely on M$ Windows too.