search

Cleeko / nintendon-t

Automatically exported from code.google.com/p/nintendon-t
0 stars 0 forks source link

Logitech Cordless Rumblepad 2 #6

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
So after one of the more recent updates, the controller responds in game which 
is great. The only issue is that for some reason while playing in game, the 
game thinks that the D-pad is the A button. Any direction you push is like 
pushing the A button. The buttons mapped to A, B, X and Y do not work at all. 
L, R and Start works, as far as I can tell.

What version of the product are you using?
r28 or r29

Support site:
http://www.logitech.com/en-us/support/287?osid=14&bit=64

Original issue reported on code.google.com by BravaCentauri on 7 May 2014 at 7:29

Attachments:

GoogleCodeExporter commented 8 years ago 
No one can help if you dont give them the raw data from HidTest.
My guess would be that the 8 bit dosent change change with those button presses 
but is used to indicate no dpad direction is pressed.

Original comment by Howard_M...@yahoo.com on 8 May 2014 at 4:31

GoogleCodeExporter commented 8 years ago 
What information do they need? I'm going to check it in the next couple of 
days.

Original comment by BravaCentauri on 10 May 2014 at 6:11

GoogleCodeExporter commented 8 years ago 
HIDVersion:40001
DeviceID:0
HIDVers:3 IntClass:0 SubIntClass:0
bEndpointAddress:81
uMaxPacketSize: 8

when nothing is being pressed, this is the default value:
01 80 7F 83 7D 08 00 00

3 and 4 never stay the original values, I guess because of the dead zone on the 
stick, but that works in game

Original comment by BravaCentauri on 12 May 2014 at 7:58

GoogleCodeExporter commented 8 years ago 
Just tested it with HIDTest 6, and pressing any direction on the d-pad is like 
pressing A, B, X, Y and the direction you pushed, rather than only the 
direction. The buttons mapped to A, B, X and Y do nothing.

Original comment by BravaCentauri on 12 May 2014 at 8:23

GoogleCodeExporter commented 8 years ago 
Try this file in HIDTest

Original comment by Howard_M...@yahoo.com on 14 May 2014 at 6:29

Attachments:

GoogleCodeExporter commented 8 years ago 
it works perfectly! that's awesome. thanks!

Original comment by BravaCentauri on 14 May 2014 at 7:28

