MantisBT - Zandronum
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0001633Zandronum[All Projects] Bugpublic2013-12-31 14:182024-03-01 02:42
ReporterEdward-san 
Assigned ToLeonard 
PriorityurgentSeveritymajorReproducibilityalways
StatusresolvedResolutionfixed 
PlatformOSOS Version
Product Version2.0-beta 
Target Version3.1Fixed in Version 
Summary0001633: [Linux x86_64] Multiplayer game completely broken
DescriptionWhen I connect to a 2.0beta server with the available linux x64 version and the 1.2 INI, the game appears completely broken:

fast cursor animations in menu and console;
very slow and choppery input responses;
ignores completely cl_capfps settings.

if I backup the old INI and let zandronum create a new one, it works fine, but when I change 'cl_capfps' to 'true' in 'console' the problem raises again, even after resetting the program.
Steps To Reproduce- Connect to a 2.0 beta server

or

- Host a server game with normal doom2.wad and connect to it
Additional Informationthe diff between new created INI and the one with 'cl_capfps' change doesn't show anything different from cl_capfps change ...
TagsNo tags attached.
Relationships
related to 0003334assigned Kaminsky Tickrate discrepancies between clients/servers 
related to 0003418resolved Leonard (3.1 alpha) Stuttering ingame 
Attached Filespatch linuxClientFix.patch (539) 2014-01-02 15:44
https://zandronum.com/tracker/file_download.php?file_id=1133&type=bug
Issue History
Date ModifiedUsernameFieldChange
2013-12-31 14:18Edward-sanNew Issue
2013-12-31 14:24Edward-sanSummaryMultiplayer game completely broken with Linux => [Linux x86_64] Multiplayer game completely broken
2014-01-01 21:27Torr SamahoNote Added: 0007822
2014-01-01 21:27Torr SamahoTarget Version => 2.0
2014-01-01 21:27Torr SamahoStatusnew => feedback
2014-01-01 21:37Edward-sanNote Added: 0007824
2014-01-01 21:37Edward-sanStatusfeedback => new
2014-01-01 21:39Edward-sanNote Edited: 0007824bug_revision_view_page.php?bugnote_id=7824#r4323
2014-01-01 22:00Edward-sanNote Edited: 0007824bug_revision_view_page.php?bugnote_id=7824#r4324
2014-01-01 22:01Edward-sanNote Edited: 0007824bug_revision_view_page.php?bugnote_id=7824#r4325
2014-01-01 22:09Edward-sanNote Edited: 0007824bug_revision_view_page.php?bugnote_id=7824#r4326
2014-01-01 22:38Edward-sanNote Added: 0007825
2014-01-02 00:30Edward-sanNote Edited: 0007825bug_revision_view_page.php?bugnote_id=7825#r4328
2014-01-02 00:33Edward-sanNote Edited: 0007825bug_revision_view_page.php?bugnote_id=7825#r4329
2014-01-02 00:55Edward-sanNote Edited: 0007825bug_revision_view_page.php?bugnote_id=7825#r4330
2014-01-02 01:15Edward-sanNote Added: 0007826
2014-01-02 02:01Blzut3Note Added: 0007827
2014-01-02 02:05Edward-sanNote Added: 0007828
2014-01-02 02:06Edward-sanNote Edited: 0007828bug_revision_view_page.php?bugnote_id=7828#r4332
2014-01-02 11:30Torr SamahoNote Added: 0007832
2014-01-02 11:40Torr SamahoStatusnew => feedback
2014-01-02 12:16Edward-sanNote Added: 0007838
2014-01-02 12:16Edward-sanStatusfeedback => new
2014-01-02 12:20Edward-sanNote Edited: 0007838bug_revision_view_page.php?bugnote_id=7838#r4338
2014-01-02 12:32Edward-sanNote Edited: 0007838bug_revision_view_page.php?bugnote_id=7838#r4339
2014-01-02 12:33Edward-sanNote Edited: 0007838bug_revision_view_page.php?bugnote_id=7838#r4340
2014-01-02 15:28Torr SamahoNote Added: 0007841
2014-01-02 15:44Torr SamahoFile Added: linuxClientFix.patch
2014-01-02 15:44Torr SamahoNote Added: 0007842
2014-01-02 15:44Torr SamahoAssigned To => Torr Samaho
2014-01-02 15:44Torr SamahoStatusnew => needs testing
2014-01-02 16:18Edward-sanNote Added: 0007843
2014-01-02 17:36Torr SamahoNote Added: 0007849
2014-01-02 17:36Torr SamahoStatusneeds testing => resolved
2014-01-02 17:36Torr SamahoFixed in Version => 2.0
2014-01-02 17:36Torr SamahoResolutionopen => fixed
2014-01-02 18:16Edward-sanNote Added: 0007852
2014-01-02 18:38Torr SamahoNote Added: 0007853
2017-11-13 09:16LeonardRelationship addedrelated to 0003334
2017-11-13 14:13LeonardNote Added: 0018869
2017-11-13 14:13LeonardStatusresolved => needs testing
2017-11-13 14:13LeonardResolutionfixed => reopened
2017-11-13 14:49Edward-sanNote Added: 0018870
2017-11-13 16:12LeonardNote Added: 0018872
2017-11-13 16:12LeonardStatusneeds testing => needs review
2017-11-13 16:12LeonardFixed in Version2.0 =>
2017-11-13 16:12LeonardTarget Version2.0 => 3.1
2017-11-17 15:20DuskAssigned ToTorr Samaho => Leonard
2017-11-19 10:49Torr SamahoNote Added: 0018891
2017-11-19 10:50Torr SamahoStatusneeds review => needs testing
2018-05-07 09:44LeonardRelationship addedrelated to 0003418
2024-03-01 02:42Ru5tK1ngNote Added: 0023139
2024-03-01 02:42Ru5tK1ngStatusneeds testing => resolved
2024-03-01 02:42Ru5tK1ngResolutionreopened => fixed

