ZDoom

This bug I have recognized this bug a long time ago, but I thought you already knew it or it was reported previously, but, while I played around the latest state of GZDoom, the bug is still here.

While playing a game (I have tried DOOM 1 Ultimate, DOOM 2, Plutonia Experiment, Evilution, Chex Quest 1, Chex Quest 3, all official I-WADs and no any extra P-WADs was used), the "1" key (but, even I'll re-assign the key to another) will won't react to any hits on it.

My build is using SDL2, the operating system is Linux Mint 18.3 (basing on Ubuntu 16 LTS), x64.

If you are interested, the CMake build a cache that keeps the full setup I am using (include stuff that was automatically recognized) and the thing was built: My game setup which may give a similar environment to mine:

Does this happen with any other slot (e.g., shotguns)?

Matt wrote:Does this happen with any other slot (e.g., shotguns)?

Nope, all other keys are all working fine. The only "1" key won't work. As I have explained, it won't work even I'll re-assign it to another key, for example, let "Q" be a "weapon 1" key... Yes, it works, but later, it gives no reaction like it was "1"...

Is it like this even if you load a mod that replaces the fist and chainsaw? I'm wondering if it might be the ZScript/Decorate code for the saw in gzdoom.pk3...

Matt wrote:Is it like this even if you load a mod that replaces the fist and chainsaw? I'm wondering if it might be the ZScript/Decorate code for the saw in gzdoom.pk3...

No, I don't use any mods for now, I use the stuff that is as-is in the repository, or do you think the bug is probably in the scripts?

What he wants to know is if the actual weapons in the slot are the deciding factor. For example, if you assign them to another slot, does it also happen there? And does it happen when other weapons are in slot 1 and not the chainsaw?

Or if you remove one of the weapons, does it help?

No, I didn't any re-assigning of weapons between slots, everything has default states. The only thing I have changed the keyboard setup as an attempt to escape this bug... I have attached my game config into the main post that you can use to better analyze the stuff...

So what happens if you do change weapon assignments?

Graf Zahl wrote:So what happens if you do change weapon assignments?

I'll test that at evening (right now I'm at my job)... But the question: how to do that?

Behold the 'setslot' CCMD!

Okay, just now I have tried a thing: I did the attempt to change control key for "Weapon 1" (at the first time I did the clear by backspace key), and when I hit "1", in result I got the "ENTER". The question: are key aliases correct? Gonna into the source code to check out what happens...

EDIT: After the game restart, the bug is going away, but then it returns back in some random moment...
And, it's no matter what I play: DOOM, DOOM 2 or Chex Quest...

That sounds more like a problem with your keyboard...

Graf Zahl wrote:That sounds more like a problem with your keyboard...

My keyboard is fine and all keys are working fine, but maybe SDL2 build side?
Anyway, I'll try to put back the game config I have uploaded here and compare the differences...

Do you have any other SDL2 games to check this with? That's what I would check first.

Rachael wrote:Do you have any other SDL2 games to check this with? That's what I would check first.

I have my own game engine that using SDL2, but, it does use of own built hg-libsdl-org that is statically linked. I have checked that, and it works fine. I have DosBox and DosBox-X are also SDL users (DosBoxX at me does use of SDL2 from a system). I have tried that and looks like everything works fine...