[Why would Big Box (but not LaunchBox) block Yuzu gyro controls?]

Title says it all. When I launch Yuzu on its own, my gyro controls work as expected. When I launch a Yuzu game through LaunchBox, gyro controls also work as expected. When I launch a Yuzu game through Big Box, however, gyro controls don't work at all. Additionally, there's some serious stick drift that happens. Why would these issues happen in Big Box but not in LaunchBox? I've gone through Big Box settings trying to find something that could be conflicting, but I haven't figured anything out. If anyone has any insight, it would be appreciated!

[Controller automation 'breaks' for some emulators?]

Hi there. I have a Big Box install going. I've recently revamped everything to eliminate Steam, so controllers are connected to Windows (via Bluetooth) and then that's it: it should go directly to BB or the emulator, depending on what's active.

For Retroarch cores and Dolphin, this works great. I can navigate Launchbox with my 8bitdo SN30 Pro + (in Switch Pro mode), open a game, play the game, exit the game (through a controller mapped hotkey into the BB Pause Screen), and then navigate BB to find something else to play. It's beautiful!

However, this DOES NOT work for Citra, Cemu, and Yuzu. When launching a game with one of these emulators using the same setup as previously described, I can play the game fine but can't exit. If I use the controller mapping hotkey I have set in BB, nothing happens. To exit the game, I need to use my keyboard. I can either hit Esc and exit the emulator or hit "Q" and get to the Paus Screen. If I go the Pause Screen route, my controller doesn't work there. I need to use the arrow keys on the keyboard to get to "Exit Game." Regardless of the method, when I'm back in BB, my controller doesn't work at all! I need to turn it off and turn it back on again to re-gain access to BB.

As noted, this only happens with Citra, Cemu, and Yuzu. Other emulators work just fine (so far, anyway; I'm not done adding systems).

I have turned on/off lots of settings to see if I can narrow down the problem (Pause Screen, Startup Screen, Use All Controllers, etc.) but nothing changes. The only thing I can think of is that these three emulators "steal" the controller and then don't give it back. I know that's a silly way to describe it, but that's what seems to be happening.

If anyone has any insight here, it would be most helpful! I've tried Googling as much as I can, but I'm going a bit mad now.

[Weird bug involving exiting Dolphin from Big Box]

Hi all. I'm having an issue that is most annoying. Technically, it's two issues but I'm sure they are intrinsically related so I'm posting both of them here to see if anyone knows what I should do.

Here is how I play Wii games on Big Box from my living room couch:

• Steam Link hardware connected to TV.
• Mayflash Dolphin Bar connected to Steam Link.
• Real Wiimotes connected to Dolphin Bar.
• Access Dolphin through Big Box in Steam.

All in all, this works well for me: I can play Wii games from the couch without many issues. This is how I start playing a game:

1. Fire up Steam Link using Xbox One controller
2. Navigate Steam using the controller and launch Big Box.
3. Navigate Big Box with the controller and launch Dolphin.
4. Set aside Xbox One controller and use Wiimotes to play.

When I'm done with a game, I pick up the Xbox One controller, turn it on, and then exit Dolphin using my shortcut (Start + B, although it shouldn't matter).

Anyway, with all that out of the way, here are the two problems:

• When I use my shortcut to bring up Bog Box's pause menu, it skips the pause menu and goes right to shutting down Dolphin. Usually I would hit the shortcut and then hit Exit Game, but I'm not given that option with Dolphin. To make matters worse, once I've exited Dolphin, my controller is unable to navigate Big Box at all. I need to go to my computer and manually shut down Big Box as the controller literally has no effect.
• If I'm in the middle of playing a Wii game and set my Wiimote down, I can't leave it unattended for long. After a few minutes of inactivity, Dolphin will stop responding to any controller input at all (both Wiimote and Xbox One). Once again, the only way to solve this is to go to my computer and manually shut down.

I am sure these two problems are linked and relatively sure they are Big Box issues, not Steam Link or Dolphin issues (although I could be wrong). If anyone has any advice, I'd really appreciate it!

[Steam Interfering with Controller config for RetroArch]

Did you ever figure out a fix for this? I am having this same problem.

[Big Box + Dolphin + Wii Remote = Pain]

OK, well, I guess I will try to remove the admin privileges for LB/BB. However, removing admin privileges from Dolphin is what helped me fix the problem stated at the beginning of this thread. Many online tutorials instruct you to give admin rights to Dolphin, which is why that was turned on in my setup.

[Big Box + Dolphin + Wii Remote = Pain]

Without running Launchbox as admin, though, it is impossible to launch Cemu games. Unless there is another way to do this?

[Big Box + Dolphin + Wii Remote = Pain]

I realize this thread is mad old but I eventually did figure this out. The problem is that Dolphin CANNOT be run as an Administrator but Launchbox needs to be. In other words, turn off the "Run as Administrator" option for Dolphin.exe and turn the same feature on for Launchbox.exe. This is what finally made things work properly for me.

[Citra on the TV while sitting on the couch...how do you all do it?]

I use the following setup:

Windows 10-based gaming PC > Steam Link Hardware > Launchbox (Big Box) as non-Steam game > Xbox One Controller

