MantisBT - Zandronum
View Issue Details
0004374Zandronum[All Projects] Bugpublic2024-08-07 00:132024-08-08 01:52
unknownna 
Kaminsky 
normalminoralways
resolvedfixed 
3.1 
3.23.2 
0004374: Spectator inherits HUD and flashes of formerly viewed player after map resets when view is reset back to self
There seems to be some odd behavior with the coop spy for spectators in modes with map resets like (team)possession.

* Adding 2 bots and spying on the bot with the highest player number causes the view to reset back to yourself, yet you still see the HUD and pickup/pain flashes of the formerly viewed bot.

What's actually happening is that the coop spy for some reason automatically uses "spynext" after map resets if you're a spectator, causing it to desync. It doesn't do this if you're a regular player in-game.
1. zandronum -iwad doom2.wad +sv_weaponstay 1 +sv_nomonsters 1 +skill 4 +possession 1 +sv_possessioncountdowntime 8 +sv_possessionholdtime 5 +addbot betus +addbot chubbs +map map01 +spectate
2. Use "spynext" twice to spy on Chubbs.
3. When the countdown ends, your client will erroneously use "spynext", reverting the view back to yourself while still inheriting Chubbs' HUD and pickup/pain flashes.
No tags attached.
Issue History
2024-08-07 00:13unknownnaNew Issue
2024-08-07 14:31KaminskyNote Added: 0023912
2024-08-07 14:31KaminskyAssigned To => Kaminsky
2024-08-07 14:31KaminskyStatusnew => needs review
2024-08-07 14:31KaminskyTarget Version => 3.2
2024-08-07 21:30KaminskyNote Added: 0023916
2024-08-07 21:30KaminskyStatusneeds review => needs testing
2024-08-08 01:52unknownnaNote Added: 0023918
2024-08-08 01:52unknownnaStatusneeds testing => resolved
2024-08-08 01:52unknownnaFixed in Version => 3.2
2024-08-08 01:52unknownnaResolutionopen => fixed

Notes
(0023912)
Kaminsky   
2024-08-07 14:31   
This should be fixed with'https://foss.heptapod.net/zandronum/zandronum-stable/-/merge_requests/159 [^]'
(0023916)
Kaminsky   
2024-08-07 21:30   
This has been pushed in:'https://foss.heptapod.net/zandronum/zandronum-stable/-/commit/6382894d1120992529f527b58e91fdcf19822403 [^]'
(0023918)
unknownna   
2024-08-08 01:52   
This seems to be fixed now. Great work as always.