amanuelg3 / padtie

Automatically exported from code.google.com/p/padtie
0 stars 0 forks source link

Buttons mapping strangely #35

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Using Logitech Wireless (see attached image for key mapping reference)

When I press button "3" the onscreen image shows a red dot, however the mapping 
states that the logitech button 3 is mapped to the Xbox button Y...

In game, the buttons certainly feel off, in DiRT, the 2 key = reverse!

Original issue reported on code.google.com by indoler...@gmail.com on 1 Sep 2010 at 7:45

Attachments:

GoogleCodeExporter commented 9 years ago
The mapping we ship for Dirt II *does* have reverse for the 2 button (it would 
be A on the virtual controller). 

I believe you are experiencing the DPI issues I described in your previous bug 
reports. The version of Pad Tie you are using (and currently all available 
versions) do not work correctly when you have selected High DPI settings. 
Windows sometimes chooses these settings for you. Please right click your 
desktop, click Display Resolution, then click 'Display' in the address bar, now 
pick the '100%' option, click Apply, log out and log back in when prompted, and 
check Pad Tie again.

You should note that the button overlays in the controller view now map 
perfectly to the buttons they should. Likewise with the mapping wizard, and 
anywhere else the 360 controller image is shown. 

This problem is thoroughly fixed in the next development version, which I will 
be releasing very shortly (along with a ton of awesome new features).

Please let me know if changing your DPI doesn't fix the problem, if this is the 
case I will set the status back from Duplicate, which I am assigning now. If it 
*is* the DPI, you can still use the higher DPI settings you had before, but the 
buttons will just be off. It may be easier for you to change the mappings from 
the Buttons or Actions tab instead of using the context menus on the controller 
view.

Sorry again for any inconvenience and for my negligence of DPI testing.

Original comment by wila...@gmail.com on 2 Sep 2010 at 4:30