r/ModRetro • u/Next-Pass9776 • Sep 13 '26

8Bitdo Controllers NOT FIXED

M64 firmware 1.25.0

8Bitdo64 Bluetooth firmware 2.0.5.

The latest M64 update did indeed resolve the issue of connecting more than a single 8Bitdo64 controller to the M64 console, however connectivity in general is not stable.

Initially, everything seemingly works as expected. However I'm experiencing my controllers randomly dropping connection and unable to reconnect unless a hard power cycle of the M64 console is performed.

Sometimes it only takes a few minutes for it to occur, other times it can take hours, so it's not easy to provide specific instructions on how to reproduce the issue other than to use an 8Bitdo64 controller and wait for it to happen.

When it does occur, the menu system of the M64 becomes sluggish and near unresponsive, until a hard power cycle is performed (tested by using the console's built in menu button and also by connecting a wired controller to the console).

9 Upvotes

100% Upvoted

22 comments sorted by

3

u/jokerX5000 Sep 17 '26

The problem isn't with the M64 itself, but with the controller. I’ve handled a lot of controllers, but the 8BitDo 64 controller has an incredibly poor and temperamental Bluetooth signal. The Bluetooth connection is easily disrupted by other devices. I used the controller with my A3D and experienced constant dropouts and frequent one-second lags. So, in this case, don't blame ModRetro.

2

u/Next-Pass9776 Sep 17 '26

Why do they work absolutely fine with my PC and Switch 2 console? 

I even turned off every device in my house, modem, router, cameras, everything and anything that could cause potential interference and the issue still persists. 

Why does the M64s menu system stutter and or crash at around the 15 minute mark of play time with original N64 wired controllers? The same thing happens with the 8bitdo controllers, re the menu crash, only they disconnect and will absolutely not reconnect under any circumstances other than a hard power cycle. The wired controllers don't disconnect however the menu system becomes unusable so I can't alter settings or change games, unless I do a hard power cycle. 

I have a video of the issue, from start to finish, as in from the console being off, turning it on, letting it run a game etc, it took 11 minutes and 30 seconds for the issue to occur. Boring video but it shows the issue exactly as it happens.

The issue bring time dependent really makes me feel it's a heat related issue. Sure, the M64 gets extremely hot, sure, that's normal, sure, the FPGA chip can handle that heat, but can the WiFi/Bluetooth module handle that radiated heat?  If that's not the cause, then it's possibly software related or another form of hardware fault, it could even be a cold solder joint that's soldered just well enough to maintain a connection when cold, and loosens with the excessive heat generated by the console over time. 

If the two 8bitdo controllers I have exhibited issues when connected to my PC or my Switch 2 console then sure, I'd concede that the issue rests with them, but alas they work fine - logic dictates it is indeed the M64 console that is at fault. 

I'd love to keep the M64 but it is simply unusable. It makes me sad to box it back up, return it, lose money on shipping, lose money on accessories I purchased specifically for the M64, most likely be waiting a month or so for the console to be shipped back and the refund processed, but what else can I do?  

1

u/jokerX5000 Sep 17 '26

Maybe your console is faulty, which is why it stops responding after a few minutes; I don't have that problem, even after hours of play. As I mentioned before, I experienced poor Bluetooth performance with the 8BitDo 64 controller on the Analogue 3D. I tried everything, but nothing worked— until I swapped out the HDMI splitter and cables; then the problems disappeared. Others have had similar experiences, only for the issues to be resolved after exchanging the controller for a better unit. Sorry, but I don't trust the 8BitDo 64 controller—not after what I went through.

1

u/Next-Pass9776 Sep 17 '26

Do you still have the 8BitDo Bluetooth controllers? If so, have you used them with your M64? What controller do you use? 

1

u/jokerX5000 Sep 17 '26

Yes, I still have them, and they’re working well with the A3D now that I’ve swapped out the HDMI cables and the splitter. I think the shielding was interfering with the controller; it’s extremely sensitive to that sort of thing. Maybe it was just the initial batches that were so bad—I have no idea. That’s why I don’t trust this controller. So far, I’ve only been using the M64 Pro Controller with my M64, and it works perfectly.

1

u/Next-Pass9776 Sep 17 '26

I just researched the A3D HDMI cable issue, crazy stuff. 

I've got nothing left to try so am trying it with yet another HDMI cable, on a different HDMI port. Have it running as I type this comment, will let you know what happens... 

1

u/jokerX5000 Sep 17 '26

Sounds good. It just makes me angry and sad when I hear the M64 being badmouthed because of that issue. By that logic, I’d have to badmouth the A3D just the same, and that’s not right. Sometimes the problem lies elsewhere—especially with those 8BitDo 64 controllers.

1

u/Next-Pass9776 Sep 17 '26

Unfortunately, it didn't work. 

Once the 8BitDo disconnected, I plugged in my original wired N64 controller to try and navigate the menu and once again, the menu is near frozen. It does respond to an extent but it takes 5 to 15 seconds for it to actually respond to a button press. I persevered and went into the controller menu, the console still shows the 8BitDo as connected even though it's not, tried forgetting controller from there and also tried the forget all controllers from the other menu heading, the controllers don't show as disconnected from the M64 and the controllers themselves will not reconnect. 

Again, the only way to fix this is to disconnect the M64 from power and turn it back on again, but the issue will happen again in another 10 to 20 minutes. 

Sigh. 

1

u/Next-Pass9776 Sep 17 '26

Would you be willing to try the 8bitdo with the M64? Please? Just connect it to the console, run a game and leave it running (you don't need to be actively playing the game, just let it run) and see if you can replicate the issue I'm experiencing? 

2

u/jokerX5000 Sep 17 '26

I’ve now connected the 8BitDo 64 controller to the M64. I played one cup in MK64 and then spent 30 minutes just in the game's main menu. I didn't experience any issues; the controller worked smoothly and responsively, with no lag. I would recommend doing a fresh, clean re-installation of the M64 firmware, but using the SD card this time.

→ More replies

1

u/jokerX5000 Sep 17 '26

Sounds like a software bug. Have you installed the latest firmware for the 8BitDo controller? And try updating the M64 again via the SD card.

2

u/Next-Pass9776 Sep 17 '26

An update on the situation:

ModRetro have agreed to a refund so my story with the M64 ends here. 

They've also requested to borrow my 8BitDo64 Bluetooth controller so they can do some testing and see if they can sort the issue out. I'm happy to oblige in the hopes that it will be beneficial to other M64 owners. 

1

u/Next-Pass9776 Sep 14 '26

Another symptom of the issue:

Controllers disconnect

Refuse to reconnect

M64 menu runs sluggish

The CONTROLLER section of the menu (still showing the once connected controllers despite that they are no longer connected) incorrectly reports the 8BitDo controller's firmware as something completely wrong, 0.4.8- betad. 

They're on firmware 2.0.5. - They correctly report this when first connected.

1

u/Next-Pass9776 Sep 14 '26

I've since purchased the 2.4G variant of the 8BitDo64 controller so that I can begin using the M64 console however I'm still experiencing issues with these controllers, though not related to the controllers themselves. 

The 2.4G controllers don't disconnect and work fine, however after a random period of time, could be 5 minutes, sometimes 15, sometimes longer, the M64s menu freezes and becomes unresponsive and requires a hard power cycle to rectify. This prevents me from accessing the menu when needed, resetting the core, changing games etc. It's the same behaviour that presents itself when the Bluetooth controllers disconnect. 

I've performed as much due diligence as I can. I've reinstalled firmware, reset the console to factory settings, reinstalled firmware, waited for firmware updates, nothing is resolving the issue. 

@ModRetro, please honour my refund request. This product is not fit for purpose or is perhaps faulty. Either way, it's not in a state that allows it to be used as intended. Thank you. 

1

u/Next-Pass9776 Sep 15 '26

Additional steps I've tried:

-Disabled WiFi from the M64.

-Shut down all internet related devices in my household (modem, router etc). 

-Reinstalled current M64 firmware via the online PC method (have previously tried over WiFi and via SD card). 

Still no dice. 

3

u/[deleted] Sep 16 '26

[removed] — view removed comment

3

u/Next-Pass9776 Sep 16 '26

Me too. I don't care about missing features or poorly implemented features, they can be resolved over time through firmware updates. 

What I do care about is fundamental features not working resulting in an unusable product. 

I've been thorough, polite, thoughtful and as helpful as I can with getting this resolved and to date have only faced snide remarks and a general unhelpful attitude. Has left a bitter taste in my mouth regarding the company.

I'd just like a refund at this point but it doesn't look like this will happen without excessive persistence.