Anonymous | Login | Signup for a new account | 2025-07-27 16:28 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 | ||||
0003272 | Zandronum | [All Projects] Bug | public | 2017-09-23 14:14 | 2018-09-30 23:24 | ||||
Reporter | Pawlacz | ||||||||
Assigned To | Dusk | ||||||||
Priority | normal | Severity | minor | Reproducibility | sometimes | ||||
Status | closed | Resolution | no change required | ||||||
Platform | Linux | OS | Linux Mint | OS Version | 18.1 | ||||
Product Version | 3.0 | ||||||||
Target Version | Fixed in Version | ||||||||
Summary | 0003272: Error message appears in Multiplayer due to a looping projectile | ||||||||
Description | During a multiplayer game when a projectile uses a user_x based condition for limiting a looping state a error message appears: "Warning: Breaking infinite loop in actor LauncherGasGrenade. Current offset from spawn state is 11" The error message does not appear all the time so it takes a while for it to show up, also no gameplay breaking bug happens as in the game will continue normally despite the error message. I tried changing the Projectile actor a few times to fix it somehow but all it does is that the number reported is not very large anymore. Offending actor: LauncherGasGrenade | ||||||||
Steps To Reproduce | 1. Load the loopingbug.pk3 mod 2. Host a server and connect to it 3. Keep firing till the error message appears | ||||||||
Attached Files | ![]() | ||||||||
![]() |
|
Dusk (developer) 2017-09-23 16:46 |
The client doesn't predict the A_JumpIf call so it assumes it to not jump until the server instructs the client otherwise. So the client can get stuck in the loop. This is not a bug but rather an unfortunate limitation of the client-side prediction involved. Since the GasCloud actor appears to be decorative, I suggest to split the gas-spawning code into a new CLIENTSIDEONLY actor. That way there's no networking involved in the loop and it should work fine. |
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 |
2017-09-23 14:14 | Pawlacz | New Issue | |
2017-09-23 14:14 | Pawlacz | File Added: loopingbug.pk3 | |
2017-09-23 16:46 | Dusk | Note Added: 0018360 | |
2017-09-23 16:46 | Dusk | Status | new => resolved |
2017-09-23 16:46 | Dusk | Resolution | open => no change required |
2017-09-23 16:46 | Dusk | Assigned To | => Dusk |
2018-09-30 23:24 | Blzut3 | Status | resolved => closed |
Copyright © 2000 - 2025 MantisBT Team |