BZFlag 2.4.0 Beta Program

[JeffM]

The development for Version 2.4 is winding down and is now in the public beta phase.
2.4 is in release candidate 1. If this works out ok then we will release shortly.

Source Code
http://beta.bzflag.org/bzflag-2.3.17-20110627.tar.bz2
http://beta.bzflag.org/bzflag-2.3.17-20110627.zip

Windows Installers
http://beta.bzflag.org/bzflag-2.3.17-20110627_32Bit.exe 32Bit (runs on all windows computers)
http://beta.bzflag.org/bzflag-2.3.17-20110627_64Bit.exe 64Bit (Requires 64 bit windows)

Macintosh
Not yet.

So what this means to you is;

1) If you are a server owner, it would be nice to get some more servers setup before the public beta. 2.4 requires that public services be registered with a special key, so it would be nice to get that system tested as well. Documentation on how to upgrade a server and use the special key is being written now.
2) If you are a plugin-developer, you will need to update your plug-in code to work with 2.4. Documentation on the process can be found here, http://my.bzflag.org/wiki/index.php?tit ... .4_Upgrade . All of our "standard" plug-ins that ship with the software have already been upgraded.
3) If you are a player with the ability to compile then it would be great for you to try out the release. 2.4 is the current "trunk" in svn.

[optic delusion]

A few months ago, I upgraded my SDL, and compilation promptly broke. I had to revert my SDL version. Are we staying with the older SDL?
Configure tells me that SDL 1.3 is required, but compile proceeds with the older version.

From a fresh checkout, ./configure.

Code: Select all

checking for SDL framework... no
checking for sdl-config... /usr/local/bin/sdl-config
checking for SDL - version >= 1.2.10... yes
checking for SDL 1.3... checking for sdl-config... (cached) /usr/local/bin/sdl-config
checking for SDL - version >= 1.3.0... 
*** 'sdl-config --version' returned 1.2.14, but the minimum version
*** of SDL required is 1.3.0. If sdl-config is correct, then it is
*** best to upgrade to the required version.
*** If sdl-config was wrong, set the environment variable SDL_CONFIG
*** to point to the correct copy of sdl-config, and remove the file
*** config.cache before re-running configure

[JeffM]

the build system for 2.4 is based on the one from 2.99 and yes I believe we upgraded to SDL 1.3

[ts]

SDL 1.3 was needed a long time ago when SDL 1.2.x didn't build using a 64-bit environment on Mac OS X out of the box. SDL 1.3 did not really work back then: The mouse clicking was broken in SDL and the keyboard code would have to be tweaked.

If I remember correct the #if switches in code regarding to SDL 1.3 where removed after the SDL project did a huge update to 1.2.x to let it also compile. One would have to take a closer look but my guess is that the check regarding 1.3 is "useless code" at the moment.

[Grans Remedy]

The development for Version 2.4 is winding down and will soon enter the public beta phase on or around June 20th 2011.

In preparation for this we will be having a week of bug testing to work out any remaining issues from our development.
So what this means to you is;

1) If you are a server owner, it would be nice to get some more servers setup before the public beta. 2.4 requires that public services be registered with a special key, so it would be nice to get that system tested as well. Documentation on how to upgrade a server and use the special key is being written now.

That's great to hear, thanks!

I'm happy to put up a v2.4 server, but:
1) is the server code likely to change much or at all from now to the 20th?
In other words should I get the source now, or wait till the beta phase actually starts?

2) Does 2.4 require "upgraded" map files and config files?
If so, are the changes documented anywhere (wiki?) so I can make these changes and host an existing map?

cheers
Grans

[Yrogirg]

I've just compiled it and it seems it doesn't use textures at least for superbulets (maybe thief and laser too). I wanted to take a screenshot, but F5 doesn't work --- is it a feature?

Everything else works fine, looking forward for MW 2.3 2.4 server.

[mahem1]

How you compile the source code?

[Yrogirg]

Code: Select all

svn co https://bzflag.svn.sourceforge.net/svnroot/bzflag/trunk/bzflag
./autogen.sh
./configure --prefix=/home/grigory/Soft/bzflag2.4
make
make install

And than launching bzflag from the directory it was installed into.

What about taking screenshots? Is F5 supposed to work? Sharing screenshots can help testing.

UPD Wait, mahem you wasn't answering my question, right? In the case you were indeed asking how to compile it yourself, there are several README's provided with 2.3 on the subject. http://my.bzflag.org/w/Compiling may also help.

