Anonymous | Login | Signup for a new account | 2025-06-18 04:57 UTC | ![]() |
My View | View Issues | Change Log | Roadmap | Zandronum Issue Support Ranking | Rules | My Account |
View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
ID | Project | Category | View Status | Date Submitted | Last Update | ||||
0003920 | Zandronum | [All Projects] Bug | public | 2021-11-01 21:08 | 2021-12-04 18:15 | ||||
Reporter | RushJet1 | ||||||||
Assigned To | Kaminsky | ||||||||
Priority | normal | Severity | minor | Reproducibility | random | ||||
Status | resolved | Resolution | fixed | ||||||
Platform | Microsoft | OS | Windows 10 | OS Version | XP/Vista/7 | ||||
Product Version | 3.1-beta | ||||||||
Target Version | Fixed in Version | 3.1-beta | |||||||
Summary | 0003920: "Connection Interrupted" joining an online game with CL_StartAsSpectator 0 | ||||||||
Description | 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. | ||||||||
Steps To Reproduce | Join a server with CL_StartAsSpectator false | ||||||||
Attached Files | |||||||||
![]() |
|
Kaminsky (developer) 2021-11-07 20:33 |
This commit:'https://osdn.net/projects/zandronum/scm/hg/zandronum-stable/commits/3e9b2a7c87a85f7ed150bf3f569bc2e2456b2510 [^]' should fix the issue. |
Kaminsky (developer) 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. |
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. |
![]() |
|||
Date Modified | Username | Field | Change |
2021-11-01 21:08 | RushJet1 | New Issue | |
2021-11-01 21:33 | Kaminsky | Assigned To | => Kaminsky |
2021-11-01 21:33 | Kaminsky | Status | new => needs review |
2021-11-07 20:33 | Kaminsky | Note Added: 0021826 | |
2021-11-07 20:33 | Kaminsky | Status | needs review => needs testing |
2021-12-04 18:15 | Kaminsky | Note Added: 0021846 | |
2021-12-04 18:15 | Kaminsky | Status | needs testing => resolved |
2021-12-04 18:15 | Kaminsky | Fixed in Version | => 3.1-beta |
2021-12-04 18:15 | Kaminsky | Resolution | open => fixed |
Copyright © 2000 - 2025 MantisBT Team |