Jason Carr

Apparently the issue is Android 13. I did all my testing on Android 12, and everything was working great. Now, since my tablet updated to Android 13, it's broken with the same error message. I don't really understand how Android 13 would introduce that error when launching Skyline, but Android is Android I guess.

Okay, what device are you using and what version of Android is it running? Have you tested opening games up manually in Skyline?

The Android platform should show up under Handhelds. I still don't really understand what's going on with Skyline for you. The version that we've installed is the free version from here: https://skyline-emu.one/download We've just installed the very first one at the top of the list. Are you installing Skyline from somewhere else?

LaunchBox for Android 1.7-beta-2 is out now with the following: Fixed the issues with the Pure theme Fixed issues with the updated grid view not sizing correctly when switching between portrait and landscape Fixed the Android platform not showing up when using platform categories Vertical wheel spacing and sizing have been adjusted to make a cleaner experience between devices

Thanks guys for the reports. I should have a new beta out later today. Do you have an outdated version of Skyline installed, by chance? We've fully tested the latest version and we're able to run it without issues. That's probably a good idea for the future, but it is likely a ways off.

There are definitely some devices that are just going to be too slow for LaunchBox. Let us know if you'd like a refund.

It's been uploaded to the Themes Manager. I haven't yet uploaded it to the forums.

I am not aware of any issues with that theme, but I will admit that I haven't tested it in a very long time, so it is possible.

I've done my most recent testing (that was I referring to on those three machines) with Unified Redux and Default.

We're not really out to prove anything here; I'm only trying to clear things up. The people that aren't having issues don't tend to speak up. Regardless, I would appreciate if we could avoid negative assumptions like that. It's just not necessary or helpful. We would much rather send you out a refund than to have negativity like this on the forums, so just let us know if you'd like a refund because you're unhappy with the product.

Please don't comment the exact same thing in multiple threads. We are working on this issue...and I can confirm that not everyone is affected by it at this point. In fact, I've successfully run the latest official release on 3 different machines for over a week running attract mode without issues. This is not to say that it is not an issue, because I know it is. The trouble is that it's not affecting every machine and so it's been difficult to pinpoint.

Hey all, I have LaunchBox for Android 1.7-beta-1 out now with the following: LaunchBox for Android can now be fullscreen! Two new options have been added to the main Options menu for hiding Android's top status bar and bottom navigation bar. LaunchBox for Android now supports platform categories such as Arcade, Computers, Consoles, and Handhelds. A new option to turn this on or off is available in the Options menu (Start with Platform Categories). Arcade filters have been added for various arcade genres and manufacturers, similar to LaunchBox on the desktop. A new option to turn this on or off is available in the Options menu (Override Arcade Genres with Improved Arcade Filters). A new Favorites filter has been added to all filters views (that have favorited games), with an option to turn it off in the Options menu Nintendo Switch emulator Skyline is now supported The Recently Played filter will no longer show up if no games have been played Performance has been significantly improved with the games grid views, which now use a more native renderer Downloading missing media should now do a better job of replacing any 0-byte files that were the result of previous failed downloads Per the RetroArch auto-install stuff, progress is being made towards getting the changes integrated into RetroArch, but we're not there yet. Those changes will probably make it into version 1.8. Even though this is the first Android beta to come out, we are planning on having it be the release candidate, and we hope to release the official version next week. Any testing you can do would be appreciated.

We got it in for the next beta.

Hey all, I'm looking for instructions on how to launch Skyline. Does anyone have any information on that?

I don't exactly have anything that can weigh it lol. It doesn't seem significantly more heavy than my previous Rec Room Masters cabinet, but I really don't know. I moved it to the destination room before final assembly.

Hey all, the cabinet video is live:

Just to update everyone here, there will be a video coming out soon on the YouTube channel to show off the cabinet a bit. But also, I'm happy with pretty much everything on the cabinet, other than the Mag-Stik Plus joysticks, which are finicky and can often be very hard to switch between 4-way and 8-way. Therefore, I'm gonna take @Headrush69's suggestion from earlier in the thread and replace them with ServoStiks from Ultimarc instead. Apparently, LEDBlinky will automatically switch those sticks from 4 to 8 ways (and vice versa) depending on the game being played. Also, I wanted to note that I ordered two different master/slave power strips: https://smile.amazon.com/dp/B08LSXXG7R?psc=1&ref=ppx_yo2ov_dt_b_product_details I started with that one and it works just fine to turn on/off the monitors and such with the internal PC, but it takes like 15-20 seconds for them to turn off after the PC turns off, so it makes for an ugly shut down process. I then ordered this one and lucked out: https://smile.amazon.com/dp/B002K8S2J6?psc=1&ref=ppx_yo2ov_dt_b_product_details The APC immediately turns off the monitors and speakers and such once the PC is shut down. So it's super smooth. One last note, I'm using the cab to improve the Big Box experience a bit regarding startup, shutdown, etc. The next version of Big Box will have an option to automatically use Big Box as the Windows shell, which makes for a much cleaner startup experience. I also fixed an issue where volume control bindings did not work when using Big Box as the Windows Shell. A beta should be out soon with those new features. Oh, and I also improved LEDBlinky performance.

@Fullgonzo Glad you got it working, but unfortunately I can't really say what actually did it. That Files.xml file is only used for imports and it comes from the LaunchBox Games Database. It shouldn't have anything to do with launching games. So, who knows.

Are you using the Duckstation app or the core for RetroArch?

Okay, well that's interesting. You definitely shouldn't need a copy of anything on both your SD card and internal storage. What do your LaunchBox settings say for your LaunchBox folder?

Hi @TheShrike, honestly I don't really know where to start with this. I've never seen anything like it before. You're saying that this issue only happens with SNES? Are you able to launch other platforms' games using LaunchBox without issues?

I'm not positive, but I think issue might be specific to the Odin Lite. I say that because I've never seen it on any of the devices that I have, and it's never been reported by anyone else, so I assume it must somehow be specific to that device. I know that we have lots of users on the regular Odin and they haven't been reporting that issue, so I assume it's only the Lite, but I can't say for certain. Unfortunately I think we would need to get a hold of one before we would be able to fix the issue (or determine if it's fixable or not).

Unfortunately it may not be possible right now to run a custom RetroArch core, because of the way that RetroArch works. We've tried to make sure that all possible cores are available, but you may have found an issue here. We do have plans to add an option for custom RetroArch cores, but as of right now, I don't believe that will work.

Thanks @shapeshifter; we've chosen to only allow importing entire MAME sets because of the complications with how files inside of MAME sets work. Depending on the type of set that you have, it may or may not work to pick and choose different files. So generally, we only recommend importing whole sets, which is why things work the way they do.

I suppose it's possible that Unified Refried has a memory leak. We should definitely look into that. Can you try using a different theme (maybe try the Default theme) to see if you have the same issue?