Warzone 2100 Forums

The Warzone 2100 Project staff bring you 3.0-beta 3!


Please submit all bugs via this link, and follow the directions listed at the link, we need every bit of that information in order to fix bugs!

NOTE: the command line arguments need a "=" between parameters now.
For example: --mod_mp=blah

NOTE: For mac users: Support for 10.4 has been discontinued; using 10.6 is highly recommended as 10.5 does not support a sufficiently high OpenGL version for all types of GFX cards.


Downloads will be made available at our usual site:
Warzone 2100 file releases on Sourceforge.

Source tarball:
http://sourceforge.net/projects/warzone ... z/download

Mac:
http://sourceforge.net/projects/warzone ... g/download

Windows:
http://sourceforge.net/projects/warzone ... e/download

Changelog:
2010-11-14: Version 3.0 beta 3

General

• Change: Make map preview faster (5f42d0032a)
• Fix: Prevent memory corruption in the scripting code (#1656, 1a6fb8a754)
• Fix: Fix rearming pads to actually repair units (#2313, #2234, 6421c81d79)
• Fix: Fix unit explosion color for turret (#2294, f4e8221ef5)
• Fix: Make armour work again (#2273, 75a6c76606)
• Fix: Don't crash in the unit design screen when using unicode strings (#2209, 3012fde61e)

Graphics

• Fix: Rocky tileset decals (#2285, 6f5392f149)

Campaign

• Fix: Make sure terrain textures and water height are correct when coming back from away missions (#2262, b859c3d699)
• Fix: Don't allow controlling the transport to prevent the scripts from getting confused (92256b2e89)

Multiplayer

• Change: Make game difficulty setting not affect skirmish games (4db5d00784)
• Change: Use the host's SP color as the default color when hosting games (09ea0be7c3)
• Fix: Make power generator output not depend on the game difficulty setting (8707a2a845)

Translations

• New: Turkish (#2261, 255a0e2413)
• Updated: Spanish (#2214, 16e015ddcf)
• Updated: Romanian (#2246, 52b86d4af1)
• Updated: French (#2268, 97a244d4a5)
• Updated: Polish (#1347, f62457fc19)

Thanks once again everyone.

Fix: Make armour work again (#2273, 75a6c76606)

W0000t? (:
This might have been a reason for both problems with overpowered scavengers and recently-overpowered machinegun branch (:
Or had it been broken recently?

upd: Ouch, guys, that makes a LOT of sense!!!111oneoneone.
I'd have to learn how to play again o.O o.O o.O
And my precious movie makes no sense now ... I couldn't repeat this victory in less than 35 minutes with beta3 Those MGs are really weak now (:

Will someone take the trouble to correct the mod shortcuts in the exe...

Owise, looking very good...(Forget to add the praise bit .)

hao wrote:Those MGs are really weak now (:

Well, the last round of rebalancing was done with broken armor (broken in 2.3.2, rebalancing in 2.3.5, fixed after 2.3.5), so some of the changes might not be so great now...

zydonk wrote:Will someone take the trouble to correct the mod shortcuts in the exe...

Should work in the next version.

In what way was armor broken?

effigy wrote:In what way was armor broken?

It was completely ignored.

Maybe it'd be good to release some sort of 2.3.6, with only the armor bug fixed??
Some people will probably play 2.3.* forever and ever ... And it'd be good even now for current games ...

Auto-kick has been working overtime. Getting alot of auto-kicks for cheating when they are no cheating. Not during game but in the game room before the game is launched.
Glad to see yall are working on anti-cheating, but right now it's hard to get a game with so many false positives.

RBL-WARDOG wrote:Auto-kick has been working overtime. Getting alot of auto-kicks for cheating when they are no cheating. Not during game but in the game room before the game is launched.
Glad to see yall are working on anti-cheating, but right now it's hard to get a game with so many false positives.

This is a truly bizarre situation...until yesterday beta3 worked fine (maybe it was a placebo but I had thought there were even performance improvements).

I did some quick trouble shooting with wardog, but all yielded an auto-kick (he trying to join my game):

1. I unistalled, then installed beta3

2. he removed all his 3rd party maps, I removed all but 1

3. I removed all and hosted a stock map

4. he re-installed

edit: Is there anything else we can do to help trouble shoot this?

hao wrote:Maybe it'd be good to release some sort of 2.3.6, with only the armor bug fixed??
Some people will probably play 2.3.* forever and ever ... And it'd be good even now for current games ...

I think its a good idea. Support +1.

Terminator wrote:

hao wrote:Maybe it'd be good to release some sort of 2.3.6, with only the armor bug fixed??
Some people will probably play 2.3.* forever and ever ... And it'd be good even now for current games ...

I think its a good idea. Support +1.

second that! or thrid that?

BTW I've contacted intel because of the OGL2.0 support with GMA devices. hopefully they'll do something about it...

as there's always a line in the error log saying, that it switches to the main pipeline and the game crashes on the GMAs with an exception handle, I think it is only to find out, what exactly is the problem with the handles. maybe it's just a small thing to fix...

Why are loading times so slow, even for a basic skirmish?

Mats wrote:Why are loading times so slow, even for a basic skirmish?

Yeah, I noticed that too

But, it's only a few seconds longer though, so no biggie for me

The new terrain textures are larger and so need more time to load.