borland502 Posted December 8, 2020 Share Posted December 8, 2020 I have a bit of a puzzle on my hands with running either Retroarch Mame 2016 or the standalone .176 & up within launchbox, but first some vitals: Processor AMD Ryzen 7 1700 Eight-Core Processor, 3200 Mhz, 8 Core(s), 16 Logical Processor(s) Version Windows 10.0.19042 Build 19042 Adapter Description NVIDIA GeForce GTX 1080 Roms mounted via network share on drives Y & Z Test Rom: 1942.zip (2016 set) I've been able to run roms with retroarch's mame 2016 core, or with the standalone .225 edition outside of launchbox. But if I try the hat trick of running the network mounted roms through launchbox then Mame (or retroarch) will try to start up and then quit out. Is it the network pathing? That doesn't seem to be a problem elsewhere. Quote Link to comment Share on other sites More sharing options...
Retro808 Posted December 9, 2020 Share Posted December 9, 2020 37 minutes ago, borland502 said: I have a bit of a puzzle on my hands with running either Retroarch Mame 2016 or the standalone .176 & up within launchbox, but first some vitals: Processor AMD Ryzen 7 1700 Eight-Core Processor, 3200 Mhz, 8 Core(s), 16 Logical Processor(s) Version Windows 10.0.19042 Build 19042 Adapter Description NVIDIA GeForce GTX 1080 Roms mounted via network share on drives Y & Z Test Rom: 1942.zip (2016 set) I've been able to run roms with retroarch's mame 2016 core, or with the standalone .225 edition outside of launchbox. But if I try the hat trick of running the network mounted roms through launchbox then Mame (or retroarch) will try to start up and then quit out. Is it the network pathing? That doesn't seem to be a problem elsewhere. In >Tools Manage Emulators when you edit Retroarch do you have the correct core selected in the Associated Platforms tab and does the Platform name in the Associated Platforms tab match exactly as the platform name appears in LB? Quote Link to comment Share on other sites More sharing options...
borland502 Posted December 9, 2020 Author Share Posted December 9, 2020 Yeppers. Quote Link to comment Share on other sites More sharing options...
borland502 Posted December 9, 2020 Author Share Posted December 9, 2020 (edited) Early on, I must have tested a bad rom. 1942, my sample test, works if I switch to the .225 standalone and launched through retroarch. I only converged on 1942.zip because I wanted to post and make sure I was comparing apples to apples. That said, whatever is built into retroarch and the .176 (exact) edition standalone do not work. So whomever made the rom set, while I bless them, was probably not spot on with the compatibility. Edited December 9, 2020 by borland502 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.