Zandronum Chat on our Discord Server Get the latest version: 3.2
Source Code
My View | View Issues | Change Log | Roadmap | Zandronum Issue Support Ranking | Rules | My Account
  

View Issue Details [ Jump to Notes ] [ Issue History ] [ Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0001167Zandronum[All Projects] Bugpublic2012-11-04 12:312018-09-30 21:55
Reporterunknownna 
Assigned ToTorr Samaho 
PrioritynormalSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOSOS Version
Product Version1.0 
Target Version3.0Fixed in Version3.0 
Summary0001167: Clients can reconnect to servers despite getting errors that would normally terminate or crash the game in ZDoom
DescriptionI've noticed this for a while now, but didn't report it until now. A certain skin will not work if the player classes are cleared through the KEYCONF lump. The game should terminate upon start, but in Zandronum, you can still reconnect to servers after getting the error. If you then reconnect, models will not be loaded.
Steps To Reproduce1. zandronum -file skin_error_01.pk3 -host
2. Connect a client to the server.
3. After getting the error in the console, "reconnect" in the console.
Attached Filespng file icon Screenshot_Doom_20121013_163703.png [^] (26,653 bytes) 2012-11-04 12:33


png file icon Screenshot_Doom_20121104_132430.png [^] (234,333 bytes) 2012-11-04 12:33


? file icon skin_error_01.pk3 [^] (52,559 bytes) 2012-11-04 12:41

- Relationships
has duplicate 0001168closed Clients can reconnect to servers despite getting errors that would normally terminate or crash the game in ZDoom 

-  Notes
User avatar (0005311)
unknownna (updater)
2012-11-04 12:32

 Alright, I've got to slim down the example PK3.
User avatar (0005312)
unknownna (updater)
2012-11-04 12:42

 I deleted the models, but thankfully it still seems to show the same symptoms.
User avatar (0005766)
Torr Samaho (administrator)
2013-01-13 12:20

 That behavior seems to be inherited from GZDoom (the model definitions are only parsed once). Just start a new game twice. The first time it will error out, the second time it will start. I didn't check the latest GZDoom version, but this definitely happens in GZDoom 323.
User avatar (0014341)
Edward-san (developer)
2016-02-06 11:01

 With the example pk3, zandronum 3.0 beta has still the problem, but in latest gzdoom (I tested gzdoom 2.0.3), the program errors out before the game starts at all.

We need to check which commit introduced this.
User avatar (0016392)
Edward-san (developer)
2016-11-29 23:53

 I stumpled upon this and discovered that backporting'https://bitbucket.org/Torr_Samaho/zandronum-zdoom-sync/commits/7185e756bd759a7e698b3ca9c7e4597acf5eac7f [^]' to 3.0 makes the program error out at startup as expected.
User avatar (0016398)
Torr Samaho (administrator)
2016-11-30 19:20

 Thanks for the info! I backported the changeset.
User avatar (0016411)
Edward-san (developer)
2016-12-03 20:01

 We need to adjust it, because the compilation with SERVERONLY=1 fails currently:


CMakeFiles/zdoom.dir/r_data/sprites.o: In function `R_InitSprites()':
/home/edward-san/zdoom/zandronum/sandbox/src/r_data/sprites.cpp:1275: undefined reference to `gl_InitModels()'
User avatar (0016417)
Torr Samaho (administrator)
2016-12-04 16:41

 Thanks for the info. I'll fix that.
User avatar (0016419)
Torr Samaho (administrator)
2016-12-04 16:58

 Should be fixed now.
User avatar (0016448)
Ru5tK1ng (updater)
2016-12-08 04:16

 With the latest changes, the server doesn't even load up the wad and as a result no clients can connect to it. I'm assuming that's intended behavior.
User avatar (0016451)
Edward-san (developer)
2016-12-08 10:20

 To be more precise, the server would error out only if the server is executed by normal zandronum. If the server is compiled standalone, the wad still loads, but no client would be able to connect in any case.

Issue Community Support
This issue is already marked as resolved.
If you feel that is not the case, please reopen it and explain why.
Supporters: No one explicitly supports this issue yet.
Opponents: No one explicitly opposes this issue yet.

- Issue History
Date Modified Username Field Change
2012-11-04 12:31 unknownna New Issue
2012-11-04 12:32 unknownna Note Added: 0005311
2012-11-04 12:33 unknownna File Added: Screenshot_Doom_20121013_163703.png
2012-11-04 12:33 unknownna File Added: Screenshot_Doom_20121104_132430.png
2012-11-04 12:33 unknownna Status new => confirmed
2012-11-04 12:35 unknownna Relationship added has duplicate 0001168
2012-11-04 12:41 unknownna File Added: skin_error_01.pk3
2012-11-04 12:42 unknownna Note Added: 0005312
2013-01-13 12:20 Torr Samaho Note Added: 0005766
2013-01-13 12:20 Torr Samaho Status confirmed => acknowledged
2013-01-13 12:20 Torr Samaho Resolution open => waiting for zdoom
2016-02-06 11:01 Edward-san Note Added: 0014341
2016-02-06 11:01 Edward-san Status acknowledged => confirmed
2016-02-06 11:01 Edward-san Resolution waiting for zdoom => open
2016-11-29 23:53 Edward-san Note Added: 0016392
2016-11-29 23:53 Edward-san Assigned To => Torr Samaho
2016-11-29 23:53 Edward-san Status confirmed => assigned
2016-11-30 19:20 Torr Samaho Note Added: 0016398
2016-11-30 19:20 Torr Samaho Status assigned => needs testing
2016-11-30 19:20 Torr Samaho Target Version => 3.0
2016-12-03 20:01 Edward-san Note Added: 0016411
2016-12-04 16:41 Torr Samaho Note Added: 0016417
2016-12-04 16:58 Torr Samaho Note Added: 0016419
2016-12-08 04:16 Ru5tK1ng Note Added: 0016448
2016-12-08 04:16 Ru5tK1ng Status needs testing => resolved
2016-12-08 04:16 Ru5tK1ng Resolution open => fixed
2016-12-08 04:16 Ru5tK1ng Fixed in Version => 3.0
2016-12-08 10:20 Edward-san Note Added: 0016451
2018-09-30 21:55 Blzut3 Status resolved => closed




Questions or other issues? Contact Us.

Links

Copyright © 2000 - 2025 MantisBT Team
Powered by Mantis Bugtracker