Search the Community
Showing results for tags 'crashing'.
Found 4 results
Hello! I've been using LaunchBox for about 2 years now, ever since I finished my MAME cabinet. I never had an issue until the 9.x update. I am currently on the latest version. I am running MAME 0.203. Ever since updating, I always have an issue launching my first game. For example, I'll click on Street Fighter 2 in Big Box mode. 9 times out of 10 it will start correctly flashing the buttons and speak its commands (LEDBlinky) and everything will go well. But then the game will never start. I will either get a black screen, or it will get stuck at the first screen where MAME tells you the info like screen res and such. I always have to force close Big Box and then start it up again, and then everything works fine. Obviously this is a pretty big issue because my young children want to play it sometimes when I am not home and it's not easy explaining to them or my wife how to force close a program and then open it again, especially with arcade controls. Does anybody know what changed from 8.x to 9.x that is causing this? I doubt it's my computer as it's an i7 @ 4.0ghz with 12GB of RAM and an SSD. And this issue did not exist with 8.X for me. I disabled "show loading screen" but that didn't seem to fix it. I even have issues sometimes when I exit games, where I exit and it takes forever and I have to force exit (kill Big Box then open it again), though this exiting issue is a lot less common than the startup one. I am running Windows 10 Pro. Any info would be greatly appreciated!
When I crank up Reicast's internal resolution to something like 1920x1440, it looks great, and runs great when I'm using Retroarch on its own. However if I launch the same games via Launchbox, Retroarch is crashing when using any Reicast internal resolution other that 640x480. Is there a conflicting configuration somewhere that Launchbox would care about? One that doesn't Retroarch when running independently? Update: Looks like the crashing is dependent on shaders, everything works great with no shaders enabled, once enabled starting a game from Launchbox crashes Retroarch. Update 2: Narrowed it down further to crashing only when a shader alters geometry, I can work around that but I'm still curious why this would only come into play when launching from Launchbox?
Outside of LaunchBox Mame works fine. I even have it set up to where it will get games from the folder inside the Launchbox games folder. I'm testing out 10 yard fight. And it works if I launch it outside of LB. But if I hit play it will start up and then crash. What am I doing wrong?
Hello everybody. So I'm really new to Launchbox, just downloaded and bought premium today, and I can't figure out my controller issue. Every game I've tried through Wii, PSX, & NES so exits the game anytime I press the start/options button on my DS$ controller. Also if I press the right trigger the screen flashes and the controller won't work in the game anymore. I've searched the internet and also the forums and couldn't find anything mentioning these problems. I've gone through the pad configs on the emu and in LB and still can't fix it. Any help would be greatly appreciated. Thanks for any help.