latin625 Posted December 22, 2017 Share Posted December 22, 2017 Hi, I recently has started taking another jab at RL and got it setup and running via various video tutorials. My new problem now is that when it launches MAME 1.77 it just shows a black MAME screen that says "loading game 0%" and it stays like that. When I press ESC, it doesnt close the window and I have to hit the taskmanager to close the MAME 1.77 by force. These are very small roms files and disable 7z and rom checking in RL, but the game will not load. Outside of RL and only using LB, i have no issues. I want to use RL because i have been told that this is how to handle Marquees, Bezels and even U360 joystick settings much easier, instead of going through my massive library and doing each game one at a time. help? Thanks!!!! Quote Link to comment Share on other sites More sharing options...
dragon57 Posted December 22, 2017 Share Posted December 22, 2017 It sounds like you have the Fade in screen enabled. If so, turn that off temporarily so you can see what is going on under the covers of RocketLauncher. Quote Link to comment Share on other sites More sharing options...
damageinc86 Posted December 22, 2017 Share Posted December 22, 2017 Yes go to the fade tab of that system and turn it off, then you might be able to see any error messages that RL is showing you. 1 Quote Link to comment Share on other sites More sharing options...
latin625 Posted December 22, 2017 Author Share Posted December 22, 2017 tried it and removed fades... still stays stuck on the loading 0% black screen of MAME. If I run it in LB, the loading screen in MAME fills up and the game loads. Have no idea what to do next. lol. Quote Link to comment Share on other sites More sharing options...
latin625 Posted December 22, 2017 Author Share Posted December 22, 2017 ok, the other platforms seem to work ok, though the screen is either too small or off center. No luck on mame though... Quote Link to comment Share on other sites More sharing options...
damageinc86 Posted December 22, 2017 Share Posted December 22, 2017 wow that's really weird. Never ran into that when I set up rocketlauncher. No idea. Quote Link to comment Share on other sites More sharing options...
dragon57 Posted December 23, 2017 Share Posted December 23, 2017 Your next step should be turn on the RocketLauncher logging, then post the result on the RocketLauncher forum and ask for help there. 1 Quote Link to comment Share on other sites More sharing options...
latin625 Posted December 23, 2017 Author Share Posted December 23, 2017 Thanks Dragon57! Here is what I get from the log error: CRC Check - No CRC defined on the header for: D:\Arcade\RocketLauncher\Module Extensions\gdip.ahk No idea what that means. lol. I am using Mame 177 if that matters. It works great via LB Quote Link to comment Share on other sites More sharing options...
dragon57 Posted December 23, 2017 Share Posted December 23, 2017 Hmm, I know what it means, but that error makes no sense in context with MAME specifically. That ahk library is used across other emulator modules as well. Are you using the latest RocketLauncher code? Have you tried forcing an update so you are assured the RocketLauncher files are all correct? 1 Quote Link to comment Share on other sites More sharing options...
latin625 Posted December 23, 2017 Author Share Posted December 23, 2017 yup. Just checked it three times. No updates. Quote Link to comment Share on other sites More sharing options...
latin625 Posted December 23, 2017 Author Share Posted December 23, 2017 Hey Dragon! So i took your comment as a sign that things may be screwed up in the settings and the version of RL to begin with. Downloaded a fresh version, installed and BOOM! It worked no issues with MAME. Thanks man. Gonna load up the systems and then work on seeing if someof my other issues have cleard up too, like the scanlines and full screen on Daphne. Thanks again! Quote Link to comment Share on other sites More sharing options...
dragon57 Posted December 23, 2017 Share Posted December 23, 2017 Excellent! I'm glad you got it working. Odd errors like that almost always point to corruption of a file, or two. If nothing comes to mind as to how this happened, you may want to keep a check in the Event Viewer of Windows for disk related errors. You may have a hard drive getting ready to die. 1 Quote Link to comment Share on other sites More sharing options...
latin625 Posted December 23, 2017 Author Share Posted December 23, 2017 oh boy.. hope not! The drives are pretty new, but lots of frozen apps and lockups may be corrupting the drive. I am trying to move everything to one drive so I can buy a 6 or 8tb external. Thanks again man. 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.