BurritoBaby78 Posted Sunday at 07:47 PM Posted Sunday at 07:47 PM (edited) I use custom emulator setups for each of my emulators that calls a batch file as there is other processing I like to do. This works well for all emulators I have set up, except one. Kega Fusion is no longer working. It used to and I haven't made any changes. Here's what's happening. Set up the emulator in LB to call the batch that launches Kega. Settings in the emulator config as follows: Application Path: Points to batch file location Default Command-Line Parameters: -fullscreen Sample Command: shows "Fusion.bat -fullscreen "FULL\PATH\TO\ROM\FILE" I have also gone in and cleared out any default emulator command line args in the associated platforms screen. I setup the batch to output what is passed to it from LB so I can troubleshoot. It should be passing -fullscreen "path to rom" based on my config settings. However, it's passing "-fullscreen" correct, but the 2nd arg it's passing is the path to the batch file. I'm not sure why and can't get it to pass the rom file location. I even tried creating another custom emulator and reconfiguring it all again, same thing. Thanks in advance for any help. Edited Sunday at 07:55 PM by BurritoBaby78 Quote
JoeViking245 Posted Sunday at 08:36 PM Posted Sunday at 08:36 PM 36 minutes ago, BurritoBaby78 said: It should be passing -fullscreen "path to rom" based on my config settings. However, it's passing "-fullscreen" correct, but the 2nd arg it's passing is the path to the batch file. I'm not sure why and can't get it to pass the rom file location. 1st thought is to double check the path to the ROM file. (i.e. Edit the game and look there) It would be a major bug if it was actually passing the emulators path rather than the ROMs path. If it truly is, definitely file a bug report. Until then, you may try adding to the end of the parameters %romfile% -fullscreen %romfile% If you're still having issues, (not to say you don't know what you're doing and "prove it") can you post some screenshots? Emulator - Default section and Associated Platforms section Game_in_question - Main section, Launching section and the Emulation section. Quote
BurritoBaby78 Posted Sunday at 11:48 PM Author Posted Sunday at 11:48 PM 3 hours ago, JoeViking245 said: 1st thought is to double check the path to the ROM file. (i.e. Edit the game and look there) It would be a major bug if it was actually passing the emulators path rather than the ROMs path. If it truly is, definitely file a bug report. Until then, you may try adding to the end of the parameters %romfile% -fullscreen %romfile% If you're still having issues, (not to say you don't know what you're doing and "prove it") can you post some screenshots? Emulator - Default section and Associated Platforms section Game_in_question - Main section, Launching section and the Emulation section. You are the man JoeViking! The -fullscreen %romfile% worked. Thanks again! 1 Quote
JoeViking245 Posted yesterday at 12:02 AM Posted yesterday at 12:02 AM 11 minutes ago, BurritoBaby78 said: You are the man JoeViking! The -fullscreen %romfile% worked. Thanks again! Thanks. Glad it worked. But it's still a little perplexing as to why it was passing the emulators application path. But since you're the first that I'm aware of that has had that issue, maybe it's a one-off Burrito thing. Quote
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.