Author Topic: Directinput button numbers don't correspond in-game  (Read 249 times)

0 Members and 1 Guest are viewing this topic.

Offline bokan

  • Bondsman
  • *
  • Posts: 14
  • Karma: 0
Directinput button numbers don't correspond in-game
« on: July 13, 2010, 07:03:34 AM »
So, I am close to completing my odyssey in setting up x52 + pedals with ppjoy on 64 bit vista (at which point I will realize that I still can't aim, but I digress).  The thing is, the data for directinput is not the same as what happens in-game.  I thought perhaps it was just offset by 1, but it appears quite random sometimes.  Does anyone know what the relationship is?  Thanks.

I will post all of my configuration stuff for people who want to use this setup if I get it working!

Offline bokan

  • Bondsman
  • *
  • Posts: 14
  • Karma: 0
Re: Directinput button numbers don't correspond in-game
« Reply #1 on: July 14, 2010, 03:32:01 AM »
<mod, feel free to delete>

What goes in the actionmapper should be what shows up in directinput + 1, for me at least.  Hope this helps someone!

Offline (TLL)CapperDeluxe

  • MWLL Developer
  • Living Legend
  • *
  • Posts: 2084
  • Karma: 117
  • Life is cheap, mechs are expensive.
Re: Directinput button numbers don't correspond in-game
« Reply #2 on: July 14, 2010, 04:31:21 AM »
what you see from that joystick.exe program is button minus 1. What you get in the actionmapper and in game should be like what you see when you test in the windows game controllers configure window thingy
Play my free open source web game MiniMek - Urbie Defense!  Its "mega fun" but with mini meks!