GoogleCodeExporter commented 8 years ago 
I hate to be a stickler, but is it possible to increase the dead zone or lower 
the sensitivity of the analog stick? I can see this being a problem in some 
games as this controller (and I'm sure others) are too sensitive to perform 
certain moves and what not.

Original comment by BravaCentauri on 14 May 2014 at 8:23

GoogleCodeExporter commented 8 years ago 
Can you describe in more ditail what the problem is?

Increasing the deadzone would mean that more of the movement of the stick would 
do nothing because it is in the deadzone. Requireing that the movement of the 
stick that is outside the deadzone become more sensitive because we now have a 
smaller amount of the total stick movement that has to register as movement 
from the center to the outside. My thoughts had been to decrease the deadzone 
to give more precise control. This would decreasing the sensitivity.

In HIDTest what does it display fot the full left, right, up and down values on 
each stick?

Original comment by Howard_M...@yahoo.com on 14 May 2014 at 12:21

GoogleCodeExporter commented 8 years ago 
In playing games like Wario Land or Mario Sunshine, it becomes really hard to 
control the characters when you need precise controls. For example, if you were 
trying to walk over a thin bridge, it becomes very hard to do so without 
falling off, or in Wario, the spin attack never works like it does on the 
Gamecube controller.

I guess on this controller, the analog sticks are really sensitive. Are there 
any plans on making a controller config utility with Nintendont? Like where you 
press a button when it asks you to and it saves? Just curious.

Original comment by BravaCentauri on 14 May 2014 at 2:48

GoogleCodeExporter commented 8 years ago 
This is just some test code.
let me know what you think about the sticks in this version.

Original comment by Howard_M...@yahoo.com on 14 May 2014 at 11:08

GoogleCodeExporter commented 8 years ago 
I tried it, and it works a little bit better, it's still too sensitive though.

Original comment by BravaCentauri on 15 May 2014 at 9:02

GoogleCodeExporter commented 8 years ago 
Someone just posted this controller.ini for the same controler. Theirs supports 
analog triggers. Which is correct?

http://gbatemp.net/threads/nintendont-controller-configurations.355035/page-6#po
st-4998053

Original comment by Howard_M...@yahoo.com on 16 May 2014 at 10:11

GoogleCodeExporter commented 8 years ago 
As far as I could tell, my controller doesn't not have analog triggers. When I 
push the buttons in, it changes one value and not more than one.

Original comment by BravaCentauri on 17 May 2014 at 1:40

GoogleCodeExporter commented 8 years ago 
Try this one for controller sensitivity.

Original comment by Howard_M...@yahoo.com on 19 May 2014 at 10:44

Attachments:

GoogleCodeExporter commented 8 years ago 
Tried it out, and the d-pad and stick doesn't do anything at all. I haven't 
changed the controller.ini, and I'm not sure how to set up the new parameters 
for the new version.

Original comment by BravaCentauri on 20 May 2014 at 3:39

GoogleCodeExporter commented 8 years ago 
Nothing should have affected the dpad.
What are the min and max values on each stick axis?

Original comment by Howard_M...@yahoo.com on 20 May 2014 at 5:37

GoogleCodeExporter commented 8 years ago 
stick x default 80 - left 00 - right ff
stick y default 7f - up 00 - down ff

stickc x default 7f - left 00 - right ff
stickc y default 80 - up 00 - down ff

Original comment by BravaCentauri on 20 May 2014 at 8:52

GoogleCodeExporter commented 8 years ago 
I think you're right about the d-pad, the game I tested it on doesn't use it.

Original comment by BravaCentauri on 20 May 2014 at 10:05

GoogleCodeExporter commented 8 years ago 
Try the released version the defaults in it should be perfect with your 
origonal file. No new setup needed

Original comment by Howard_M...@yahoo.com on 20 May 2014 at 11:04

GoogleCodeExporter commented 8 years ago 
Tried out r55, and with the same old controller.ini the sticks do nothing at 
all.

Original comment by BravaCentauri on 22 May 2014 at 3:54

GoogleCodeExporter commented 8 years ago 
It should be working.
Try r52 to to confirm nothing eles got messed up.
If r52 still works go back to r55.
Adding ,0,100 to the end of each of your Stick commands will make it work 
exactly like the test code from message 10 did that you thought was a little 
better.

Original comment by Howard_M...@yahoo.com on 22 May 2014 at 4:44

GoogleCodeExporter commented 8 years ago 
When you were trying r55 did you have any gamecube controllers plugged in?

Original comment by Howard_M...@yahoo.com on 22 May 2014 at 4:55

GoogleCodeExporter commented 8 years ago 
I don't know how to compile older revisions, but I'll try adding ,0,100 to 55 
and see how that turns out. I didn't have any GC controllers plugged in while 
testing 55.

Original comment by BravaCentauri on 22 May 2014 at 5:02

GoogleCodeExporter commented 8 years ago 
you can download r52 directly from the svn here
https://nintendon-t.googlecode.com/svn-history/r52/trunk/loader/loader.dol
You can get any other version just by changing the version.

Original comment by Howard_M...@yahoo.com on 22 May 2014 at 5:07

GoogleCodeExporter commented 8 years ago 
Alright so adding ,0,100 to the stick values works in r55. I personally prefer 
,0,80 though

Original comment by BravaCentauri on 22 May 2014 at 5:31

GoogleCodeExporter commented 8 years ago 
,0,80 is the default. it should have worked that way without you changing 
anything.
If ,0,80 works for you in r55 try removing it it should work the same way.

Original comment by Howard_M...@yahoo.com on 23 May 2014 at 5:37

GoogleCodeExporter commented 8 years ago 
Yeah the analog stick doesn't work and you can't move anywhere.

Original comment by BravaCentauri on 23 May 2014 at 4:48

GoogleCodeExporter commented 8 years ago 
Please test with this version. The only differance between this and r55 is it 
has some debug info enabled.
Run it booth with the ,0,100 and without.
send the ndebug.log files it creates and booth of the actual controller.ini 
files.

Original comment by Howard_M...@yahoo.com on 23 May 2014 at 10:40

Attachments:

GoogleCodeExporter commented 8 years ago 
Haven't had a chance to check it yet, I'll try to do it later on today

Original comment by BravaCentauri on 24 May 2014 at 4:20

GoogleCodeExporter commented 8 years ago 
Here you go. With ini1 it worked, with ini2 it didn't work at all.

Original comment by BravaCentauri on 24 May 2014 at 5:57

Attachments:

GoogleCodeExporter commented 8 years ago 
The problem was a result of trying to combine the two contolller.ini files.
r56 or newer should fix it.

Original comment by Howard_M...@yahoo.com on 25 May 2014 at 7:05

GoogleCodeExporter commented 8 years ago 
Ah, well I wasn't sure if that would work or not. How many configurations can 
be in the ini file?

Original comment by BravaCentauri on 27 May 2014 at 6:33

GoogleCodeExporter commented 8 years ago 
Only 1 configuration will work per file.

Original comment by Howard_M...@yahoo.com on 28 May 2014 at 3:16

GoogleCodeExporter commented 8 years ago

Original comment by Howard_M...@yahoo.com on 13 Nov 2014 at 4:28