Jump to content

Recommended Posts

Posted

Thanks for the info Floatingyeti. I hadn't updated the mame core yet so I have been able to save it under the version name and change it in the rocketlauncher settings..

I also use different versions of Retroarch in order to "freeze" certain systems in their working state (hopefully).

Have you been able to pinpoint the problem in the retroarch module and/or determine what change caused the problem in the updated mame core ?

Posted

I think the solution (for now) is to set RA Options: Resolution = 1280x720.

I have had resolution set to 1920x1080 since I started using RA(MAME) with absolutely no issue.

I just tested a few systems that were crashing on the new core when launched from RocketLauncher.  They seem stable now, but I need to go through every system again today.

I don't know if this is a module issue.  I think this is specifically a version 0.247 issue. I will figure this out and update the compatibility guide today.

Probably the easiest "fix" is waiting for 0.248 but I will do my best to sort this out now.

 

  • 6 months later...
Posted
1 hour ago, Mangusto said:

Well, I had a similar problem solved when I was able to deal with the module, so you are generally correct.

What was the problem and how was it fixed?

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...