Jump to content
LaunchBox Community Forums


  • Content Count

  • Joined

  • Last visited

Community Reputation

7 Neutral

About PiperCalls

  • Rank
    8-Bit Processor

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Old topic but very interesting. Just curious how exit is working for you? There's an 'exit on esc' option in MFME but it doesn't exit it just switches from fullscreen to windowed mode.
  2. This is all I get after the "Launchbox initializing" screen. Thx...Piper
  3. DOS76, thanks for trying to help. No updates, it's a fresh install of Windows 7 Home Premium 32-bit with the motherboard drivers (Gigabyte), Video Graphics Suite (AMD) and I installed .NET 4.8 directly from Microsoft. Nothing else is installed/running. I was trying to eliminate variables so it's as clean as can be. Thanks...Piper
  4. C-Beats, thanks for trying to help. I thought maybe it was the 64-bit Windows version that was causing the issue so I wiped & tried to install with Windows 7 Home Premium 32-bit. I tried to install LB first in C:/Launchbox...same error so I wiped it and let it install in the User directory (the default install location)...same error. It hangs for a while on the "initializing..." screen then says it stopped working. Here is a copy of the error log... Just to be clear this is a fresh install of Windows 7 Home Premium 32-bit and I have only installed the motherboard drivers (from Gigabyte), the Video Suite (from AMD) and Launchbox, nothing else. Problem signature: Problem Event Name: CLR20r3 Problem Signature 01: LaunchBox.exe Problem Signature 02: Problem Signature 03: 5dd429b3 Problem Signature 04: mscorlib Problem Signature 05: 4.8.3928.0 Problem Signature 06: 5d39000b Problem Signature 07: 426b Problem Signature 08: 12 Problem Signature 09: System.IO.FileNotFoundException OS Version: 6.1.7601. Locale ID: 1033 Additional Information 1: 0a9e Additional Information 2: 0a9e372d3b4ad19135b953a78882e789 Additional Information 3: 0a9e Additional Information 4: 0a9e372d3b4ad19135b953a78882e789 Read our privacy statement online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409 If the online privacy statement is not available, please read our privacy statement offline: C:\Windows\system32\en-US\erofflps.txt
  5. Purchased a premium license, I have a couple PC's lying around so figured I'd setup a LB/BB system. I've tried installing on both PC's and neither one will launch LB. I did fresh OS installs on both (Win 7 Home Premium 64-bit) and both do the exact same thing. Try to launch LB and it sits on the "initializing" screen for several minutes and then errors out. I get exactly the same error log as this post ... I followed this thread and uninstalled .NET 4.8 & reinstalled it directly from the MS link given...it installed correctly. I have also turned of UAC. What am I missing here? Thanks...Piper
  6. PiperCalls


    It's a Mame4Droid issue. It starting happening on STV either 1 or 2 Shield Experience updates ago. It crashes back to the STV Home Screen when exiting Mame4Droid with any/all game browsers (I've tried 3). Thanks...Piper
  7. Yea ETA Prime goes into great detail showing what platforms/games work on the STV so that's a good resource. PS1, Gamecube, Saturn, PSP, Dreamcast and even Wii run very well on the STV. Wii of course has that funky controller so getting a regular controller to work with your games can be fun. PS2, PS3 not there yet..not sure if that's a hardware or (more likely) an emulator issue at this point. Not familiar with Wii-U so can't comment on that. The new (2019) STV is just a speed bump. Google discussed a new "hero" device coming out in 2020, my guess is STV is involved in that.
  8. I reached out to the Yaba dev via the email listed on the Play Store page but he/she hasn't responded at all. I know Yaba changes the launch intent parameters periodically so I'm pretty sure this is what's going on. Not sure what to do to get the details at this point. Maybe I'll post on the Play Store page but those questions rarely get answered...
  9. Ok, I'll reach out to the Yaba dev and see if I can get any info on the parameters for launch intent & send you whatever I get. For the RA-Flycast thing, I didn't see any way to generate a log but if there is anything I can do to help just let me know. Thanks...Piper
  10. Hi, I've updated to 0.28 with STV (2017). All ROMs are on external USB drive (setup as external not adopted/internal). I've imported 10 or so systems now and almost all imported fine and are launching correctly. Colecovision, SNES, Genesis, 32X, etc. I'm using RA with all those and they are working fine. I have run into issues on 2 so far... 1. Sega Saturn: Using Yaba Sanshiro (stand alone/free). Imported fine but games will not launch, it just immediately goes back to the LB game selection screen. This might not be a LB thing as Yaba updated to 2.10.2 a few days ago and they might have changed their launch intent parameters (again). I can launch games fine directly in Yaba but not through LB. 2. Sega Dreamcast: Using RA-Flycast. Imported fine but when launching a game RA tries to load the game as a Naomi game instead of a Dreamcast game. The Naomi bios screen comes up and then just errors out. I tried setting system type as Dreamcast (instead of Auto) in RA options and saving an override but it still tries to load up as a Naomi game each time. I can launch Dreamcast games in RA directly with no problem with the Flycast core. Other than that, it is working very well. Just wanted to give some feedback on the 2 "problem children" so far. Thanks...Piper
  11. PiperCalls


    I'm using RA PUAE core and it's working pretty well for me. I'd say about 80% of the HDF games load up & play fine. Haven't spent a ton of time with it but so far so good. I can't get UAE4ARM to even load a game.
  12. I've been using Mame4Droid on my STV for ages and it works pretty well. It uses the 0.139u1 set which has most of the games I want to play. For the newer games I use RA with the FBNeo core, works great on android. One note, the last STV update messed up something with some apps (Mame4Droid is one of them) that when you exit the game it goes back to the STV home screen instead of the launcher app. I'm sure it will get fixed but for now that's what we have. Cheers...Piper
  13. $5 is more than fair. Pay the devs if you want ongoing support & development. No such thing as a free lunch.
  14. That's great to hear (direct setup on Android). I already have all my roms & assets on my STV and don't use LB on PC so I've just been in a holding pattern on full setup with LBA. You're doing great work...thx....Piper
  15. Jason, just want to wrap this one up. I connected my DS4 controller and have launched & re-launched LBA several times and have no more weird behavior anymore. It was a bad controller, thanks for that...Piper
  • Create New...