Zandronum 3.0-alpha-170806-2040

[Torr Samaho]

Once again, thanks for your reports! It turned out that the custom userinfo syncing still needed more fine tuning. Moreover, the flag compat_pushwindow needed to be made available to keep backwards compatibility to several existing maps. Note that I changed how the zip archive of the Windows binaries is generated. It should be a bit smaller now and hopefully still work as before. If you encounter any problems with it, please let me know.

Here is the full Mercurial changelog:

Code: Select all

changeset:   10003:a578f7f4b368
user:        Torr Samaho
Fixed: The client could crash when activating the automap.

changeset:   10004:2e401826db2e
user:        Torr Samaho
Fixed: The server could kick clients erroneously for incomplete userinfo.

changeset:   10005:d0193daa9f8c
user:        Torr Samaho
Fixed: Clients tried to handle "switchonpickup" locally for other clients instead of waiting for the server to announce the weapon switch (addresses 3190).

changeset:   10006:bb47f922498c
user:        Teemu Piippo <teemu@hecknology.net>
The client now·arranges the cvars sent in the userinfo batch so that the built-in cvars are always sent before mod cvars. This way, in the event the client needs to split the userinfo packet, the built-in cvars go in the first one. If this isn't the case, the server kicks the client for sending an incomplete userinfo packet (partially addresses 3178).

changeset:   10007:8addcabb3e86
user:        Torr Samaho
Updated the links to zandronum.com from http to https (addresses 3192).

changeset:   10008:87186e95d533
user:        Torr Samaho
The command "save" can't be called by ConsoleCommand anymore (addresses 3203).

changeset:   10009:ebde7837934f
user:        Torr Samaho
typo fix

changeset:   10010:919ea7a1a4ac
user:        Torr Samaho
The command "load" can't be called by ConsoleCommand anymore (addresses 3203).

changeset:   10011:a72468b3d166
user:        Torr Samaho
Fixed: The client was kicked for "User info change flood." when connecting to a server with wads that use too many user entries in CVARINFO (addresses 3209).

changeset:   10012:2546d3bcdcb5
user:        Edoardo Prezioso <edward.san.dev@gmail.com>
- Fixed very useful GCC 7 warnings.

changeset:   10013:97e6888d369b
user:        Gaerzi <gaerzi@gmail.com>
Missing break in case NAME_FillColor
This caused weirdness with invulnerable monsters when their fillcolor was changed.

changeset:   10014:681f37880398
user:        Randy Heit <rheit@users.noreply.github.com>
Add a needed break in FxAbs::Resolve()
- Fixed: FxAbs could not resolve floating point constants because it fell
  through to the error case.

changeset:   10015:1c5cfa376463
user:        Christoph Oelckers <c.oelckers@zdoom.fake>
- fixed: The checks in P_IsThingSpecial was broken.

changeset:   10016:e834241f9d74
user:        Christoph Oelckers <c.oelckers@zdoom.fake>
- made disabling the push window check a real compatibility option.
No idea why this was a hidden one, this one definitely needs to be in the menu.
- set some required compatibility options for Super Sonic Doom.

changeset:   10017:a09712084028
user:        Torr Samaho
The authentication mechanism for non-map related lumps now allows Freedoom 0.11.3/Doom clients to join Doom/Freedoom 0.11.3 servers.

changeset:   10018:187974f45430
user:        Edoardo Prezioso <edo88@email.it>
Remove unneeded variable in doom sbar code.

changeset:   10019:7c73e83cdbfe
user:        Edoardo Prezioso <edo88@email.it>
Apply zdoom svn r4167 changes in doom sbar code.

changeset:   10020:4e5d2a415553
user:        Teemu Piippo <teemu@hecknology.net>
Fixed the wraithverge potentially causing players to become zombies (client thinks they're dead even when they're not). The wraithverge still needs a lot of work but at least this fixes the worst of it, addresses 1551.

changeset:   10021:f0e5871080e4
tag:         tip
user:        Edoardo Prezioso <edward.san.dev@gmail.com>
- fixed the glitch with status bar and automap with no-hardware acceleration systems (addresses 2604).

Download

[Sean]

TSPG has been updated to this build.

[Konda]

Linux builds (for now, not sure how this site works):
64bit: https://jenkins.csnxs.uk/job/zandronum/ ... _64.tar.xz
64bit debugging: https://jenkins.csnxs.uk/job/zandronum/ ... dbg.tar.xz

Edit: updated links, shouldn't 404 now.

[Vulpeka]

TSPG has been updated to this build.

So that means some servers are using a different version of zandronum?

[Torr Samaho]

So that means some servers are using a different version of zandronum?

There are servers running 2.1.2 and testing servers running 3.0 beta builds.

[Vulpeka]

So its still like the old days. I'll have to give 3.0 a spin haven't tested a build in 6 years.

[SP_FACE1]

My two cents:
Tested this build on Ubuntu 16.04
- coop over wifi on local network
- few players
- 2 hours
- 2 levels
* http://www.doomworld.com/idgames/?file= ... thundr.zip
* https://www.doomworld.com/forum/topic/9 ... 017-02-14/

no issues encountered

[killerkouhai]

I find with this build I get quite a lot of 'Very Fatal Errors'
Never had this problem with any of the older builds :S

[Torr Samaho]

I find with this build I get quite a lot of 'Very Fatal Errors'
Never had this problem with any of the older builds :S

I'm sorry to hear that. Did you get crash logs?

[Sean]

Torr when can we have the win32 builds of stable 3.0 because tspg has been using that commit for like a day and a half now

[Torr Samaho]

Torr when can we have the win32 builds of stable 3.0 because tspg has been using that commit for like a day and a half now

Wait, why is TSPG using an unreleased Zandronum version? We are about to release 3.0, but it's not done yet.

[Sean]

Apparently we're not anymore and nobody told me oops

[Torr Samaho]

I see. Thanks for clarifying!

[Campaum]

Not for Raspberry yet?

[ZzZombo]

Please fix the formatting of the changelog, it lacks newlines or something.

[Torr Samaho]

Seems to be working again. I think this had to do with the forum software update.

[ZzZombo]

N-no? Are you telling me on your end the changelog is formatted properly? Because for me nothing has changed. Is the forum acting up?

[Empyre]

I'm seeing the same thing, using the Zandronum skin, the changelog is all crammed together with no line breaks.

[Torr Samaho]

I'm using the black theme and the changelog is formatted properly.

[Fused]

The zandronum theme messes it up. For now read it out of the quote, Torr can't and won't fix this.