dorr35 Posted July 29, 2016 Author Share Posted July 29, 2016 Today I opened Launchbox and downloaded the new version. Now every time I click on a game to play I get this error: File.__New - fullFilePath parameter cannot be blank to instantiate this class. I hope that someone can assist me with this. Gaming is much more enjoyable with your wonderful FrontEnd! Thank you for your reply. Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted July 29, 2016 Share Posted July 29, 2016 Hi @dorr35, are you using the betas? Can you try the latest beta that I just put out? Quote Link to comment Share on other sites More sharing options...
dorr35 Posted July 30, 2016 Author Share Posted July 30, 2016 Thank you for such a quick response. Using Ver. 6.7-beta-2 I am receiving the same error. I am able to launch games directly from RocketLauncher But when I try to launch from LaunchBox the games will not run. I have included the RocketLauncher.log Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted July 30, 2016 Share Posted July 30, 2016 Thanks @bundangdon. I have more confirmations that RL is working fine with the latest betas in the beta testing thread. @dorr35, unfortunately I think this must be a configuration issue of some sort. Quote Link to comment Share on other sites More sharing options...
dorr35 Posted July 30, 2016 Author Share Posted July 30, 2016 Thank you both for your assistance. It is now working wonderfully!! Quote Link to comment Share on other sites More sharing options...
fromlostdays Posted July 30, 2016 Share Posted July 30, 2016 Just a heads up, you no longer have to set up each system command line individually via associated platforms. You can set the default command line parameter and it will let launchbox automatically find the ini it needs. I just updated the rocketlauncher wiki with this info: First, set up RocketLauncher as an emulator in Launchbox. Name it something like "RocketLauncher" and point it to RocketLauncher.exe. *Do not point it to RocketLauncherUI.exe. Next, you have to set the default command line parameter in Launchbox. Set it to: %Platform% -p LaunchBox -f "(Type Full Path to LaunchBox.exe here)" -s "%platform%" -r Example: %Platform% -p LaunchBox -f "L:\LaunchBox\Launchbox.exe" -s "%platform%" -r Make sure that you've set up your default emulator for each system in RocketLauncher. This should have created a file called Emulators.ini in the directory RocketLauncher/Settings/[System Name]. The above command will tell Launchbox to look in this location for every system, so you DO NOT have to set up individual command lines for each system under Associated Platforms in Launchbox anymore. Hope it helps! Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted July 31, 2016 Share Posted July 31, 2016 Thank you @fromlostdays. Keep in mind that I've actually simplified this even further now. If you remove your Rocket Launcher emulator in LaunchBox, and then add a new one to replace it, you'll see that Rocket Launcher is now in the list with the latest beta. Selecting it will automatically populate all the right settings (saving you from having to manually add the path to LaunchBox, etc.). :) Quote Link to comment Share on other sites More sharing options...
fromlostdays Posted July 31, 2016 Share Posted July 31, 2016 I appreciate that a lot, and a bunch of people on RL will too. Thanks man! (Everything always gets easier after I bumble my way through it. These kids don't know how lucky they got it with launchbox, haha) Quote Link to comment Share on other sites More sharing options...
Jason Carr Posted July 31, 2016 Share Posted July 31, 2016 Hehehehe. Somebody's gotta be the one to break new ground. ;) 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.