Closed GoogleCodeExporter closed 9 years ago
Please be more precise when filing issues. I see the submission for 046d:c219
(is that the Logitech Chillstream?)
Is the problem with your X/Y axes (i assume the left analog stick)? Because in
your mapping you have mapped axis 1 to both the X and Y axis, which will cause
problems. This can happen during mapping, be sure to take a look at the text on
the right side while mapping your gamepad, as you can see which axis gets
mapped.
If this is not your problem, please reply with more detail. Thank you!
Original comment by wila...@gmail.com
on 22 Aug 2010 at 2:37
I will have to look more closely, however the 1234 buttons were not mapping
correctly to the ABCD buttons either.
It is a Logitech wireless rumblepad.
Original comment by indoler...@gmail.com
on 22 Aug 2010 at 5:56
Since the button highlights aren't showing up correctly for you yet, please
re-run the mapping wizard and press the buttons in the following order (please
ignore the position of the button indicator). Make sure to press them carefully
so you don't mistakenly press another input.
Left trigger
Left bumper
Right bumper
Right trigger
A
B
X
Y
Start
Back
System/Dashboard
Left Stick (press)
Right Stick (press)
Press up on the left analog stick
Press left on the left analog stick
Press up on the digital pad
Press left on the digital pad
PRess up on the right analog
Press left on the right analog
At this point you should see the finishing screen. Please submit this mapping,
and click the Finish button to close the wizard. Now you should be looking at
the main Pad Tie controller view- if you press the buttons on your gamepad,
they will light up on that view. Ensure they are all mapped properly. If you
still have the issue, please drop a note here.
Original comment by wila...@gmail.com
on 22 Aug 2010 at 6:34
Is it working? If not I will close the issue.
Original comment by wila...@gmail.com
on 26 Aug 2010 at 1:56
Closing the issue. If this issue reappears, please open a new bug.
Original comment by wila...@gmail.com
on 28 Aug 2010 at 3:26
This is also likely a manifestation of Pad Tie's inability to handle high DPI
configurations properly.
See http://code.google.com/p/padtie/issues/detail?id=32
Original comment by wila...@gmail.com
on 28 Aug 2010 at 10:14
Original issue reported on code.google.com by
indoler...@gmail.com
on 19 Aug 2010 at 5:02