Anonymous | Login | Signup for a new account | 2024-05-02 18:59 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 | ||||
0003107 | Zandronum | [All Projects] Bug | public | 2017-04-29 08:33 | 2018-09-30 21:45 | ||||
Reporter | Cutman | ||||||||
Assigned To | |||||||||
Priority | high | Severity | major | Reproducibility | always | ||||
Status | closed | Resolution | fixed | ||||||
Platform | Microsoft | OS | Windows | OS Version | XP/Vista/7 | ||||
Product Version | 3.0-beta | ||||||||
Target Version | 3.0 | Fixed in Version | 3.0 | ||||||
Summary | 0003107: Issues with weapon switching and state jumps | ||||||||
Description | In 3.0 we've started to notice people getting invalid weapon state errors online. It's difficult to pinpoint the issue but one of our weapons can reproduce it every time. The error does not appear in 2.1.2. I've made a Doom version of our weapon. Sadly it's still a little complicated but I couldn't come up with a more minimal example (excuse the graphics). I'll explain what it does: You fire the weapon once to activate it. It then enters a waiting loop. If you press fire again it will deactivate it and fire a projectile. While activated it will heal you if you are damaged (this is where some of the jumps are called). If press and hold fire (while it is not activated) and quickly switch to a regular doom weapon (and keep holding fire), you should get a couple of error messages appear and some graphical glitches. This ONLY happens online, so I assume what is happening is the weapon is getting desynced somewhere. | ||||||||
Steps To Reproduce | 1. Host and join your own server with the file attached, deathmatch 1 map01. 2. Obtain the Plasma Rifle in MAP01 (or cheat to give yourself PlantBarrierWep). 3. Select the weapon. Press and hold the fire button and immediately switch to a different regular weapon. Continue to hold fire. 4. A bunch of error messages should appear. | ||||||||
Additional Information | This "unique" weapon isn't the only weapon causing this. Other weapons that get stuck in a loop and call jumps also have this this problem and is most likely not limited to mm8bdm weapons. | ||||||||
Attached Files | jumptest.wad [^] (1,818 bytes) 2017-04-29 08:33 jumptest2.wad [^] (604 bytes) 2017-04-30 12:10 | ||||||||
Relationships | |||||||||||
|
Notes | |
(0017441) Cutman (reporter) 2017-04-30 12:29 edited on: 2017-04-30 13:14 |
I have uploaded a second example that clears out most of the junk that isn't required to see the bug (it is now a simple nonsense weapon to purely show off the desync, weapon name is "TestWeapon"). Repeat the steps to reproduce to see and you just get a message printed to the screen. Check the DECORATE lump to see some comments that may help identify what causes it. A lot of weapons have been reported to be doing this in various mods, but most are difficult to reproduce. It seems to be the same problem though, a weapon is trying to access states it doesn't have due to desync. I don't think I can release a new MM8BDM until we have an answer to this. |
(0017470) WaTaKiD (updater) 2017-04-30 20:12 |
i tested some builds and it seems 'https://bitbucket.org/Torr_Samaho/zandronum/commits/be80717ad949c9eae6c091b929c4cb0d7ee06c3a [^]' is related, as switching from TestWeapon to another weapon was broken, but no error message showed but then with this 'https://bitbucket.org/Torr_Samaho/zandronum/commits/edda8070f9b1011dd162004e6bba9ea9e43922f0 [^]' switching from TestWeapon worked again and the error message showed |
(0017482) Torr Samaho (administrator) 2017-05-01 17:31 |
The graphical glitches should be fixed now. Also the error messages should be gone . You'll still get a warning if you have "cl_showwarnings 1", but it should be safe to ignore that warning for now. SetPlayerPSprite and SetThingFrame should be tested thoroughly to make sure that the client is not blocking any valid commands. |
(0017485) WaTaKiD (updater) 2017-05-01 18:00 |
this build contains the fix: 'https://www.dropbox.com/s/hayd6havowr3my5/zandronum-3.0-r170501-1721-6265097-windows.zip?dl=0 [^]' |
(0017503) Cutman (reporter) 2017-05-01 21:02 |
I've tested it with the mm8bdm weapon and had others test the mods that were also causing the issue. Appears to be fixed. |
(0017526) Ru5tK1ng (updater) 2017-05-02 22:24 |
Thanks for testing and getting others to test other mods as well. Feel free to re-open this ticket if the issue pops up again. |
This issue is already marked as resolved. If you feel that is not the case, please reopen it and explain why. |
|
Supporters: | Marcaek sonicfam1102 |
Opponents: | No one explicitly opposes this issue yet. |
Issue History | |||
Date Modified | Username | Field | Change |
2017-04-29 08:33 | Cutman | New Issue | |
2017-04-29 08:33 | Cutman | File Added: jumptest.wad | |
2017-04-30 12:10 | Cutman | File Added: jumptest2.wad | |
2017-04-30 12:29 | Cutman | Note Added: 0017441 | |
2017-04-30 12:32 | Cutman | Note Edited: 0017441 | View Revisions |
2017-04-30 13:14 | Cutman | Note Edited: 0017441 | View Revisions |
2017-04-30 20:12 | WaTaKiD | Note Added: 0017470 | |
2017-04-30 20:19 | WaTaKiD | Relationship added | child of 0002776 |
2017-05-01 17:31 | Torr Samaho | Note Added: 0017482 | |
2017-05-01 17:31 | Torr Samaho | Status | new => needs testing |
2017-05-01 17:31 | Torr Samaho | Target Version | => 3.0 |
2017-05-01 18:00 | WaTaKiD | Note Added: 0017485 | |
2017-05-01 21:02 | Cutman | Note Added: 0017503 | |
2017-05-02 22:24 | Ru5tK1ng | Note Added: 0017526 | |
2017-05-02 22:24 | Ru5tK1ng | Status | needs testing => resolved |
2017-05-02 22:24 | Ru5tK1ng | Resolution | open => fixed |
2017-05-02 22:24 | Ru5tK1ng | Fixed in Version | => 3.0 |
2017-05-07 14:52 | Torr Samaho | Relationship added | related to 0002832 |
2018-09-30 21:45 | Blzut3 | Status | resolved => closed |
Copyright © 2000 - 2024 MantisBT Team |