BlueRetro: SNES Multitap controller 4 doesn't work on NBA Jam since v1.8.2

BlueRetro firmware version

v1.8.2

BlueRetro firmware specification

HW1

BlueRetro firmware variant

Universal

BlueRetro hardware type

External adapter with detachable cord

Manufacturer

I did

System used

Nintendo SFC SNES

Bluetooth controller brand & name

2xPS3 and 2xN30

What is problem? (only list ONE problem per report)

When multitap is enabled (slot 2), NBA Jam allows you to play up to four players. With v1.8.1, it works great, but since v1.8.2, the first three controllers work, but attempting to use the fourth controller causes the game to detect an invalid device. It shows a screen that says:

PROBLEM

A DEVICE NOT SUPPORTED BY
THIS PROGAM HAS BEEN
CONNECTED.

PLEASE USE THE STANDARD
CONTROLLERS ONLY.

More details about NBA Jam: when multitap is enabled, the title screen only shows two options: “Start Game” and “Options” (if you see more options, multitap is not detected). Selecting “Options”, and moving to the bottom where you can configure controller buttons, pressing start on the 2nd and 3rd controllers activates their configuration, but pressing start on the fourth controller does not. However if you mash buttons on controller 4, the game detects an invalid controller and displays the message above.

I suspect that this change may have broken multitap in NBA Jam: https://github.com/darthcloud/BlueRetro/commit/0eb8e2551221a5a4362c313f087047bae9b1d45a

What did you expect to happen?

All four controllers work in multitap mode in NBA Jam.

Attach files like logs or Bluetooth traces here

No response

About this issue

  • Original URL
  • State: open
  • Created a year ago
  • Comments: 17 (14 by maintainers)

Most upvoted comments

@amaiorano The reason I think the problem might not be in this part of code is that I’ve not updated to 1.8.3, I’m using a custom firmware, a tree branch of 1.7.3, with this particular changes you mention. I’m going to update to 1.8.3 and see if I have the same problem you are having. If that’s the case, some other games could be broken too, and it’s something I will also look into.

Interesting. In my case, I made a custom build of 1.8.3 where I reverted your patch, and it works perfectly in NBA Jam. I will try making a custom build of 1.7.3 + your patch (same as you), and see if that works.

If this message appears when you pair or press buttons (and not at boot, or by itself when you reach a part, so multitap code is working fine), then I suspect is a problem not related to timing, but to mapping (inside firmware). When I pair my SN30 controller, I have to use “START + A, macOS” mode to make it work, other modes are not well mapped or supported (@darthcloud we need your help here), and they exhibit strange behaviour (snes controller data is made of two bytes, the last 4 bits are signature, anything that is written from bit 13 to bit 16 can mess up with multitap games, and make them think you’re connecting a mouse, or a superscope, if mapping is faulty, then we know where to look). Try this with your N30 and let me know if the problem is fixed.

That’s very interesting about use the macOS mode. I will try that. In my case, they are all mapped in Windows mode using START + UP (see https://download.8bitdo.com/Manual/Mod-Kit/Mod-Kit-for-NES-Original&Classic-controller.pdf). @darthcloud added support for the N30 as part of 1.8.2 assuming the Windows mode, I believe.

In my case, all four controllers are paired even before I launch the game from the clone Super Everdrive menu. NBA Jam recognizes a multitap (showing only 2 options), and whether I start a new game or go into options, pressing start on the player 4 controller, which is a PS3 controller, doesn’t do anything. But then if I start pressing other buttons (I didn’t carefully check which ones), suddenly the game shows that error screen. So it’s possible that it’s related to mapping, as you suggest. I can try the macOS mode for my two N30 controllers. I also have 2 other PS3 controllers that I could test with, so that would make 4x PS3 controllers, and this could also help understand the bug.

So here’s what I’ll do:

  1. Try 1.7.3 + your patch (NES30’s paired in Windows mode)
  2. On 1.8.3: try NES30’s paired in MacOS mode
  3. On 1.8.3: try 4x PS3 controllers on 1.8.3