Notes
(0007822)
Torr Samaho   
2014-01-01 21:27   
Can you compile older 2.0 builds and find out which changeset caused this?
(0007824)
Edward-san   
2014-01-01 21:37   
(edited on: 2014-01-01 22:09)
alright, trying to compile and check ...

[edit]Torr, can you reproduce this in your 32bit linux machine?

[edit2]what the ... after upgrading ubuntu from 13.04 to 13.10 now when I try to run a server with compiled zandronum (1.2 works fine) I get *** buffer overflow detected *** message ...

[edit3]debug build works fine and I can still reproduce the problem. I'll try checking old revisions again ...
(0007825)
Edward-san   
2014-01-01 22:38   
(edited on: 2014-01-02 00:55)
It's hard to test, because the linux compile problems were fixed in recent commits ... so I have to proceed from the beginning of the codebase upgrades and see...

[edit]it seems that the problem started with'https://bitbucket.org/Torr_Samaho/zandronum/commits/ba94cf3b16e1bad293c36db650ff412ca13f94ae [^]' , no idea how is it that possible...

[edit2]scratch that, it seems that I can still reproduce with'https://bitbucket.org/Torr_Samaho/zandronum/commits/bc34588bbc13be68b4fb077e9683b44fe6ab4c56 [^]' ... time to recheck again
(0007826)
Edward-san   
2014-01-02 01:15   
Ok, culprit is'https://bitbucket.org/Torr_Samaho/zandronum/commits/2deeea24afbf719c74bcb11576a24b61ab4565e8 [^]' :

Quote

- Added partial support for a signal based timer under Linux/Mac OS X in order to make cl_capfps effective at limiting CPU usage.
(0007827)
Blzut3   
2014-01-02 02:01   
The signalling code was improved in ZDoom r3270/r3276. I do recall the old method being a little flaky in keeping 35hz (IIRC the frame rate would some times drop below 35 even though without cl_capfps it would obtain 60 or so).
(0007828)
Edward-san   
2014-01-02 02:05   
(edited on: 2014-01-02 02:06)
I can confirm that the code from specified zdoom rev works fine on my end.
(0007832)
Torr Samaho   
2014-01-02 11:30   
So GZDoom revision 880 is unaffected by the problem?
(0007838)
Edward-san   
2014-01-02 12:16   
(edited on: 2014-01-02 12:33)
Since the gzdoom multiplayer code is different from zandronum, I thought I didn't need to test it, but it should be "affected", since it inherits code from zdoom r2310.


[edit]Just to note: I tested with gzdoom 880, it works fine when I run 2 clients in multiplayer.
(0007841)
Torr Samaho   
2014-01-02 15:28   
I can reproduce the problem in my Ubuntu VM. Perhaps it has to do with the prediction. I'll have to look into this.
(0007842)
Torr Samaho   
2014-01-02 15:44   
Can somebody check if the attached patch fixes the problem?
(0007843)
Edward-san   
2014-01-02 16:18   
Yes, it works properly.
(0007849)
Torr Samaho   
2014-01-02 17:36   
Thanks for checking!
(0007852)
Edward-san   
2014-01-02 18:16   
that'd be good if the linux betas could be re-released with this patch on...
(0007853)
Torr Samaho   
2014-01-02 18:38   
I think we should never re-release beta builds with manually added patches. The beta builds are just development snapshots. If we fix something important, we can just release a new beta build.
(0018869)
Leonard   
2017-11-13 14:13   
Quote
<@Blzut3>: and imo we should reevaluate enabling the linux timer interface. I think 3.0 has the good code.

I can't test on linux myself so someone else will have to build/test this in client mode.
Here's a commit that re-adds the linux timer for clients.
(0018870)
Edward-san   
2017-11-13 14:49   
Just tested the build with 1 and 2 players connecting to a server, it works fine on my end.
(0018872)
Leonard   
2017-11-13 16:12   
Quote
<edward-san>: <Leonard> so linux clients with cl_capfps work? <- yes

I guess Blzut was right then.
Here's the PR to revert the fix.
(0018891)
Torr Samaho   
2017-11-19 10:49   
I added your patch.
(0023139)
Ru5tK1ng   
2024-03-01 02:42   
Since no new reports of this issue, this will be marked as resolved