Disable DirectInput?

[gandhi_the_peacemaker]

Hi, all.

I just downloaded this game and decided to try it out. Plugged in an old DirectInput controller (Saitek Cyborg Rumble Pad V3 or something similar), the key bindings were all wonky. Decided to try out a working x360ce binding to emulate XInput. Now the game is sensing inputs from both the DirectInput Saitek and the XInput-emulating x360ce.

Essentially it's recognizing two different controllers pressing different buttons at the same time.

Any way to disable the DirectInput recognition so that it defaults to the x360ce input?

Thanks for the help.

[gandhi_the_peacemaker]

Bump to front page, could use some help.

[mirHL]

Define wonky.. could it be deadzones were just not set?

[gandhi_the_peacemaker]

Wonky as in buttons are completely remapped. Besides being completely different from the X360/PS3 controls (for instance, DirectInput controllers change right stick to throttle/yaw controls instead of camera control), most buttons seem to be remapped one button over. Machine gun got shifted to X instead of A, Missile to A instead of B, etc. The right stick controls are mapped to the wrong axes - left/right changes trottle, up/down yaws left/right.

It's a case, I believe, of the Namdai devs manually mapping controls to various DirectInput setups, and this controller wasn't included in the default config file.

But more than that, I have the controller emulating an X360 controller through x360ce, and ACAH recognizes that just fine, but it also recognizes the original DirectInput, so when I press, say, A to shoot my machine gun (as it's mapped to the X360), I also end up shooting a missile.

It even screws with my ability to navigate the menus. I end up pressing X for confirm and A to cancel.

All of this would be easily rectified if I could just disable DirectInput controllers for the game completely.

[gandhi_the_peacemaker]

A secondary issue, I don't know how common it is:

Sometimes during gameplay (typically during DFM), the game will freeze for just a second, then resume gameplay, but I'll be out of DFM, facing a different direction, and the enemy will always be the left of me on my radar. I'm wondering if it's a poor optimization issue with the game or if it's my hardware. Maybe it's even my wonky controls? (For the record, I managed to get gameplay manageably working by simply unbinding all controls to my DirectInput controller. Game prompts will flicker back and forth between X360 prompts and generic "Button 1, Button 2, etc." prompts, but in-game everything works just like it does on the consoles. Menus are still a hassle, though. I doubt there's any way to unbind THOSE controls.)

My computer specs:
- Windows 7 64-bit
- CPU - AMD Athlon X4 750k @ 4.0GHz
- Motherboard - MSI A88XM-E45
- GPU - Sapphire AMD Radeon R7 260X, 2GB GDDR5
- RAM - Team Zeus 8GB 1600

[mirHL]

I think the only proper solution to your problem would be to correctly remap controller bindings..
I wrote some notes here[pcgamingwiki.com] if you hare interested...
It doesn't seem something which has necessarily have to be difficult.. but it is :/

[gandhi_the_peacemaker]

Well, that's a workaround, I suppose... Shame. I wonder if deleting the default inputs file altogether will do anything... Will try that first. If all else fails, will go the remapping route. Thanks for the help.

[gandhi_the_peacemaker]

Okay. So deleting the default_input.ini file seems to fix things, with the caveat being that you can't enter the keybinding menus without crashing the game. But now the menus/game/everything works just like they should. Wonder of wonders.

Any advice on the graphical hitch issue? Or would it be better to ask that in a separate thread?

EDIT:

To clarify, the game no longer accepts the DirectInput commands from my controller. It only sees the XInput commands that my controller sends via x360ce.

[mirHL]

Woah, cool
I'm glad you could fix it.. and now that you point this out.. you are damn right
Default_input.ini seems to be using directinput names, it shouldn't regard XInput controllers..like mine

For the glitches.. did you tried updating driver?

[gandhi_the_peacemaker]

All drivers are current.

[mirHL]

Could you try without controllers?
Or could you even get to take a video?

[gandhi_the_peacemaker]

Yeah, switching to mouse/keyboard (had to replace default_input.ini file) seemed to fix the hitching problem in DFM. So again, looks like it's a control input problem.

I would just stick with mouse/keyboard, but that control scheme has so many problems of its own. Mouse vertical isn't picked up in-game, so pitch up/down isn't possible. If I switch it over to Original control scheme (with rolls instead of turns), then even the WASD keys become unrecognized.

Just... ugh. I'm glad for the free period to try this game out; I'd been wanting to get this game for a while, but now that I get a look at it, it's just... just ugh. This should have been easy peasy to port to PC. The controls should not be this much of a pain to contend with.