Jayinem Posted Thursday at 06:30 PM Posted Thursday at 06:30 PM It comes as a Launcher to boot the games, but usually you can work around that. However I've tried command prompt and tried --game and just putting the path to the game but it doesn't do anything. It's a pretty good emulator because the controls are already configured unlike the original Model 1 2 and 3 emulators, and it has support for higher resolutions. Just need to be able to add it to Launchbox somehow. https://github.com/uronito/SEGA-MODEL-1-2-3-Emulator-for-windows Quote
Noah Evans Posted Thursday at 07:11 PM Posted Thursday at 07:11 PM LaunchBox can launch it only if the launcher accepts a ROM argument. In Edit Emulator, point Executable to the launcher, set Working Folder to its folder, and try just "%romfile%" or --game="%romfile%" in Default Command-Line Parameters; don’t put the ROM path in the executable field. If neither works, the launcher likely expects an internal game name/index or has no CLI—check its readme/config or use a small wrapper. What syntax does its help/readme document? Quote
JoeViking245 Posted Thursday at 07:16 PM Posted Thursday at 07:16 PM 1 minute ago, Noah Evans said: LaunchBox can launch it only if the launcher accepts a ROM argument. In Edit Emulator, point Executable to the launcher, set Working Folder to its folder, and try just "%romfile%" or --game="%romfile%" in Default Command-Line Parameters; don’t put the ROM path in the executable field. If neither works, the launcher likely expects an internal game name/index or has no CLI—check its readme/config or use a small wrapper. What syntax does its help/readme document? Nice totally-non-helpful AI response. Might try starting to reply to posts that you actually have personal knowledge on and using your own words. Not using an ignorant AI's response. 1 Quote
gamingirdbir Posted 1 hour ago Posted 1 hour ago Nice find. You don't need the emulator's own launcher for this: Tools -> Manage Emulators -> Add, browse to the emulator EXE, then map your platform and file extensions (.zip/.7z/.cue) on its Associated Platforms tab. LaunchBox passes the selected ROM path as the last command-line argument automatically, so once associated it should boot straight into the game. If the build ignores bare paths, check the GitHub readme for the exact switch it expects - some front-end style launchers only accept their own profile names, and a tiny batch/AHK wrapper translating the ROM name into the expected argument does the job. What --help prints usually makes the right switch obvious. 1 Quote
Jayinem Posted 43 minutes ago Author Posted 43 minutes ago 1 hour ago, gamingirdbir said: Nice find. You don't need the emulator's own launcher for this: Tools -> Manage Emulators -> Add, browse to the emulator EXE, then map your platform and file extensions (.zip/.7z/.cue) on its Associated Platforms tab. LaunchBox passes the selected ROM path as the last command-line argument automatically, so once associated it should boot straight into the game. If the build ignores bare paths, check the GitHub readme for the exact switch it expects - some front-end style launchers only accept their own profile names, and a tiny batch/AHK wrapper translating the ROM name into the expected argument does the job. What --help prints usually makes the right switch obvious. There doesn't seem to be any command line arguments, any I add such as -h --help --game --play fails to work. I will try your method later though. 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.