Garrick_Greathouse Posted October 5, 2016 Share Posted October 5, 2016 Windows 10 fully updated. Asus N501VW Laptop. I've been using the Launchbox/Retroarch combination for about six months. I've set this up multiple times on multiple computers and can always figure things out until today. My NES and Genesis games are launching correctly via Launchbox, but not SNES games. I double click a rom and nothing happens. The weird thing is that the SNES games launch fine when played directly through Retroarch. I simply can not figure out why this is happening. Any thoughts? All the software involved was downloaded today, so it's all current. The only SNES core I can get to work in Retroarch this time around is SNES9X 2010. Any ideas? I've tried searching, but I guess I can't figure out the exact terms because I found nothing. Quote Link to comment Share on other sites More sharing options...
Lordmonkus Posted October 5, 2016 Share Posted October 5, 2016 Check your emulator settings in Launchbox. Quote Link to comment Share on other sites More sharing options...
Garrick_Greathouse Posted October 5, 2016 Author Share Posted October 5, 2016 (edited) Ok, Launchbox has a different SNES core listed than the one I downloaded for some reason. I fixed it by manually renaming the dll file to match what Launchbox thinks it should be. seems to work for now! Thanks for the help! Edited October 5, 2016 by Garrick_Greathouse Quote Link to comment Share on other sites More sharing options...
Lordmonkus Posted October 5, 2016 Share Posted October 5, 2016 Yup, the core needs to match. I suggest tryout out one of the BSnes cores if you have a decent CPU, the accuracy or balance are both excellent and better than Snes9x. Quote Link to comment Share on other sites More sharing options...
Garrick_Greathouse Posted October 5, 2016 Author Share Posted October 5, 2016 (edited) I use the bsnes cores on my home theater PC with great success, but for some reason they crash retroarch on my laptop. Edited October 5, 2016 by Garrick_Greathouse Quote Link to comment Share on other sites More sharing options...
Lordmonkus Posted October 5, 2016 Share Posted October 5, 2016 Weird that they would crash when other cores work. Could be a bad config file for the bsnes cores though. If you want to you can delete any bsnes core configs and try fresh. Quote Link to comment Share on other sites More sharing options...
MonsterTweaks Posted January 7, 2017 Share Posted January 7, 2017 (edited) This happened to me as well. LaunchBox is looking for a core file named snes9x_next_libretro.dll found in c:\EMULATORS\RetroArch\cores. However, the none of the dll core files that RetroArch downloads has the name snes9x_next_libretro.dll. THE FIX: rename the "snes9x_libretro.dll" core file to "snes9x_next_libretro.dll" and LaunchBox was able to emulate Super Nintendo fine after. You can rename any one of those snes9xXXX.dll files and it would probably work as well. I hope this helps someone else. Edited January 7, 2017 by MonsterTweaks fix quotes Quote Link to comment Share on other sites More sharing options...
Lordmonkus Posted January 7, 2017 Share Posted January 7, 2017 I have no idea in the world why you would need to do this sort of thing to fix it. I have never seen this issue before and I have used many builds of Retroarch going back to 1.2 including nightlies. I can almost guarantee the problem is in the command line parameters in Launchbox for Retroarch in your setups. Quadruple check your cores you have downloaded and the names of the cores you have in your associated platforms command line parameters. There have been times when I have been pulling my hair out trying to solve a problem with loading and even though I think every thing is right I almost always find a small typo. Quote Link to comment Share on other sites More sharing options...
DOS76 Posted January 7, 2017 Share Posted January 7, 2017 Sounds like his LB is looking for snes9x_next core which no longer exists and instead of changing LB to look for the new core names he changed the core name to match watch LB is looking for unless I'm reading it wrong. Quote Link to comment Share on other sites More sharing options...
Lordmonkus Posted January 7, 2017 Share Posted January 7, 2017 That's what it sounds like. Quote Link to comment Share on other sites More sharing options...
DOS76 Posted January 7, 2017 Share Posted January 7, 2017 Sort of the bass ackwards approach but still get the same results. 1 Quote Link to comment Share on other sites More sharing options...
Lordmonkus Posted January 7, 2017 Share Posted January 7, 2017 Indeed. Quote Link to comment Share on other sites More sharing options...
Garrick_Greathouse Posted January 7, 2017 Author Share Posted January 7, 2017 Completely reinstalled retroarch and LaunchBox on two different computers since this original post. One one install all cores work perfect all the time, the other install requires me to rename core dll's to whatever LaunchBox THINKS it wants. Same rom sets, and distributions of retroarch & LaunchBox released within a week of each other. No idea why it happens, but I found the renaming work around to suffice. Quote Link to comment Share on other sites More sharing options...
DOS76 Posted January 7, 2017 Share Posted January 7, 2017 Have you tried changing what LB is asking for to the core name that you have downloaded that should 100% do it. If you tried that and it didn't work I don't know what the issue is Quote Link to comment Share on other sites More sharing options...
Garrick_Greathouse Posted January 7, 2017 Author Share Posted January 7, 2017 Yeah, totally done that. On the desktop I need to rename the cores even after telling LB to choose a specific doll. Same software on my laptop? LB changes the cores fine. 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.