Give it at least 2 or 3 years, could be longer though.
Zandronum 3.0
Re: Zandronum 3.0
Re: Zandronum 3.0
Actually, 2-3 years seems to be the distance between major Zandronum releases:
Skulltag 0.98d - 7 Nov, 2010
Zandronum 1.0 - 24 Aug 2012
Zandronum 2.0 - 29 Mar 2015
Zandronum 3.0 - 07 Sep 2017
<capodecima> i dont say any more word without my loyer jenova
Re: Zandronum 3.0
It can sound like mocking when you say it, but it's just the way things are with major release versions of Zandronum
Re: Zandronum 3.0
How can build Zandronum 3.0 server for Raspberry? Not released yet?
- doomjoshuaboy
- Developer
- Posts: 304
- Joined: Thu Aug 02, 2012 5:36 am
- Location: Australia
- Contact:
Re: Zandronum 3.0
doomjoshuaboy wrote: ↑Sun Oct 01, 2017 1:42 amil sent over the one thats released now if you get my pm.
Please, I need it for my servers... they can not connect anymore...
Re: Zandronum 3.0
I've found the way to do it, had some issues to register on this forum but it works now.
I'll provide step by step manual from my notes.
Manual for version 2.0 doesnt work anymore.
Basically this needs to be done differentlty:
Do not apply raspberry patch after getting source code.
Compilation can be done the way as manual for 2.0 suggests however compiler throws up error regarding one static char variable.
You need to change this static char in signed static char because it contains negative variables and compiler apparently dislikes this on arm.
Ibwas able to compile server then and runs normally.
Uset old config for it however Ive noticed that player respawns with shotgun now.
I'll provide step by step manual from my notes.
Manual for version 2.0 doesnt work anymore.
Basically this needs to be done differentlty:
Do not apply raspberry patch after getting source code.
Compilation can be done the way as manual for 2.0 suggests however compiler throws up error regarding one static char variable.
You need to change this static char in signed static char because it contains negative variables and compiler apparently dislikes this on arm.
Ibwas able to compile server then and runs normally.
Uset old config for it however Ive noticed that player respawns with shotgun now.
- Torr Samaho
- Lead Developer
- Posts: 1543
- Joined: Fri May 25, 2012 6:03 pm
- Location: Germany
Re: Zandronum 3.0
ok here is the list of all steps with both particular commands and descriptions:
Install packages necessary to perform build:
sudo apt-get install build-essential zlib1g-dev libsdl1.2-dev libjpeg-dev \
nasm tar libbz2-dev libgtk2.0-dev cmake mercurial libfluidsynth-dev libgl1-mesa-dev \
libssl-dev
Create and cd to your working directory:
$ mkdir $HOME/zandronum-build && cd $HOME/zandronum-build
Clone the Zandronum repository:
$ hg clone https://bitbucket.org/Torr_Samaho/zandronum .
Create and cd to the directory where build files will be outputted:
$ mkdir buildserver && cd buildserver
Change variable type from char to signed char in file p_spec.cpp line 1578:
Original declaration:
static const char hexenScrollies[24][2] =
{
{ 0, 1 }, { 0, 2 }, { 0, 4 },
{ -1, 0 }, { -2, 0 }, { -4, 0 },
{ 0, -1 }, { 0, -2 }, { 0, -4 },
{ 1, 0 }, { 2, 0 }, { 4, 0 },
{ 1, 1 }, { 2, 2 }, { 4, 4 },
{ -1, 1 }, { -2, 2 }, { -4, 4 },
{ -1, -1 }, { -2, -2 }, { -4, -4 },
{ 1, -1 }, { 2, -2 }, { 4, -4 }
};
modified declaration with added signed:
signed static const char hexenScrollies[24][2] =
{
{ 0, 1 }, { 0, 2 }, { 0, 4 },
{ -1, 0 }, { -2, 0 }, { -4, 0 },
{ 0, -1 }, { 0, -2 }, { 0, -4 },
{ 1, 0 }, { 2, 0 }, { 4, 0 },
{ 1, 1 }, { 2, 2 }, { 4, 4 },
{ -1, 1 }, { -2, 2 }, { -4, 4 },
{ -1, -1 }, { -2, -2 }, { -4, -4 },
{ 1, -1 }, { 2, -2 }, { 4, -4 }
};
Generate Makefiles
Run cmake, this generates the Makefiles.
$ make clean; \
cmake -DCMAKE_BUILD_TYPE=Release -DSERVERONLY=ON -DNO_ASM=1 ..
The -DNO_ASM=1 argument is important as it doesn't compile the architecture-dependent assembly code.
Install packages necessary to perform build:
sudo apt-get install build-essential zlib1g-dev libsdl1.2-dev libjpeg-dev \
nasm tar libbz2-dev libgtk2.0-dev cmake mercurial libfluidsynth-dev libgl1-mesa-dev \
libssl-dev
Create and cd to your working directory:
$ mkdir $HOME/zandronum-build && cd $HOME/zandronum-build
Clone the Zandronum repository:
$ hg clone https://bitbucket.org/Torr_Samaho/zandronum .
Create and cd to the directory where build files will be outputted:
$ mkdir buildserver && cd buildserver
Change variable type from char to signed char in file p_spec.cpp line 1578:
Original declaration:
static const char hexenScrollies[24][2] =
{
{ 0, 1 }, { 0, 2 }, { 0, 4 },
{ -1, 0 }, { -2, 0 }, { -4, 0 },
{ 0, -1 }, { 0, -2 }, { 0, -4 },
{ 1, 0 }, { 2, 0 }, { 4, 0 },
{ 1, 1 }, { 2, 2 }, { 4, 4 },
{ -1, 1 }, { -2, 2 }, { -4, 4 },
{ -1, -1 }, { -2, -2 }, { -4, -4 },
{ 1, -1 }, { 2, -2 }, { 4, -4 }
};
modified declaration with added signed:
signed static const char hexenScrollies[24][2] =
{
{ 0, 1 }, { 0, 2 }, { 0, 4 },
{ -1, 0 }, { -2, 0 }, { -4, 0 },
{ 0, -1 }, { 0, -2 }, { 0, -4 },
{ 1, 0 }, { 2, 0 }, { 4, 0 },
{ 1, 1 }, { 2, 2 }, { 4, 4 },
{ -1, 1 }, { -2, 2 }, { -4, 4 },
{ -1, -1 }, { -2, -2 }, { -4, -4 },
{ 1, -1 }, { 2, -2 }, { 4, -4 }
};
Generate Makefiles
Run cmake, this generates the Makefiles.
$ make clean; \
cmake -DCMAKE_BUILD_TYPE=Release -DSERVERONLY=ON -DNO_ASM=1 ..
The -DNO_ASM=1 argument is important as it doesn't compile the architecture-dependent assembly code.
Re: Zandronum 3.0
I've checked dmflags description and found respawn with shotgun only for cooperative, I'm puzzled now.Torr Samaho wrote: ↑Mon Oct 09, 2017 7:36 pmSome dmflag numbers needed to be changed in 3.0 compared to 2.1.2. Could this be causing your problem?
Here are dmflags that I use:
dmflags 1004740
dmflags2 8391168
zadmflags 1
compatflags 0
zacompatflags 262144
Re: Zandronum 3.0
Well, it's not cooperative-exclusive anymore...
- Torr Samaho
- Lead Developer
- Posts: 1543
- Joined: Fri May 25, 2012 6:03 pm
- Location: Germany
Re: Zandronum 3.0
includes "sv_shotgunstart 1" and the behavior of this was changed in 3.0:
Code: Select all
- - sv_shotgunstart is now respected in non-cooperative gamemodes. [Dusk]
Re: Zandronum 3.0
Thank you for clarification.Torr Samaho wrote: ↑Tue Oct 10, 2017 7:55 pmincludes "sv_shotgunstart 1" and the behavior of this was changed in 3.0:Code: Select all
- - sv_shotgunstart is now respected in non-cooperative gamemodes. [Dusk]
Re: Zandronum 3.0
I guess a better estimate would be "never".
=== RAGNAROK DM ON ... uh... dead forever? ===
=== ALWAYS BET ON ... uh... dead forever? ===
=== Who wanta sum wang? ===
=== Death and Decay - A new Monster/Weapon replacer ===
=== ALWAYS BET ON ... uh... dead forever? ===
=== Who wanta sum wang? ===
=== Death and Decay - A new Monster/Weapon replacer ===
Re: Zandronum 3.0
Considering Konar is too inactive to even hand over the IRC network, I'd say him updating his servers is even less likely.
Re: Zandronum 3.0
Have you checked the Multiplayer Options -> Network options if everything is set on fastest, especially the Game Update rate?grrfield wrote: ↑Tue Sep 12, 2017 7:42 amCan you elaborate? This works fine for me. Also, it won't hurt to try with a fresh INI.grrfield wrote:but Torr, the spycam in survival mode is lagging like hell....
I seriously thought it was a general problem. My first post was just to verify if other people were experiencing the same problem (this does not seem to be the case apparently). I won't raise a ticket yet, as i'm currently collecting further information.
To further elaborate on the matter: Since i mostly die early on in the coop/survival stuff (due to not enough skills), i get a lot to spectate the remainder of the round. With zan 3.0 (as opposed to the testing versions and 2.1.2), it seems that in spectator mode the movement of the guy i'm following is stuttering heavily now (all doomguys, all pings). Otherwise this was very smooth (taking into account the ping of other players). I said "lag" in my first post, but this seems not to be a correct description, i really is stuttering, not lag. "Heavily" means: "very unpleasant to watch comfortably", "like a streaming movie you watch on the internet, but better should lower resolution, since you are exceeding slightly your bandwith". Not a huge problem, but very noticeable....
I keep you posted, but most likely it is just my configuration (server-side or client side) i have to dig in some further. Oh yeah, I started with a new config. ini (client side).
regards,
Re: Zandronum 3.0
I could whip something up on my next day off real quick and give it a test run, only problem is I don't know why my connection isn't allowing me to host so I might need someone to throw it up.Torr Samaho wrote: ↑Sun Sep 24, 2017 12:46 pmI'm exactly not sure which problem you are referring to. Do you have a minimal example wad that allows to reproduce the problem?Peanut wrote:Does this mean that annoying displacement bug with sky portals is fixed or closer to being fixed? WDI01 of WhoDunIt for instance, I built that skybox with anchors throughout that entire map without the knowledge of that limitation and it was always a coin toss whether it worked properly or not. This is merely for future reference.
Again, I could be mistaken but from what I can recall from it happening, it always seemed to happen for everybody unless the map was reloaded leading to thought that "well, maybe it's some kind of disconnect between the server and clients and possibly something to do with the reliability of the actor placements". Something along those lines. That being said, now I'm even more interested in what it could possibly be. We'll see if we can replicate the issue here in a few days and I'll see if I can send you some examples.Torr Samaho wrote: ↑Sun Sep 24, 2017 12:46 pmInformation about actors is sent in reliable packets, i.e. all commands are guaranteed to arrive in the correct order and no commands are lost. So if you weren't disconnected, this doesn't sound like a packet loss problem.Peanut wrote:Clients load into map but the server can't properly spawn in every single anchor actor or something happens between the packets being sent to the clients due to the amount on the map, thus leading to the sky breaking in multiple sectors or just completely so the server resolves to sit there with broken anchors. Of course, I could be mistaken on how this works because as of now I can't really recall any other actors being effected this way, but that's the first thought that popped in my mind when I read about the packet increase.