Alumriel

Posting this here for visibility, in case anyone else with a new GRS Super Joystick has the same issue and wants to upvote my bug report. https://bitbucket.org/jasondavidcarr/launchbox/issues/8211/odd-behavior-with-new-grs-super-joystick

TL;DR - install Windows 10 on a MicroSD card, then use BigBox there. 😉 I used this guide and it worked wonderfully - https://wagnerstechtalk.com/sd-windows/ Even though the Steam Deck doesn't yet support dual boot, it's pretty easy to switch back and forth using the bios boot menu.

FYI to anyone finding this thread - there is now an installer that does pretty much EVERYTHING for you (the "baller" installer): https://www.nailbuster.com/wikipinup/doku.php?id=baller_installer

I also created a ticket

Was this resolved? I have a similar problem with my Logitech G923 racing wheel. It works fine in anything outside of Launchbox. I use it in MAME, Retroarch, Forza, etc... It's only Launchbox that doesn't see it.

The wheel is detected just fine in Forza Horizon 5, and other games, on the same PC, and is shown in dxdiag. The problem only exists in Launchbox, so I'm a bit skeptical of the conclusion that the problem exists outside of Launchbox. I'm going to submit a bug for this.

Logitech G923 Xbox/PC wheel arrived today. Works perfectly fine in Windows and MAME, but Launchbox/BigBox doesn't see it. I have checked "Enable Game Controllers". Any ideas?

Fair enough. Good luck. 😃

Every once in a while, I'm right about something. 😃 But you may not have to resize the images, depending on what that person was suggesting on StackOverflow. I don't know what it means to "Move your image in the (hi-res) drawable to drawable-xxhdpi.", but it was suggested as a solution. Maybe this is also helpful - https://exchangetuts.com/android-canvas-drawing-too-large-bitmap-1639500845290684

Sorry, I should have been more clear. I meant the versions of the rom dumps, not the entire set being playable. Meaning that, if you use the latest MAME rom set with FBNeo, you shouldn’t get any errors that the checksum of the rom is wrong, due to the rom dump being newer than what FBNeo expects.

It was my understanding that FBNeo uses the same romset as current MAME. At least, that's what I thought I saw a developer say in a post somewhere a while back, on reddit. I use both FBNeo and MAME and just use the current MAME rom set (from Pleasuredome). I have MAME set as my default emulator, but switch to FBNeo on a per-game basis, if MAME doesn't run the game well.

I would be happy to pay for a linux/steam version if Jason ever decides to make one.

you can go back and edit posts 😃

This seems related to the log message - https://stackoverflow.com/questions/40835514/android-canvas-drawing-too-large-bitmap

I'm having the same problem. I've repeatedly cleared out ALL media, roms, etc and started over from scratch. EDIT - Debug log attached. (looks like a bitmap is too large - even though I didn't control where the bitmap came from - I assume it's coming from a launchbox server) "2022-04-27 04:55:46 PM DISPLAYED EXCEPTION: Canvas: trying to draw too large(127955808bytes) bitmap." Device - Ayn Odin Pro OS - Android 10 Debug 2022-04-27 04-54-39 PM.log