This allows me to sit on the couch, pick up my controller, and play all my games without needing to touch a mouse, keyboard, or my PC in any way. This, above all else, is what I want.

However, I'm at an impasse with Citra because I can't use the touch screen without needing a mouse. Here's what I've tried:

• Use Citra core in Retroarch: This actually works really well. I can load my games from the couch and Retroarch emulates a mouse using the right stick of my Xbox controller. However, the Retroarch core for Citra is not nearly as fast and efficient as the standalone. Also, certain games don't run in Retroarch because of missing Mii data. I have spent literally hours trying to fix this problem but nothing works. In other words, controls work great, but games don't.
• Use standalone Citra: Standalone Citra plays all my games and they look/sound great. However, Citra itself doesn't have a user-friendly way to emulate touch interactions with the second screen of a 3DS. I have no idea why Retroarch has no problem doing this and Citra can't, but that's just how it is. In other words, games work great, but controls don't.

So far, the only thing I can think of to get both games and controls working is to use Steam to remap my Xbox Controller within Launchbox to act as a mouse and keyboard rather than a gamepad. The problem here is that Launchbox would then do that for every other emulator, as there's no way for Launchbox to assign certain controller configs to certain emulators.

Anyway, I figured I'd throw this out there and see how other people are doing this. Maybe you've thought of something I haven't.

[Big Box + Dolphin + Wii Remote = Pain]

4 hours ago, Reevesad said:

I tried my setup last night playing wii via bixbox, and It was playing fine using the wii remotes. the only issue I came across was a low battery prompt on my screen. but the remotes were fully charged and didn't run out even after I stopped playing 2 hours later. 

So I have the same setup as you running Lunchbox/ big box and with the Emulator Dolphin.  

My Setup is as follows, the usb wii bar (pc version) is switched to 4.

I have an xbox one wired controller hooked to my pc (gonna upgrade to wireless at some point) this is used to start the wii/ start a game and exit a game. 

I have the automation setup on both launchbox and bigbox and enabled all controllers. 

If you want I can grab some screenshots of my dolphin contoller setup but tbh it was pretty much all setup. as it's just a case of choosing real wii remotes and then syncing the controllers with the wii bar.

OK, so this is REALLY helpful, thank you!

Your setup is very, very close to what mine is. I'm using wireless DS4 controllers instead of wired Xbox controllers, but I don't think that's what's causing the problem. Other than that, we're the same

I think what's happening is a conflict with Big Box and Steam Link. Other than the controllers, I have the exact same setup as you except I'm adding in the Steam Link.

Now, as I said earlier, everything with my setup works fine when I'm using the Link and Dolphin on its own, and it still works fine when I'm using the Link and Dolphin launched through LaunchBox's desktop mode.

So the problem must be a conflict between Big Box and the Steam Link, NOT Big Box and Dolphin.

If anyone has any ideas on how I could test this, let me know! 

 

[Big Box + Dolphin + Wii Remote = Pain]

21 minutes ago, Reevesad said:

Have you been able to setup the automation for the Wii remote to enable EXIT GAME? 

I've setup an xbox controller to exit a game back to big box but haven't been able to work the same out for Wii.

No, I haven't. But honestly, I don't think I've even tried, as my DS4 it's always right there to control LB. At this point, I have bigger fish to fry anyway!

[Big Box + Dolphin + Wii Remote = Pain]

Can you elaborate on your particular setup? Maybe there's something about your setup that's different from mine?

I am launching the standalone Dolphin, not the RetroArch core. It's the lastest update of Dolphin as well.

[Big Box + Dolphin + Wii Remote = Pain]

The Wii remotes are not setup through LaunchBox. However, they never have been. The setup I have worked flawlessly for a long while, until something recently went wrong with Big Box.

I have been doing some troubleshooting with a helpful Redditor, and we've concluded this is some sort of LB bug. We've come to that conclusion because:

• The Wii remotes work fine with Dolphin on its own (without LB or BB involved at all)
• The Wii remotes work fine with Dolphin launched through the desktop mode of LB.
• Controller support on every other emulator launched through LB or BB works fine.

Something between BB and Dolphin isn't playing nice when it comes to the Wii remotes. Now I have to figure out how to report a bug :-)

[Big Box + Dolphin + Wii Remote = Pain]

I have Launch Box set up with Dolphin to play Wii games. I use real Wii Remotes passing through the Mayflash Dolphin Bar. Everything works great, it's like having a real Wii.

However, things go wrong with Big Box. If I open a Wii game through Big Box it doesn't recognize my Wii Remotes. If I open Dolphin on its own, everything works great. If I open Dolphin in desktop mode, everything works great. Big Box mode? No Wii Remotes.

Can anyone assist with this? I'm going crazy.

[Wiimotes don't work within Big Box only]

I have Dolphin setup through Launch Box for Will games. I have the Mayflash Bar so I can use real Wiimotes for playing.

When I Launch Dolphin on its own, Wiimotes work great. When I launch Dolphin through the desktop mode of Launch Box, the Wiimotes also work great. However, when I launch a Wii game through Big Box, the Wiimotes don't connect to Dolphin. I have no idea why this would be. Any ideas?