markrock76 Posted August 28, 2020 Share Posted August 28, 2020 Just recently I have an issue with Retroarch throwing out this error only with the Flycast core and only when I have launched through Launchbox. If I run the same content directly from Retroarch I do not get this error. Anyone can point me in the direction of fixing my error. I did try to update but it did not fix my problem. Any help is appreciated. Thank You. Debug 2020-08-27 08-27-04 AM.log Quote Link to comment Share on other sites More sharing options...
markrock76 Posted August 30, 2020 Author Share Posted August 30, 2020 Anyone have a suggestion? Quote Link to comment Share on other sites More sharing options...
Rukushin Posted August 30, 2020 Share Posted August 30, 2020 I can't even get flycast to work at all so your doing better than I for even getting an error box. Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted August 31, 2020 Share Posted August 31, 2020 We have noticed weird things like this with certain cores in the past, but it's always been an issue with the core. Unfortunately I don't have any experience with that core, so I can't help out much here. Quote Link to comment Share on other sites More sharing options...
markrock76 Posted August 31, 2020 Author Share Posted August 31, 2020 Thanks for the reply. Quote Link to comment Share on other sites More sharing options...
sundogak Posted August 31, 2020 Share Posted August 31, 2020 On 8/30/2020 at 12:33 PM, markrock76 said: Anyone have a suggestion? I am able to run the flycast (build Aug 7) core with RA 1.9 and LB 11.4 (it also worked under prior LB versions). You might double check versions running are current as well as try a reinstall of LB. Copies of the LB installer are under ..\\Launchbox\Updates Also, you might try turning on logging in RA. Since issue is happening in LB, the easiest way is to go to your retroarch.cfg file in the Retroarch directory and search for the following: log_dir = ":\logs" log_to_file = "false" log_verbosity = "false" If you change the "false" flags to "true" then Retroarch will keep a log and place it (default) in Retroarch\logs whenever RA is launched. That way you don't have to mess with your command line in LB for RA. Then there might be a clue in the RA log as to what is causing RA to crash when launched through LB. 1 Quote Link to comment Share on other sites More sharing options...
markrock76 Posted September 1, 2020 Author Share Posted September 1, 2020 (edited) Thanks sundogak I reinstalled LB 11.4, my Retroarch is 1.9, and cores are updated. I confirmed again that the problem does not exist when launching from Retroarch only when launching from LB. The issue from what I can tell is only with Flycast core. The issue almost always happens within the first 2-4 minutes of starting emulator (so I am able to play for a very short time) or it seems to always happen when I press F1 to bring up Retroarch Quick Menu. I have attached both logs if any one knows what to look for in these. Debug 2020-09-01 01-31-29 PM.log retroarch.log Edited September 1, 2020 by markrock76 Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.