Zandronum 3.2-alpha-241030-1744

[Kaminsky]

We needed to release a new beta right away to address some regressions to the player spawning that were introduced in the beta released last weekend. These issues should now be fixed. Other changes in this build include:

• Fixed a desync that happened when a player disconnected from the server before clients received a full snapshot of a level. This also caused the "P_PlayerThink: No body for player" warning to start spamming in the console after the level change.
• Added Sean's tweak to the HUD in CTF/Skulltag. The names of carriers are now displayed in their team colour, instead of the colour of the team's item they are holding.

Here is the full Mercurial changelog since the previous beta:

Code: Select all

changeset: 12636:28e433ec2ffb
user: Adam Kaminski <kaminskiadam9@gmail.com>
Fixed: players sometimes spawned in the void, or just random spots in the map, when they should've spawned at a random cooperative spot.

changeset: 12642:992907f71812
user: Adam Kaminski <kaminskiadam9@gmail.com>
- Fixed a fatal error when trying to select the farthest deathmatch spot available, and all spots were taken.
- Restored more code from GZDoom 1.8.6 used to spawn a player in deathmatch, albeit commented out because Zandronum doesn't actually use it.

changeset: 12645:1eb062e9ae46
user: Sean Baggaley <sean@csnxs.uk>
The bottom-right HUD in CTF/Skulltag now displays the names of carriers in their team colour, instead of the colour of the flag they are holding (addresses 4428).

changeset: 12646:9d7ec921b8d5
user: Adam Kaminski <kaminskiadam9@gmail.com>
Added a sanity check, when processing a "DisconnectPlayer" server command, to ensure a few things aren't executed if the player being disconnected had no body.

changeset: 12647:0c2b243f9d02
user: Adam Kaminski <kaminskiadam9@gmail.com>
Fixed "P_PlayerThink: No body for player" warnings if a player disconnected from the server before the clients received a full update (fixes another regression caused by c770f5a41612).

Download

Enjoy the fresh new build!

[Sean]

Yay, I took up 1/3 of the forum post with a patch that has basically 1 meaningful line of code

[RmBeer]

And the source code what?

Even in hg source code exist only to 3.1, or a "default" branch. How can get a 3.2 alpha like all in doomseeker?

[Sean]

And the source code what?

Even in hg source code exist only to 3.1, or a "default" branch. How can get a 3.2 alpha like all in doomseeker?

hg tags aren't created for betas. A list of hg revisions for 3.2 betas is available at https://wiki.zandronum.com/Version_hist ... eta_builds however. For this specific beta, use hg update 0c2b243f9d02

[RmBeer]

And the source code what?

Even in hg source code exist only to 3.1, or a "default" branch. How can get a 3.2 alpha like all in doomseeker?

hg tags aren't created for betas. A list of hg revisions for 3.2 betas is available at https://wiki.zandronum.com/Version_hist ... eta_builds however. For this specific beta, use hg update 0c2b243f9d02

You're mix beta with alpha. But thanks, i will try with the hash of checkout for 3.2 alpha.

[Sean]

You're mix beta with alpha. But thanks, i will try with the hash of checkout for 3.2 alpha.

"Beta" and "alpha" have ended up being interchangeable in the context of Zandronum builds.

The Linux build guide always shows the latest alpha/beta/whatever hash now; I should probably extend that to the other build guides...

[RmBeer]

You're mix beta with alpha. But thanks, i will try with the hash of checkout for 3.2 alpha.

"Beta" and "alpha" have ended up being interchangeable in the context of Zandronum builds.

The Linux build guide always shows the latest alpha/beta/whatever hash now; I should probably extend that to the other build guides...

I recompile with the correct hash of checkout in hg, and still doomseeker can't recognize the version of zandronum.

[RmBeer]

They/you really lost track of everything, and can't create a decent version that works. They/you should be more careful next time about what and how to release version 3.3, because they/you only lose players by this neglect. :/

[phineas]

They/you really lost track of everything, and can't create a decent version that works. They/you should be more careful next time about what and how to release version 3.3, because they/you only lose players by this neglect. :/

Whoa man! We're trying... we're trying REAL HARD!
You need to slay some monsters.
Try out Chap Stallis: Mo Tanky Enemeesh in Doomseeker.
It's still running 3.1.

[RmBeer]

Doomseeker shows this for all clients and asks me to install the following version:
Zandronum 3.2-alpha-r241030-1744

According to this site:
https://wiki.zandronum.com/Version_hist ... eta_builds

Show this:
Zandronum 3.2-alpha-220904-2011 a079616e5796
Zandronum 3.2-alpha-221030-0316 2c280cd262f3
Zandronum 3.2-alpha-230709-1914 89bccf7127ba
Zandronum 3.2-alpha-240405-2229 ec2e32b05ed8
Zandronum 3.2-alpha-240414-1910 fdf5f68843a5
Zandronum 3.2-alpha-241027-2139 4e8342339656
Zandronum 3.2-alpha-241030-1744 0c2b243f9d02

I go to the Zandronum source code and use:
hg checkout 0c2b243f9d02
make

I rebuild everything again for the client and use it in my Zandronum game directory, try to enter doomseeker again, and still want the damn 3.2 version:

[RmBeer]

I solved it by copying the same zandronum binary to the required directory. A doomseeker bug, why does the custom directory exist if the program no longer want to use it?