MantisBT - Zandronum
View Issue Details
0003920Zandronum[All Projects] Bugpublic2021-11-01 21:082021-12-04 18:15
RushJet1 
Kaminsky 
normalminorrandom
resolvedfixed 
MicrosoftWindows 10XP/Vista/7
3.1-beta 
3.1-beta 
0003920: "Connection Interrupted" joining an online game with CL_StartAsSpectator 0
If CL_StartAsSpectator is set to false, the game will make you join the game immediately upon joining the server or upon map change. In Zandro 3.0.1 this works as intended, but in 3.1 this always results in a "Connection Interrupted!" message at the bottom of the screen, which locks out player movement entirely. You can still be fragged, but your corpse will be stuck in the first frame of its death animation. You can fix this by spectating and rejoining.

If CL_StartAsSpectator is true, joining the game does not have this effect. This happens when first joining a server and on map change (join an empty server with 3.1 running to see this). Happens on two different machines.

I put "Random" for reproducibility because it randomly will not do this, but more often than not in my experience it does, something like 80% of the time.
Join a server with CL_StartAsSpectator false
No tags attached.
Issue History
2021-11-01 21:08RushJet1New Issue
2021-11-01 21:33KaminskyAssigned To => Kaminsky
2021-11-01 21:33KaminskyStatusnew => needs review
2021-11-07 20:33KaminskyNote Added: 0021826
2021-11-07 20:33KaminskyStatusneeds review => needs testing
2021-12-04 18:15KaminskyNote Added: 0021846
2021-12-04 18:15KaminskyStatusneeds testing => resolved
2021-12-04 18:15KaminskyFixed in Version => 3.1-beta
2021-12-04 18:15KaminskyResolutionopen => fixed

Notes
(0021826)
Kaminsky   
2021-11-07 20:33   
This commit:'https://osdn.net/projects/zandronum/scm/hg/zandronum-stable/commits/3e9b2a7c87a85f7ed150bf3f569bc2e2456b2510 [^]' should fix the issue.
(0021846)
Kaminsky   
2021-12-04 18:15   
Since there hasn't been any more reports of the "connection interrupted" message appearing if "cl_startasspectator" was disabled upon connecting to a server, it's safe to say the issue has been resolved for good.