Anonymous | Login | Signup for a new account | 2024-05-04 08:07 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 | ||||
0004061 | Zandronum | [All Projects] Bug | public | 2022-12-19 04:59 | 2024-04-09 04:20 | ||||
Reporter | Kaminsky | ||||||||
Assigned To | Kaminsky | ||||||||
Priority | normal | Severity | minor | Reproducibility | always | ||||
Status | resolved | Resolution | fixed | ||||||
Platform | OS | OS Version | |||||||
Product Version | 3.2 | ||||||||
Target Version | 3.2 | Fixed in Version | 3.2 | ||||||
Summary | 0004061: Free chasecam gets "locked" while you're dead. | ||||||||
Description | If you die while using the free chasecam, you will be unable to move the view around the actor that you're spying on. This is because in P_PlayerThink, their angle/pitch are updated based on input only when they're not dead. If they're dead, then P_PlayerThink calls P_DeathThink which changes the player's angle/pitch to gradually face towards the actor that killed them instead. | ||||||||
Steps To Reproduce | 1. Start an offline multiplayer game with at least one bot. 2. Spy on the bot with the chasecam and "cl_freechase" enabled. 3. Type "kill" in the console. 4. You are now unable to move your view around the bot until you respawn. | ||||||||
Attached Files | |||||||||
Notes | |
(0023333) Kaminsky (developer) 2024-03-10 14:40 |
This is addressed in this merge request:'https://foss.heptapod.net/zandronum/zandronum-stable/-/merge_requests/47 [^]' |
(0023488) Ru5tK1ng (updater) 2024-03-24 21:21 |
This was merged in:'https://foss.heptapod.net/zandronum/zandronum-stable/-/commit/e7872589deb3763b559c513f31a444e7709442ad [^]' |
(0023575) Ru5tK1ng (updater) 2024-04-09 04:20 |
Tested with the latest 3.2 beta and the chase came worked correctly both online and offline when following the steps to reproduce. |
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 |
2022-12-19 04:59 | Kaminsky | New Issue | |
2022-12-19 04:59 | Kaminsky | Status | new => assigned |
2022-12-19 04:59 | Kaminsky | Assigned To | => Kaminsky |
2024-03-10 14:40 | Kaminsky | Note Added: 0023333 | |
2024-03-10 14:40 | Kaminsky | Status | assigned => needs review |
2024-03-24 21:21 | Ru5tK1ng | Note Added: 0023488 | |
2024-03-24 21:22 | Ru5tK1ng | Status | needs review => needs testing |
2024-04-09 04:20 | Ru5tK1ng | Note Added: 0023575 | |
2024-04-09 04:20 | Ru5tK1ng | Status | needs testing => resolved |
2024-04-09 04:20 | Ru5tK1ng | Resolution | open => fixed |
2024-04-09 04:20 | Ru5tK1ng | Fixed in Version | => 3.2 |
Copyright © 2000 - 2024 MantisBT Team |