[blast]

I'm happy to put up a v2.4 server, but:
1) is the server code likely to change much or at all from now to the 20th?
In other words should I get the source now, or wait till the beta phase actually starts?

At this point no new features will be going in - just minor bug fixes.

2) Does 2.4 require "upgraded" map files and config files?
If so, are the changes documented anywhere (wiki?) so I can make these changes and host an existing map?

Map files will still work just fine. The only change to the BZW format was the addition of the "ricochet" option, which allows ricochet to be turned on per object.

As JeffM mentioned, we will be making an upgrade document. We didn't change a whole lot in the configuration stuff. Off the top of my head, I think the only things that will need to be tweaked for old servers is:

• Remove -requireudp as we always require UDP now
• Must have a -publickey as described at http://my.bzflag.org/w/ServerAuthentication
• No more local authentication, so -passdb is gone

I've just compiled it and it seems it doesn't use textures at least for superbulets (maybe thief and laser too). I wanted to take a screenshot, but F5 doesn't work --- is it a feature?

Everything else works fine, looking forward for MW 2.3 2.4 server.

Ensure that your key mappings are set right. I'm not sure if the configuration upgrade code has been tweaked yet or not, so maybe that's something we need to test further.

How you compile the source code?

That depends on your operating system. We don't really plan on teaching everyone to compile. However, the process of building on Windows is easier than with 2.0.x as we include the necessary dependencies.

[Yrogirg]

Ensure that your key mappings are set right. I'm not sure if the configuration upgrade code has been tweaked yet or not, so maybe that's something we need to test further.

Well, indeed there was no "bind F5 down screenshot" string in the config file, I've had to add it manually. Maybe that's why I have no textures for SB, TH or L --- do they require certain setting in config? The bug I have with radar zoomed in can also be due this.

Screenshots:

http://ubuntuone.com/p/zLe/
http://ubuntuone.com/p/zLf/

[JeffM]

How you compile the source code?

We will be providing beta installers around the 20th of this month so if you can't build don't worry you just have to wait a little bit.

[mahem1]

In one of Yrogirg pics http://ubuntuone.com/p/zLf/
The shot on the radar seem to be backwards.
The big square part is at the back instead of the front.
Or is that a customization?

[strayer]

That's just an option (customization).

[blast]

We're also keeping an updated list of what changes are necessary to migrate 2.0.x servers to 2.3/2.4 here:
http://my.bzflag.org/w/BZFS_2.4_Upgrade

[JeffM]

The fist set of beta builds have been posted ( see the first post).
Please report bugs in the Bugs and Problems forum

http://my.bzflag.org/bb/viewforum.php?f=32

[JeffM]

The beta build has been updated to 2.3.16 and includes fixes for a number of reported bugs.

[Yrogirg]

As far as I understand tank labels were removed (except for autopilot and gm lock), right?

btw the radar bug was not fixed completely --- the tank has textures but it still lacks treads. For the setting "Animated treads" "exposed" there are no treads, but with "off" or "covered" the tank has it's normal dimensions on the radar.

http://ubuntuone.com/p/10uf/ (on the screenshot I'm sitting on the box, it's not a jump).

[JeffM]

The automatic identification maker was removed, the flag and lock on markers were left in . They can be disabled by not using the experimental mode. We will evaluate the ID marker (and classic right click ID) for gameplay impact in the next major release (2.6)

The radar bug has not been fully fixed and probably will not be before release. It only happens with one setting at extreme zoom levels. We have to refactor how the tank is drawn to fix it and it's a bit too risky right now and doesn't have that big of an impact. I am fully aware of what the problem is and it is still on our list, and I hope to get to it for 2.4.2 or 2.4.4

[JeffM]

Please note that 2.4 has gone to release candidate one.
http://my.bzflag.org/bb/viewtopic.php?f=62&t=17459

[Propane Tank]

Will you still update the Ubuntu Software Center when this release is final or will I have to compile it?

[JeffM]

We submit builds to the debian repositories that ubuntu pulls from so eventually the game should make it's way into the ubuntu software center, but it's not up to us when that happens. You may need to compile it, or download a package to get it before they move it into a stable release.

[Bacon]

The links don't work so I can't download the source code.... Help?

[joevano]

The links don't work so I can't download the source code.... Help?

2.4 has been released and you are trying to download old code! You can find the release version here... http://sourceforge.net/projects/bzflag/files/