Warzone 2100 Forums

As most of you know, we took down 2.2 beta 1 because of lobby server issues.

Well, those are fixed now, as well as a ton of other things, so I bring you 2.2 beta 2!

2.2 beta 2 offers:

• Rebalance 0.4.2
• Radar detector turret
• FMV playback supported on more computers
• Version checking added; game now runs on port 2100 (and will not conflict with 2.1.3)
• Games can now be password protected

For the full changelog, see: ChangeLog

Notice that this version doesn't include my fixes to Repair Facility, units auto-repairing or in Hold Position mode ignoring surroundings, secondary turrets of multi-turret tanks not firing, and all my other order/action fixes. :/ Sorry, folks.

Download
The source code and all available binaries can be found, as usual, at the download page.

Best regards,
The Warzone 2100 Resurrection Project

does the rebalance 4.2 affect the campaign? (please say yes xD )

No.

Per wrote:No.

And the repair facility fixes arent either?

Per wrote:No.

lol that sucks.

Just two quick questions from me:

1. If the FMV support is fixed, then where the hell are the downloads with the FMVs? sorry about that? The FMV were sometimes a little wonky, sometimes not I couldn't nail down a dump normally.
2. Why does it take so long for the installers to be made, I think I had to wait for two days till the Windows Installer came out. I know it takes a while to compile but doesn't GNA have pretty powerful servers that can get the job done faster than that?

themousemaster wrote:

And the repair facility fixes arent either?

Nope, neither are the multi-turret fixes, the Hold Position fixes, auto-repair fixes, and lots of other stuff. Just think of it as "awesome things will come in the next beta"!

TylerP223 wrote:Just two quick questions from me:

1. If the FMV support is fixed, then where the hell are the downloads with the FMVs? sorry about that? The FMV were sometimes a little wonky, sometimes not I couldn't nail down a dump normally.
2. Why does it take so long for the installers to be made, I think I had to wait for two days till the Windows Installer came out. I know it takes a while to compile but doesn't GNA have pretty powerful servers that can get the job done faster than that?

1. sequences.wz <- Put that in your Warzone 2100 folder (where warzone2100.exe is). Keep in mind, if you just install over 2.2 beta 1 with FMVs, you won't need to redownload them.

2. We currently only have one person capable of making a Windows installer, since it's impossible to make one in Windows, you can only make one using Debian Linux (else I would make one myself). We don't use Gna anymore, and I don't think Gna could ever compile Windows installers for us in the first place.

Sorry about that, I'm glad that I didn't have to download it again, but why on Earth would the program need to be compiled on a Debian machine instead of a Windows machine? It can't just be for the GCC, there's at least 3 different Windows ports that I can think of right now. And your wrong about the GNA thing, at least for download servers, here's the 2.2b2 Windows Link
http://download.gna.org/warzone/release ... -debug.exe
That's why I assumed you still used GNA for everything.

TylerP223 wrote:Sorry about that, I'm glad that I didn't have to download it again, but why on Earth would the program need to be compiled on a Debian machine instead of a Windows machine? It can't just be for the GCC, there's at least 3 different Windows ports that I can think of right now. And your wrong about the GNA thing, at least for download servers, here's the 2.2b2 Windows Link
http://download.gna.org/warzone/release ... -debug.exe
That's why I assumed you still used GNA for everything.

Giel compiles them and uploads them to Gna. I meant that we don't use Gna for source code management - we still currently use it for the mailing list and to host releases.

It needs to be compiled on a Debian machine because the installer makefiles don't work for Windows shell scripting. Since I absolutely hate Windows shell scripting, there's nothing I can do to fix it. You might want to try pestering the other developers, though.

(Emphasis on "installer" - you can compile binaries just fine.)

Can't wait to see multi-turret fixes, beta 3 perhaps?

PS: When did you guys switch to SourceForge?

Has anyone noticed that the font family changes from monospace to sans-serif? I really think that should be done much earlier.

Violin wrote:Has anyone noticed that the font family changes from monospace to sans-serif? I really think that should be done much earlier.

So this is actually a compliment, right?

Violin wrote:Has anyone noticed that the font family changes from monospace to sans-serif? I really think that should be done much earlier.

Indeed, although Mac OS X has always been a sans-serif font.

However, it is not without its share of problems. If I recall correctly the text entry box assumes all characters are the same size and so clicking on characters to change the current insert position is probably broken.

Regards, Freddie.

I liked mono space it looked better. Anyway to get it back without recompiling?

What is a Radar Detector?