ZDoom

This can probably be closed by way of https://github.com/coelckers/Raze/commi ... 3cc7710ecb.

The double read is because it's loading dinput and xinput when it should do one or the other. The menu code for joysticks needs to 1:1 match GZDoom to fix that and I imagine it will now that the ZScript VM is in there.

So all in all it feels perfect out of the box? That's really good! I'll look into that crash and see what the go is. Hopefully I can reproduce it on my end .

@mjr4077au, I just gave it a quick blast for a few minutes and I can confirm that it's working well in-game. So:

- Yes, it works!
- I found out of box sensitivity a little much.
- I turned down Overall Sensitivity to 0.6. Play felt a lot smoother to me, though that could just be me getting old.

The controller doesn't work quite right in the menus. Using the d-pad to move up and down options makes the highlight two options at a time (if that makes sense). Also, though I could go 'forward' into menus using the A button, the B button didn't seem to back out of options.

All in all, though, this is a great step forward. Thanks for continuing to work on this.


EDIT: After just loading again, it seems that the game was previously 'double reading' my controller. When playing this time the menu navigation was fine and the sensitivity was far too low. The default sensitivity is perfect as is.

Also, the game crashes (Duke Nukem) when using the controller to start a new game. Game fails to load and just hangs before entering the level.

I'll let you know if the above crash and the 'double reading' keeps happening or if there are any more inconsistencies.

@Barry Burton, can you please test this build for me? https://drive.google.com/file/d/1TFZ_kl ... sp=sharing

I'm interested in feedback on:

- Does it work?
- How's the out of box sensitivity (was going for playability at 1.5x sensitivity)?
- What you think as a game pad/joystick user would be optimal?

Dunno if anyone's done any work on this but thought I'd bump just in case. The issue still persists in 0.4.2.

Yeah. It works flawlessly in GZDoom.

Does this controller work in GZDoom?
It uses the same code so the result may be useful.

My controller works fine in menus. However, as analogue input, they don't respond. The triggers don't work either. Out of curiosity I assigned the analogue sticks in the Controls menu as digital movement. The game reads that input but that leads to twitchy movement. Of course, this could all be on me but I thought I should report it just in case.

I am using Raze 0.4.0 on Windows 10 Pro (up to date) and I only have the Duke.GRP file (no other Build game data).