Need help getting multiplayer with Project Brutality via Zandronum 3.0 to work correctly

General help and assistance forum.
Post Reply
temp_user_1
New User
Posts: 2
Joined: Wed Jul 13, 2016 12:32 pm

Need help getting multiplayer with Project Brutality via Zandronum 3.0 to work correctly

#1

Post by temp_user_1 » Wed Jul 13, 2016 12:51 pm

Hi everyone, I hope anyone here can help me with this. I've tried Google, tried troubleshooting this by myself - nothing yielded any results.

Preparations:
  • DOOM2.WAD - md5: 25e1459ca71d321525f84628f45ca8cd, size: 14 604 584 bytes
  • ZandroDev3.0-160519-2047windows.zip - downloaded from here
  • Project_Brutality_2.03.zip - downloaded from here
  • Windows 8.1 64bit
I extract and put everything in the same folder, and create empty "zandronum-<username>.ini" file to force it to launch in portable mode and use default settings.

Here is how I start my local server:

Code: Select all

zandronum.exe -iwad DOOM2.WAD -file "Project Brutality 2.03.pk3" -port 1234 -host -nobroadcast -private +sv_cheats 1 +bd_classicmonsters 0 +bd_TraditionalMode 0
Here is how I join that server:

Code: Select all

zandronum.exe -iwad DOOM2.WAD -file "Project Brutality 2.03.pk3" -connect 127.0.0.1:1234
Here is how I start singleplayer:

Code: Select all

zandronum.exe -iwad DOOM2.WAD -file "Project Brutality 2.03.pk3" +sv_cheats 1
I have tried several versions of Zandronum 3.0 - ZandroDev3.0-160519-2047windows.zip, ZandroDev3.0-160510-1827windows.zip and ZandroDev3.0-150819-2351windows.zip , with no noticable difference between them.

List of issues:
  • Gore is bugged and does not work correctly.
    Here is how it should be (singleplayer): https://streamable.com/m2tl
    But instead I get this (when joining my server): https://streamable.com/nh3x
  • Grenade explosion is bugged. Sound is delayed (sometimes for as much as 5 seconds) and explosion itself is not centered on grenade. Video above illustrates this.
  • No visual damage indicators (bullet holes) on HUD.
  • Some weapon switching animations are bugged: https://streamable.com/z5z9 (you can see silencer appear for a few frames - this does not happen in singleplayer)
  • Some weapon idle animations are bugged: https://streamable.com/87te (the barrel is constantly blinking red - this does not happen in singleplayer)
  • Sometimes, even on lowest difficulty, enemies are still alive after getting hit with a rocket launcher. Happened about 2 or 3 times and I was unable to record it since. They flew away from the blast, laid on the floor looking confused, then stood up as if nothing happened.
  • Sometimes, instead of blowing up correctly, corpses just stand in the air frozen during their "blowing up" animation midway. Happened only once, not sure if it's multiplayer-only bug.
Why does multiplayer differ so much from singleplayer in a bad way and how do I get multiplayer to work correctly?

User avatar
Torr Samaho
Lead Developer
Posts: 1543
Joined: Fri May 25, 2012 6:03 pm
Location: Germany

Re: Need help getting multiplayer with Project Brutality via Zandronum 3.0 to work correctly

#2

Post by Torr Samaho » Thu Jul 14, 2016 7:39 pm

For existing mods, Zandronum 3.0 should behave as 2.1.2. If it does not, it's either a bug (if it only happens online it is likely a Zandronum bug, if it also happens online it's more likely a bug in our ZDoom base) or the mod relied on undefined behavior and ZDoom changed how the undefined case is handled.

The issues you are describing could be Zadronum bugs. Please open a tracker ticket and we can discuss the technical details there.

temp_user_1
New User
Posts: 2
Joined: Wed Jul 13, 2016 12:32 pm

Re: Need help getting multiplayer with Project Brutality via Zandronum 3.0 to work correctly

#3

Post by temp_user_1 » Fri Jul 15, 2016 2:45 am

Thank you for reply.
Here is a link to the ticket for this issue: http://zandronum.com/tracker/view.php?id=2783

I was expecting my problem to be of a more stupid kind (not passing some important arguments to the server, or not joining it correctly - something like that), but totally not something that warranted a bug tracker ticket.

Post Reply