This so far only seems to happen with Project Brutality, but this may (or may not) be a serious issue.
So, someone 6 months ago reported having bizarre and weird issues with Project Brutality. The cause was eventually tracked down to my written PDA framework implementation in PB_EventHandler class and GZDoom's melt screen effect. In 4.3.3 it crashes after showing bizarre behaviour, in later versions it crashes immediately.
Unfortunately I (and others in the PB Dev team) got no luck replicating the problem so far, so I am leaving this bug report in case someone gives a clue on what happens. Investigating the crash dumps in the linked GitHub thread may help too. I am reporting this because it seems to be more of a GZDoom bug than PB.
GZDoom has weird behaviour in some conditions on PB
Moderator: GZDoom Developers
-
- Posts: 422
- Joined: Fri Dec 22, 2017 1:53 am
- Graphics Processor: ATI/AMD (Modern GZDoom)
-
- Lead GZDoom+Raze Developer
- Posts: 49183
- Joined: Sat Jul 19, 2003 10:19 am
- Location: Germany
Re: GZDoom has weird behaviour in some conditions on PB
Moving out of the way, with the given info it's hard to say.
-
- Posts: 1
- Joined: Sun Sep 27, 2020 1:55 pm
- Graphics Processor: ATI/AMD (Modern GZDoom)
Re: GZDoom has weird behaviour in some conditions on PB
Hi, I am affected by the bug. Here are my specs:
Operating System: Windows 10 Pro 64-bit (Version 1903, Build 18362)
Processor: Intel i7-4790K CPU
Graphic Card: AMD Radeon R9 280x
Memory: 16GB RAM
Tested Versions: GZDoom 4.3.3 - 4.4.2 & gzdoom-x64-g4.5pre-150-gc3dc84297
LZDoom 3.85
Newly installed, no mods (except PB), no changes to the Doom.ini
The bug is also on my brother's pc. I will submit his specs and crash reports later.
Operating System: Windows 10 Pro 64-bit (Version 1903, Build 18362)
Processor: Intel i7-4790K CPU
Graphic Card: AMD Radeon R9 280x
Memory: 16GB RAM
Tested Versions: GZDoom 4.3.3 - 4.4.2 & gzdoom-x64-g4.5pre-150-gc3dc84297
LZDoom 3.85
Newly installed, no mods (except PB), no changes to the Doom.ini
The bug is also on my brother's pc. I will submit his specs and crash reports later.
You do not have the required permissions to view the files attached to this post.
-
- Posts: 422
- Joined: Fri Dec 22, 2017 1:53 am
- Graphics Processor: ATI/AMD (Modern GZDoom)
Re: GZDoom has weird behaviour in some conditions on PB
https://github.com/pa1nki113r/Project_B ... -701338402
The issue has now been found to be mouse-related and SendNetworkEvent-related issue.
Any further ideas?
Edit: The issue only happens on programmable mice, other ones work fine.
The issue has now been found to be mouse-related and SendNetworkEvent-related issue.
Any further ideas?
Edit: The issue only happens on programmable mice, other ones work fine.
-
- Posts: 422
- Joined: Fri Dec 22, 2017 1:53 am
- Graphics Processor: ATI/AMD (Modern GZDoom)
Re: GZDoom has weird behaviour in some conditions on PB
Now that I got more information from load_andre, I think the summary is pretty much this: The bizarre behaviour only happens if:
1. in_mouse is set to either 0 or 3 (which I presume is RawInput).
2. Wipe Effect is set to "Melt".
3. Programmable mice is used.
4. Mouse input is posted *just* before the melt effect starts (meaning the very first tic).
InputProcess gets called in the following event processing code. Then SendNetworkEvent gets called from ZScript code.
I will try making a minimal sample about this later.
1. in_mouse is set to either 0 or 3 (which I presume is RawInput).
2. Wipe Effect is set to "Melt".
3. Programmable mice is used.
4. Mouse input is posted *just* before the melt effect starts (meaning the very first tic).
InputProcess gets called in the following event processing code. Then SendNetworkEvent gets called from ZScript code.
I will try making a minimal sample about this later.