[Issues with new GRS Super Joystick (Ikari warriors style) in Big Box navigation]

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

[Launchbox on Steam Deck]

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.

[Visual Pinball X + Bigbox ... a starters guide]

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

[Either Launchbox doesn't recognize my controller or I don't know how to add it...]

I also created a ticket 

[Either Launchbox doesn't recognize my controller or I don't know how to add it...]

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.

[Launchbox does not see my Logitech G923 wheel?]

3 hours ago, faeran said:

LaunchBox just uses the Microsoft built-in directx controller support, so there must be some miscommunication happening between that particular controller and directx.

You could try a third party controller mapping program that would convert your inputs into an emulated xinput controller. I've had good luck with x360ce in the past.

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.

[Launchbox does not see my Logitech G923 wheel?]

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?

 

[crash with Raiden]

21 minutes ago, Jason Carr said:

Yeah, unfortunately it's not possible to move images from the drawable folder to that folder, because they're not included with the application. They're downloaded from the games database, so those folders aren't even relevant. There are a few other things to try in that thread, but unfortunately I'm doubtful that they'll make any difference. Worth a shot though.

Fair enough. Good luck. 😃

[crash with Raiden]

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

[Mame and FBNeo: how to make them live together]

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.

[Mame and FBNeo: how to make them live together]

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.

[Launchbox on Steam Deck]

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

[PS2 direct game launch]

On 5/15/2022 at 5:22 AM, orac31 said:

sorry about large text 

you can go back and edit posts 😃

[crash with Raiden]

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

[crash with Raiden]

On 5/11/2022 at 4:13 PM, Jason Carr said:

That's odd. I'm guessing maybe there might be a corrupt image or video download for that game. Can you try deleting all media associated with that game?

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

[Ayn Odin Emumovies login freezes app]

I don't think it's a bug.

I have an Ayn Odin Pro and also use LaunchBox (version 1.1). Emumovies downloads work fine for me.

[Visual Pinball X + Bigbox ... a starters guide]

Thanks for this guide. My end goal is to setup a combined arcade/pinball setup, with a monitor stand that "transforms" from arcade mode to pinball mode. I will also have a DMD and "backglass" monitor up above, so I'm hoping that will work with Bigbox.

Here is the TV stand I just purchased - https://www.buystuffarcades.com/products/t-t-transforming-tv-stand

[Mame doesn t work]

Well, MAME can work perfectly fine with both Retroarch and Launchbox on Android. I'm using it myself. I switch between MAME and Final Burn Neo depending on the game.
The critical part for arcade games is that the rom set needs to match the version of MAME you're using. Meaning, if you're using MAME 2003, you need a rom set specifically for MAME 2003 (which is based on the 0.78 build).

My setup in Launchbox:
Default Emulator - RetroArch (64-bit sideloaded)
Default Core - mamearcade_libretro_android.so (or fbneo_libretro_android.so depending on the game)

Note - The MAME choice maps to the "Arcade (MAME - Current)" core in Retroarch, which I use because I have a relatively powerful CPU (Snapdragon 845) - older chips should maybe use older MAME cores, or else the experience might be choppy
The "MAME - Current" core is based on fairly recent build of MAME (maybe 0.239), so I'm using roms from that set, not an older set.

[Mame doesn t work]

I'm having a little difficulty understanding your problem, so I apologize if I don't quite understand.

Note that this for is specifically for the Android version of Launchbox. Are you using Android? or a Windows PC?

Also, neogeo games are just a small subset of all games you can run in MAME. Have you tried running games that aren't neogeo based? There are literally thousands.

Lastly, have you tried using Final Burn Neo? This is another emulator core (like MAME) that runs many arcade games, including neogeo.

[Metadata/media shows for some games, but not others.]

22 hours ago, Jason Carr said:

Most likely this was caused by a bug with a previous version, I think. There actually isn't a way to refresh the cache on Android (because the cache doesn't really work that way).

To fix it, you should be able to delete the platform, but choose the option not to delete any media. Then just re-import the platform, and all the media should show up. Let me know if that doesn't fix the issue. If it doesn't, then we probably have a bug that I'm unaware of.

Unfortunately, this did not work.
However, I re-did it and deleted all folders I was given the option to delete (including media), then things seem to be fine now.
Odd, but I only have around 700 games, so not a huge deal.

On a possibly related note - when trying to view "Raiden", Launchbox crashes.
If I skip past it quickly to other games, including Raiden sequels (like Raiden DX), they display fine.

This is even with a "clean" install of the platform.
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)

Debug 2022-04-27 04-54-39 PM.log

[Metadata/media shows for some games, but not others.]

Now that I have an Odin handheld, I'm using the android version of Launchbox in earnest.

I don't know if this is a bug or what, but I've noticed that after downloading media for all my games, the "Clear Logo Image" (which I think is what replaces the name of the game in the "scroll list") isn't showing for some games, even though I know the media exists.
When I go to "edit data", it shows "None" for the "Clear Logo Image", HOWEVER, I can open that option and view the image.
Any idea what's going on here?
At least half my arcade games are like this.

Details (which may not matter):
Odin Pro handheld
Android 10
Launchbox v1.1

Images attached to show what I mean.

[Navigation impossible in Android app on Ayn Odin]

I got my Ayn Odin Pro yesterday and I can navigate launchbox 1.0 no problem. No idea why it works fine for me.

My problem is different. I’ll make a separate post for it. (Launchbox just opens Retroarch, not the game)

[LaunchBox on Nvidia Shield - Can't Launch/Read Only Error]

Maybe I'm late to the party here, but it works fine for me on a 2017 Shield Pro. I didn't have to do anything special, so maybe it was fixed before I installed it.

[What are people using for arcade games on Android?]

18 minutes ago, JoeViking245 said:

Don't forget to be nice and let it 'seed' for a little while afterwards. 

100% agree. Pleasuredome is very strict about greedy people. But they are a superb source. Well worth the effort.

[What are people using for arcade games on Android?]

I'm using Retroarch (the "normal" one you download from the Play Store, not sideloaded) with the "Current MAME" core (currently 0.232) with a curated subset of games from the current MAME rom set (now at 0.235).

Generally, it works fine on my Nvidia Shield TV.