[GH-ISSUE #531] Directinput #54

New issue

Closed

opened 2026-03-03 13:45:18 +03:00 by kerem · 3 comments

kerem commented

2026-03-03 13:45:18 +03:00

Owner

Originally created by @Mayo77 on GitHub (Jul 31, 2025).
Original GitHub issue: https://github.com/gopher64/gopher64/issues/531

First off i wanted to say thank you for Gopher 64 what a fantastic N64 emulator by far the best i have found anywhere. You guys can play basically ALL games. I haven't found one it can't play yet! Top N64 emulator by far.

The direct input control settings do no seem to work properly on a N64 control converter for PC windows 10.

I now own 2 different control converters, neither seem to be hold their "mapping" properly it seems.

Newest controller adapter was a cheap china version:
https://www.aliexpress.com/item/1005005917015197.html

First off this controller being recognized on windows as "game cube controller" which is already an issue considering it says it's a N64 controller adpater.... Regardless it does work with my controller somewhat..but, the left and right buttons were not working at all.. also, the Up and down on the joystick was inverted (down was up and up was down). 99% sure this was the Adapters bios issue, not Gopher64 but, I will add, I did re-map the buttons manually (using direct input) in gopher and for some reason it still did not work in gopher. Everything else worked the Dpad , C buttons, A & B, Z worked, start worked. Just the left and right did not work and the up and down on the joystick were opposite, no matter how i mapped it. I even tried mapping it upside down to make it work .. Like when it asked for up on the joystick I pressed down and when it asked for down I pressed up and it still was working opposite. like i said it could be the adapter itself i guess but isn't direct input supposed to be able to hold a remap regardless, maybe im wrong here.

Second Adapter seem below:
https://www.mayflash.com/product/PC043.html

It seems to work sometimes, yet it sometimes when i reboot the computer it doesn't again... Again it maybe an issue with this adapter but i also need to use direct input otherwise it automaps the buttons all wrong. Just seems to turbo pick all the buttons itself if i don't use direct input.

Even after I have a working profile, it sometimes works and sometimes it seems to "randomly" have a key issue. Most the time its either the start button or the "joystick up". Sometime the start button seems to just turn on and off randomly or the "joystick up" will sometime activate the start button. Really weird because I can other time play games for hours without ANY issues at all (currently working 100%) then i restart my computer and next time i open gopher64 I have these issues again and, I have to remap all my keys to get it working. Its weird because once i get it fixed it says fixed, until i reboot the computer it seems.

Not sure if this is gopher saved settings with direct input... or again if it's just the adapter but trying to give as much information as possible so someone can figure this out. Its really weird like i said as it works (after remapping using direct input) for hours upon hours until I reboot. Then "sometimes" I have issues, yet sometimes it works fine.

Windows 10 64 bit/ Gopher 64 newest using the second adapter. I save all my mapped profiles and just use those.

Originally created by @Mayo77 on GitHub (Jul 31, 2025). Original GitHub issue: https://github.com/gopher64/gopher64/issues/531 First off i wanted to say thank you for Gopher 64 what a fantastic N64 emulator by far the best i have found anywhere. You guys can play basically ALL games. I haven't found one it can't play yet! Top N64 emulator by far. The direct input control settings do no seem to work properly on a N64 control converter for PC windows 10. I now own 2 different control converters, neither seem to be hold their "mapping" properly it seems. Newest controller adapter was a cheap china version: https://www.aliexpress.com/item/1005005917015197.html First off this controller being recognized on windows as "game cube controller" which is already an issue considering it says it's a N64 controller adpater.... Regardless it does work with my controller somewhat..but, the left and right buttons were not working at all.. also, the Up and down on the joystick was inverted (down was up and up was down). 99% sure this was the Adapters bios issue, not Gopher64 but, I will add, I did re-map the buttons manually (using direct input) in gopher and for some reason it still did not work in gopher. Everything else worked the Dpad , C buttons, A & B, Z worked, start worked. Just the left and right did not work and the up and down on the joystick were opposite, no matter how i mapped it. I even tried mapping it upside down to make it work .. Like when it asked for up on the joystick I pressed down and when it asked for down I pressed up and it still was working opposite. like i said it could be the adapter itself i guess but isn't direct input supposed to be able to hold a remap regardless, maybe im wrong here. Second Adapter seem below: https://www.mayflash.com/product/PC043.html It seems to work sometimes, yet it sometimes when i reboot the computer it doesn't again... Again it maybe an issue with this adapter but i also need to use direct input otherwise it automaps the buttons all wrong. Just seems to turbo pick all the buttons itself if i don't use direct input. Even after I have a working profile, it sometimes works and sometimes it seems to "randomly" have a key issue. Most the time its either the start button or the "joystick up". Sometime the start button seems to just turn on and off randomly or the "joystick up" will sometime activate the start button. Really weird because I can other time play games for hours without ANY issues at all (currently working 100%) then i restart my computer and next time i open gopher64 I have these issues again and, I have to remap all my keys to get it working. Its weird because once i get it fixed it says fixed, until i reboot the computer it seems. Not sure if this is gopher saved settings with direct input... or again if it's just the adapter but trying to give as much information as possible so someone can figure this out. Its really weird like i said as it works (after remapping using direct input) for hours upon hours until I reboot. Then "sometimes" I have issues, yet sometimes it works fine. Windows 10 64 bit/ Gopher 64 newest using the second adapter. I save all my mapped profiles and just use those.

kerem closed this issue

2026-03-03 13:45:19 +03:00

kerem commented

2026-03-03 13:45:19 +03:00

Author

Owner

@loganmc10 commented on GitHub (Jul 31, 2025):

It's hard for me to say. I also have an N64 adapter (this one: https://www.raphnet-tech.com/products/dual_n64_to_usb_adapter/index.php) that needs Direct Input, but I've never had a problem with it.

It makes sense that both require Direct Input. The "regular mode" with automapping is basically for Xbox/PlayStation style controllers, so different styles like GameCube or N64 often require Direct Input with a custom profile.

@loganmc10 commented on GitHub (Jul 31, 2025): It's hard for me to say. I also have an N64 adapter (this one: https://www.raphnet-tech.com/products/dual_n64_to_usb_adapter/index.php) that needs Direct Input, but I've never had a problem with it. It makes sense that both require Direct Input. The "regular mode" with automapping is basically for Xbox/PlayStation style controllers, so different styles like GameCube or N64 often require Direct Input with a custom profile.

kerem commented

2026-03-03 13:45:19 +03:00

Author

Owner

@Mayo77 commented on GitHub (Jul 31, 2025):

It's hard for me to say. I also have an N64 adapter (this one: https://www.raphnet-tech.com/products/dual_n64_to_usb_adapter/index.php) that needs Direct Input, but I've never had a problem with it.

It makes sense that both require Direct Input. The "regular mode" with automapping is basically for Xbox/PlayStation style controllers, so different styles like GameCube or N64 often require Direct Input with a custom profile.

Yup depending on if i can get this fixed i may just have to buy a third USB adapter like that one.

I just got refunded for the cheap china one, because it shouldn't be installing on my windows as a "Game cube controller" since it was avertisted as a N64 controller adapter, but that is what it does. I'm assuming this maybe due to the cheap controllers I am using were not QC'd properly... but, it's just odd how I can get the second one working (after re-mapping) for hours and hours until a reboot. Then it tends to just randomly "break" again. Just confuses me. Make me think its a saving config issue with direct input and gopher or a faulty controller adapter (which is possible). Just like i said it weird if its a faulty controller adapter why does it work flawlessly for hours upon hours if I remap it, then only break upon reboot.

@Mayo77 commented on GitHub (Jul 31, 2025): > It's hard for me to say. I also have an N64 adapter (this one: https://www.raphnet-tech.com/products/dual_n64_to_usb_adapter/index.php) that needs Direct Input, but I've never had a problem with it. > > It makes sense that both require Direct Input. The "regular mode" with automapping is basically for Xbox/PlayStation style controllers, so different styles like GameCube or N64 often require Direct Input with a custom profile. Yup depending on if i can get this fixed i may just have to buy a third USB adapter like that one. I just got refunded for the cheap china one, because it shouldn't be installing on my windows as a "Game cube controller" since it was avertisted as a N64 controller adapter, but that is what it does. I'm assuming this maybe due to the cheap controllers I am using were not QC'd properly... but, it's just odd how I can get the second one working (after re-mapping) for hours and hours until a reboot. Then it tends to just randomly "break" again. Just confuses me. Make me think its a saving config issue with direct input and gopher or a faulty controller adapter (which is possible). Just like i said it weird if its a faulty controller adapter why does it work flawlessly for hours upon hours if I remap it, then only break upon reboot.

kerem commented

2026-03-03 13:45:19 +03:00

Author

Owner

@Mayo77 commented on GitHub (Sep 7, 2025):

I just wanted to update you on this issue. I found out i not only had a faulty N64 controller at the plug in end. It seemed to be loose connection at the plug in end. Also the controller adapters mentioned above BOTH do not work properly. I Since have gotten a new original OEM Nintendo n64 controller and one of these controller adapters (linked below) which actually worked. Finally I found a controller adpater that works properly. So what im trying to say it wasn't gopher it was my controller + my controller adapters all along.

Just FYI this Controller adapter worked, I grabbed it on amazon. Cost alot more but at least it worked.

https://www.mayflash.com/product/n64_controller_adapter_mf103.html

@Mayo77 commented on GitHub (Sep 7, 2025): I just wanted to update you on this issue. I found out i not only had a faulty N64 controller at the plug in end. It seemed to be loose connection at the plug in end. Also the controller adapters mentioned above BOTH do not work properly. I Since have gotten a new original OEM Nintendo n64 controller and one of these controller adapters (linked below) which actually worked. Finally I found a controller adpater that works properly. So what im trying to say it wasn't gopher it was my controller + my controller adapters all along. Just FYI this Controller adapter worked, I grabbed it on amazon. Cost alot more but at least it worked. https://www.mayflash.com/product/n64_controller_adapter_mf103.html

kerem referenced this issue

2026-03-03 13:46:16 +03:00

[PR #54] [CLOSED] Use macos-13 #170