[Bug] Inter-Hexen: Key mappings reset when playing Deathkings

[NightFright2k19]

Upon entering HexenDK, my customized keyboard setup is resetting to default.

PS: It's possible this happened since there were new config entries with the latest update. Is the port resetting key configs in such cases?

[JNechaevsky]

PS: It's possible this happened since there were new config entries with the latest update. Is the port resetting key configs in such cases?

Looks likes it was. 😟

Sigh. I think I was able to caught it one or two times, but never was able to reproduce it properly. Recent change hopefull will fix it, I've tried to add/remove new controls and features variables, looks likes it's all fine.

[NightFright2k19]

Thanks! Surely stuff one wants to have working properly before an official release. ^^ Will resume my DK playtesting session, then. Fingers crossed!

[JNechaevsky]

Absolutely true! I'll merge autoload for DK soon, this addon definitely deserves it.

[JNechaevsky]

And done! Once hexdd.wad loaded, a folder hexdd.wad will be created in autoload folder. Absolutely same way to other autoloads.

[Meerschweinmann]

And done! Once hexdd.wad loaded, a folder hexdd.wad will be created in autoload folder. Absolutely same way to other autoloads.

Nice! Then i can put separate widescreen assets with deathkings title screen in Hexdd folder 😀👌

[NightFright2k19]

Um, I'm afraid it's still happening. Not completely, but for example my jump key is reset when I load a PWAD, in this case caldera.wad...

[JNechaevsky]

Please advice, does it happens every time new pwad is loaded or just randomly? I can't reproduce it on my side. 😕 Also, did you tried to update source code by git pull? I made some changes yesterday for Hexen so now it is possible to run on Linux. Not sure it was the case, but...

[NightFright2k19]

Currently I'm always playing with "bleeding edge" builds. I create a new build every time before I start a game. What I can tell you is that it happened when I switched from playing Deathkings to a custom PWAD, in this case caldera.wad.

It did NOT happen when I switched from one pwad to another, e.g. caldera.wad to chuxen.wad. Right now, I cannot reproduce it by switching back to Deathkings, it seems. Maybe it also has to do with using different executable versions. I will observe this further.

[NightFright2k19]

Update: I compared now a recent back of inter-hexen.ini from yesterday. At least the following variables are reset (basically all which I changed from default):

key_flyup 
key_flydown
key_flycenter 
key_invleft 
key_invright 
key_useartifact
key_jump
key_buddha

This probably won't help much since it doesn't reveal anything new. It's a total reset.

What I did just now:

• Restore that ini backup
• Load caldera.wad as PWAD
• Result: NO ini reset

I don't get this. It definitely happened when I switched from Deathkings to Caldera. But only the first time.

[JNechaevsky]

Total maze, but thank you for suggestion any ways. 🤗 Could you please git pull again, I made small additional change for Hexen.

[NightFright2k19]

Thanks for keeping it up. I'll keep an eye on this and will report back in a few days. By then it should be clear whether it's fixed or not. Fingers crossed!

[JNechaevsky]

I was able to catch it, finally. Pretty odd steps:

1. Start a game normally.
2. Make a save in any slot.
3. Press DEL on saved slot, and then Y.
4. Restart the game. Controls will reset to defaults.

Something went wrong with action confirming, for some reason keyboard binding reset is invoked.

[JNechaevsky]

Oh dammit, missing break; below this line was executing M_ResetBinds() two lines below! 🤤

[NightFright2k19]

Right, savegame deletion. I did that after finishing regular Hexen and then again after DK. Would explain why it didn't happen more than once after starting a new game. Never thought it might have anything to do with it.

Let's hope that finally fixes it for good. I'll keep backups of my ini files in any case. Old habits die hard. :P