Warzone 2100 Forums

We would like to thank all the testers for testing all those 2.3 beta candidates, and bringing us one step closer to doing a final 2.3 buid.

In this release, we have changed the write directory for warzone's crash report file (warzone2100.rpt [windows only]) and the logging file (WZlog*.txt), to obey window's vista & win 7 UAC restrictions.
All our files will now be written to <config-dir>/logs.
On windows: C:\Users\user name\Documents\warzone2100\logs
On linux: ~/.warzone2100-2.3/logs
On mac: ~/Library/Application Support/Warzone 2100 2.3/logs

The stderr file is called WZlog-<date>_<time>.txt

As usual, this release candidate brings in more fixes.

Thanks again for testing!


Bug Reports:
As usual, we need bug reports to fix problems in the game. Please note that we use tickets only to track bugs, for discussions about how features should work and feature requests we have a dedicated forum section.

For bug reports, see BugReporting for details, in short:

• Search the existing tickets for your problem, if the problem has already been fixed in SVN, the ticket will be closed.
• If there is an open one already, feel free to add more info to it.
• If there is no report yet, make a new ticket.
• Be as detailed as possible in both summary and description, and either log in with your forum account or leave an email address so we can contact you if we need more information.
• The more information we have, the easier it is to fix problems, so include savegames/instructions to reproduce the bug, crashdumps, backtraces, screenshots for graphical problems... if you have.
• When you attach files to a ticket, please add each text/image file separately and uncompressed, so we can view them easily in trac (savegames can and should be zipped, they consist of name.gam, possibly name.es, and the files in the name/ folder).

Download:
As usual, downloads can be found on our download page.

2010-04-17: Version 2.3 RC 1a

• General:
  • Change: Supress system dialogs when in full screen mode (r10605, ticket:1776)
  • Fix: Actually use saved experience for new droids (r10604, ticket:251)
  • Fix: Various build fixes (r10558, r10561, r10563, r10586, r10595, r10606)
• Multiplayer:
  • Fix: When using a passworded game, prevent connection to anyone but the host, until verified. (r10572, ticket:1611
• Mods:
  • Change: DyDo AI updated to version 2.1.1
• Translations:
  • Updated: Spanish (r10598), German (r10599), Croatian (r10588), Polish (r10577)

for Bug reports: http://developer.wz2100.net/newticket

Thanks to forum member Berg for the pic.

Thanks WZ Team. Great work guys.

LMAO That second image looks like someone playing the piano, and the last image looks like you are giving the bug a traffic ticket!

KenAlcock wrote:LMAO That second image looks like someone playing the piano, and the last image looks like you are giving the bug a traffic ticket!

"Hey bug, you can't park there!"

It isn't pretty different than that, after all

~Olrox

Does that pic count as a bug report?

Back in beta 6 ports were no longer forward to port 9990
Change: Don't forward port 9990, we only need 2100. (r9012)

my config file still says
masterserver_port=9990

Is that line in config like dead?

Thanks for the hard work, devs. I will try it when possible... Hope this time everything is ok. ^^ The problems I had with B13 were my fault... Don't even think about that problem anymore. :<

viewtopic#p53196

BunkerBlaster wrote:Back in beta 6 ports were no longer forward to port 9990
Change: Don't forward port 9990, we only need 2100. (r9012)

my config file still says
masterserver_port=9990

Is that line in config like dead?

The connection to the lobby is over port 9990, to other players over port 2100. Only the latter needs to be forwarded to the host.

I tested recycling experience over a save/load cycle in skirmish and in campaign; it worked exactly as one would hope.
Keith

hei,
i played the game in skirmish.
I found some problems:
Game crashed after i end one game and clicket on skirmish,
game begins to run slow and need much cpu (should the game not run even on very old pcs? - dualcore on 0.8 ghz running)
units ignore orders when game is running slow.

and now my question how do i find out if there is a bug report about THIS crash there are 1000 of crash reports in the bugtracker...

andron wrote:hei,
i played the game in skirmish.
I found some problems:
Game crashed after i end one game and clicket on skirmish,
game begins to run slow and need much cpu (should the game not run even on very old pcs? - dualcore on 0.8 ghz running)
units ignore orders when game is running slow.

and now my question how do i find out if there is a bug report about THIS crash there are 1000 of crash reports in the bugtracker...

Hi andron, did you follow the procedures from the FAQ?
Maybe that can solve your problem with the game speed.

Also, there is a search tool in the trac, you should use that to find out when you want to know if there's an already opened ticket for something.

Anyway, this problem is frequent and most of the times it is driver-related. If you've updated your drivers and the problem is still happening, then you should try the procedures from the FAQ and then ask for help if it still persists

~Olrox

uhm yeah i think its also okay when i just let the cpu run on fullspeed but i just wonder why this game need so much hardware...

i tried the search tool but there are too much results when i just put in "crash" hmm Results (1 - 10 of 1019) and how can i filter the results that are fixed with the new version?

Installing newer drivers could decrease your CPU usage significantly.

Anyway, give us your crash report files. They should be in the logs folder in your Warzone configuration folder (My Documents/Warzone 2100 2.3/logs/ or ~/Library/Warzone 2100 2.3/logs/ depending on OS)

You guys need to offer mirror options in the installer for the videos.