|
#1
|
|||
|
|||
![]()
I tried searching the forums but couldn't find anything about this...
I have an n64 usb adapter for my computer and am using Jabo's DirectInput7 1.6 for the emulator. My controller works fine, but when I map the buttons for the emulator, the c-down button just doesn't register at all. The button works fine when I plug it into an original n64 and even tried another controller but still no luck. Every other button maps fine and works except c-down. Can anyone help? |
#2
|
||||
|
||||
![]()
install the adapters driver.
__________________
CPU:Intel Xeon x5690 @ 4.2Ghz, Mainboard:Asus Rampage III Extreme, Memory:48GB Corsair Vengeance LP 1600
Video:EVGA Geforce GTX 1080 Founders Edition, NVidia Geforce GTX 1060 Founders Edition Monitor:ROG PG279Q, BenQ BL2211, Sound:Creative XFI Titanium Fatal1ty Pro SDD:Crucial MX300 275, Crucial MX300 525, Crucial MX300 1000 HDD:500GB Spinpoint F3, 1TB WD Black, 2TB WD Red, 1TB WD Black Case:NZXT Phantom 820, PSU:Seasonic X-850, OS:Windows 7 SP1 |
#3
|
|||
|
|||
![]()
I just had this same exact problem...
using a authentic n64 controller with a generic usb adapter, for which there are no drivers. the controller seemed to work fine in XP but i installed windows 7 a few days ago and reinstalled p64, and i had the same problem as you. but, I fixed it by doing the following (well, not so much a fix but a work-around): - open up P64 - Go to Options > Settings - for Input (controller) plugin, instead of Jabo's, select N-Rage's Direct-Input8 V2 1.80a and click OK - Go back to Options > then Configure Controller Plugin - Stay under the Controller 1 tab, but switch to the Devices tab - in the right panel, select your gamepad in the dropdown under Gamepad Devices. - then go back to the controls tab, and you should be able to map all your buttons - at least, mine worked. you may want to calibrate the controller in windows before doing this. For windows 7: Start > Devices and Printers > right click the gamepad icon > Game Controller Settings > select your gamepad from the list and click properties. hope this all wasn't terribly obvious information and i hope it helps. good luck |
#4
|
|||
|
|||
![]() Quote:
|
#5
|
||||
|
||||
![]()
Can someone tell me what C-Down registers as? Which button? POV? Slider? I don't understand entirely why this should not be detected...
__________________
Project64 Developer HP Laptop, Intel P7540 with GMA4500, Windows 7 |
#6
|
||||
|
||||
![]()
It sounds like they couldn't get it to register at all, though I imagine it's some form of driver fault mainly.
__________________
http://theoatmeal.com/comics/cat_vs_internet |
#7
|
||||
|
||||
![]()
Yea just this seems like a pretty strange bug I was hoping someone like in3rtia could throw a hint my way about which axis was having the problem...
__________________
Project64 Developer HP Laptop, Intel P7540 with GMA4500, Windows 7 |
#8
|
||||
|
||||
![]()
I took a quick look after being poked by RadeonUser and it seems there is an awful hack for a workaround with sliders that default to the negative axis, always wanted to fix that, I'll give it some thought and hopefully have something soon please give it a try when it's up there
__________________
Project64 Developer HP Laptop, Intel P7540 with GMA4500, Windows 7 |
#9
|
||||
|
||||
![]()
Much of the sliders I can't test I guess since I have only a keyboard, wasn't sure if there was some correlation to the issue with the C-Down map though when I see it I'll test what I can.
![]()
__________________
http://theoatmeal.com/comics/cat_vs_internet |
#10
|
||||
|
||||
![]()
yea altho reading this thread again he mentioned he's using 1.6, which means I really either need him to tell me which axis was having the problem or try 1.7 because I've changed it in 1.7
back to the start I'm afraid :P going to move this thread to the public forum.... people need to stop posting in 1.7 if they aren't using it!
__________________
Project64 Developer HP Laptop, Intel P7540 with GMA4500, Windows 7 |