Controller problem

[desert_doomer]

For the last few years I've been using a PS4 controller to play Doom on gzdoom 4-10-0 and it worked fine. I downloaded gzdoom 4-14-1 today and when I activate the controller my view shoots straight up and spins around. The only way I found to stop it was to set the X-Rotation and Y-Rotation sensitivities to zero.

I tried setting the controls for the controller but no change (by the way I also noticed I could not assign the x button to anything where beforehand I could).

So I went back to 4-10-0 and now it's doing the same thing where it worked fine this morning.

Deleted both versions, deleted the ini file, rebooted the computer, unpacked the 4-10-0 zip file and tried again. Same thing.

Tried playing some other games and had no issues with the controller at all.

Any idea why this is happening? When I ran the new version did a dll file get overwritten or a registry entry get reset, anything like that? Or maybe something in the ini file I need to change?

Thanks to all.

My legacy computer I keep around for playing old games -

Dell OptiPlex 780
Intel Core Duo CPU E8400 @3.00GHZ
4 Gigs ram
DirectX 11

NVIDIA GeForce 210
2 Gig ram
Display Mode: 1920 x 1080 (32 bit)(60Hz)

Windows 7 Profession 64 bit (Build 7601)

[Rachael]

Try increasing the dead zone for the controls that keep the player spinning or pitching when the sticks are stationary.

[desert_doomer]

Tried that... tried pretty much everything I could think of.

But get this -

When I first installed version 4-10-0 some years ago I made a copy of the ini file. I tried using this as the active ini file and the controller works perfectly.

However, if I allow either version to generate a new ini file I get the spin.

The kicker? The text in both files is exactly the same.

Looking into it I found the backup file size is about 31k whereas a newly generated ini file is about 15k.

The 31k file works, the 15k file doesn't no matter what I do.

I have no idea why but that's honestly what's going on. Maybe the file format was changed, or some kind of compression was added to the ini file generation? I know it sounds crazy but that's what is happening.

I'll see if I can find out anything else. Thanks for the reply!

[Nash]

desert_doomer: Which PS4 controller specifically are you using, and what do I need (besides the controller itself) to get it all set up on the PC?

I don't have a PS4 controller but I'm willing to purchase one, because it's the only way I'm able to actually debug/test this stuff.

[desert_doomer]

The only information I could find was "HID-compliant game controller" in the properties window. I bought it at Target about four years ago when my old controller conked out. There's a label on the underside but it's long since worn off.

All I had to do was plug it into my Win7 computer and run the calibration program and it worked. I'm pretty sure Win10 and 11 also has controller software. Should be pretty straight forward. Then go into zdoom options, enable the controller, assign the buttons and you're good to go.

I also use the AntimicroX keymapper program for older games that don't have controller support but it's clunkier than true controller support.

I'm going to check out a few thrift stores and see if I can find an XBox controller and see what happens with that.

Thanks and good luck!

[desert_doomer]

I think I figured out the spin thing, when a new ini file is created XRotation is set to 'Turning' and YRotation is set to 'Look Up/Down' when they need to be assigned to the z axis instead. I should have seen that right off but I never was very good with geometry.

Also having two versions may have caused an issue, I most likely used one version to generate the ini then used that ini to run the other version. Probably best to pick one and stick with it.

Anyway it works and there's no reason to pick over details when there are cyberdemons to be slain. Sorry if I wasted anyone's time and I'd like to thank everyone for the help, let's mark this one as solved.

Happy dooming!

[desert_doomer]

I'll have to stick with 4-10-0 as I found 4-14-1 won't allow me to assign Joy2 to any control (the X button on the PS4 controller). It just doesn't see it.