ZDoom Controller Recommended Mapping

mediamogul

@thedatacereal said in ZDoom Controller Recommended Mapping:

Any ideas what may cause this?

It could be an issue with the driver. Is it just the right trigger, or will the left not map either?

KN4THX

@mediamogul Trying to bind the bottom 'X' button to USE or MOVE FORWARD (yes, I know, just a test :)) doesn't set the bind but it detects the button press and backs out of the active bind without actually binding. RIGHT TRIGGER (joy10) does the same for FIRE but can be bound to secondary fire. This happens for many of the control options. It's throwing me for a loop why certain buttons can be bound for only certain things. I'd understand if it was all or none.

Ok, I never proceeded before because I didn't see any reason to if binds weren't taking, but in the middle of typing this I decided to see what in-game actions did and sheesh, they seem to work.

Weirdest thing but I'll take it. Now the hard part of determining which functions to leave off the controller. Forgot there is an inventory system in this one.

I appreciate the help as always.

edmaul69

@thedatacereal here is how i do it on my ps3 controller. Im ripping off @mediamogul ‘s list. I added R2 and L2 as i prefer them for triggers.

Left Analog: Movement
Right Analog: POV
DPad Up:
Dpad Down:
Dpad Left: Cycle Inventory Back
Dpad Right: Cycle Inventory Forward
L1 Button: Throw Grenade
R1 Button: Reload Weapon
L2 Button: Fire Left-handed Weapon/Left Punch
R2 Button: Fire Right-handed Weapon/Right Punch
B Button: Kick
A Button: Jump
Y Button: Cycle Weapon Back
X Button: Cycle Weapon Forward
L3 Button: Toggle Run
R3 Button: Toggle Crouch
Select Button: Map
Start Button: Taunt

mediamogul

@thedatacereal said in ZDoom Controller Recommended Mapping:

It's throwing me for a loop why certain buttons can be bound for only certain things. I'd understand if it was all or none.

These inconsistencies, scattered throughout various software, are why I mostly key-map everything on my controllers. Thinking on it here, I believe I actually key-map everything except for the RetroArch cores which have always proven to behave very reliably for controller input. Granted, key-mapping can be an involved process and I'm not directly advocating that as a solution to you, but in certain situations, with some controllers, I've found it to be a pretty reliable nuclear option.

KN4THX

@edmaul69 Awesome, thanks! That config for Brutal Doom looks great and after reading about that mod I definitely want to add it to my setup. I'm thinking I may stick to a keyboard for Heretic as having to use the right analog for specific features seems to be too sensitive and there are too many necessary features to boot try to include them.

@mediamogul By keymapping are you referring to literally mapping keys to the keyboard or just manually editing the cfg file? I could see that second method being very easy once you are familiar with your particular controller and knowing what your tastes are.

edmaul69

@thedatacereal brutal doom and project brutality mods are awesome. Heretic and hexen games are some of the few that it doesnt work on.

mediamogul

@thedatacereal said in ZDoom Controller Recommended Mapping:

By keymapping are you referring to literally mapping keys to the keyboard or just manually editing the cfg file? I could see that second method being very easy once you are familiar with your particular controller and knowing what your tastes are.

I was actually referring to key-mapping a controller, such as mapping the 'Enter' keyboard key to a controller's 'Start' button. Afterwards, the software just thinks your using a keyboard. Aside from RetroArch, most of the available software in RetroPie tends to behave more predictably with keyboard input. You also have more flexibility in setup. For example, I run 32 systems and have every non-RetroArch emulator set to mirror the RetroArch commands. So everything I use exits with 'Select+Start', brings up a menu with 'Select+X', takes a screenshot with 'Select+Y' ...etc.

KN4THX

@mediamogul Yes, that's what I was getting at, I left some important words out of my reply :/. Do you just use xboxdrv for this or do you recommend another utility? I had looked at the xboxdrv option for dos games before when I saw a guide you posted but hadn't pursued it as I wasn't sure if I wanted to stick with my ps3 controllers yet and was ordering a new controller every two weeks for testing. If that's the method you still use I have some questions about that procedure I'd like to ask.

mediamogul

@thedatacereal said in ZDoom Controller Recommended Mapping:

Do you just use xboxdrv for this or do you recommend another utility?

I use xboxdrv personally, as it has the most options available. However, Linux Joystick Mapper also has a solid feature set.

If that's the method you still use...

It's still roughly the same method. I've improved it over time to allow both automatic and manual map selection, as well as dynamic mapping based on whatever controller I have plugged in. My setup also waits to start the maps until the Runcommand menu has disappeared so that it can be navigated when active. I never added that stuff to the guide due to it already being pretty complex.

... I have some questions about that procedure I'd like to ask.

Ask away.

KN4THX

@mediamogul Actually, rereading the documentation answered my questions so far. It was a lot to take in at first but makes perfect sense once I put it all in order in my head. Thanks for the great write-up!

mediamogul

@thedatacereal

Not a problem. If you run into any trouble, just let me know.