Jason Carr

Wow, great work, Hani. I will at least fix that issue with the origin links for the next release, so that at least that method works. Hopefully an import isn't too far off.

Good idea, duck.

Hi retro, this actually *is* an emulator-specific issue. Every emulator is different and requires different command line parameters. I'm not familiar with Project Tempest, but this is the best thread I could find: http://www.gameex.info/forums/topic/9199-project-tempest-loader/ Are you using the PTLoader.exe file? It does look like there are some issues with that particular emulator and auto-loading games, though I haven't spent too much time looking into it.

Wow. I haven't dealt with Origin too much, but that sucks. I was under the impression that everything "just worked" when you used the game's EXE, but apparently I was wrong. This is very telling: http://gaming.stackexchange.com/questions/179412/are-there-any-command-line-arguments-for-origin Supposedly there's a method to launch games just like Steam. So it sounds like I have some work to do. If I can get at those game IDs somehow, I can build an automatic Origin import just like the Steam import and make it magically work. In the mean time, if you can figure out how to come up with those game IDs (per the above link), you could probably put something like this in the application path field: origin://launchgame/DR:235664700 And in theory, it *should* just work (though I have yet to test this in particular). Keep me updated if you have any luck with this or figure out if the IDs are stored somewhere on the machine, where I can parse them. Thanks, Jason

By the way, guys, 4.2 will (and the 4.2 betas already do) support nullDC and Project64 1.6 out of the box properly. I added an option to not add an extra space (for nullDC) and not use quotes (for PJ64 1.6).

Wow, I'm on my laptop, but I can't even get Turbo Engine to successfully go fullscreen. It crashes every time. I guess I'll try it on my desktop when I get home.

Great. It should be obvious for new users because it will automatically plug in proper settings for missing emulators. But I can see how existing users might be thrown for a loop. Wonder how we might mitigate that.

But yes, the other option is just to change the Emulator Name field. The name just has to be unique. But now that emulators support more than one platform with different command line parameters, you can just add one emulator with different platforms and it'll run the right command line parameters depending on the platform of the game.

Ah, yes, that's because it expects you to add two different platforms to the *same* emulator instead of two completely different emulators. You can specify different command line parameters for different platforms, even when using the same emulator.

ps4isthefuture said Hi everyone, Just wondering if anyone is using Turbo Engine to emulate the TG16. Command-line --fullscreen works fine but I'm getting some serious background clipping from LaunchBox. If I Alt+Enter out of fullscreen and back into fullscreen the issue goes away. It's only present when launched from LaunchBox. Anyone know of a command-line to solve this? Running Win 7 Ult 64 just incase that might matter. So if you like Jason you can add Turbo Engine for NEC Turbo Grafx 16, --fullscreen, zip. I haven't looked to see what other files it will run, I would assume the same as the other TG16 emulator though. Update 1: Some games, like R-Type, will start the background clipping again when the game switches to demo mode and also when it returns to the title screen. Just a little info to maybe help. That's interesting. I'll see if I can get that emulator working. I wonder if minimizing LaunchBox before launching the game would fix the problem...

Duckeenie, can you explain what you mean by "no way to use an emulator for more than one set of ROMs"? Emulators support multiple platforms and can apply to any ROMs you want. I don't understand what you mean.

Alright, beta 2 is out: https://bitbucket.org/jasondavidcarr/launchbox-nightlies Fixed a bunch of things, added support for problem child emulators like Project64 1.6 and nullDC, added more automatic emulator settings, tweaked the interface, etc. I'm hoping no news is good news?

Yeah, I'm settling not to include any emulators. There's just too many of them. I'm including download links to make it easy. I've messed around with Retroarch, and yeah, it doesn't look like it would work or be a good idea to auto-configure it. It just has too many options, and I know too little about how it all works. The maths question...first time I've heard or seen that. But, odd. You got in though?

Got it fixed; I should have a new beta up tonight. I was attempting to not duplicate results between the LocalDB and TheGamesDB, but the results were confusing and I'm not sure it was working right anyways.

Ah, wow. Good find. Will fix for 4.2.

I've figured this out; LaunchBox puts a space in between the file name and the command line parameters, which works for pretty much every other emulator, except, of course, for this one because of the =. I'm going to try and add an option to support it for 4.2.

Welcome Duckeenie, yes, right now that isn't easy to do. Glad you were able to search and replace in the XML. If you keep LaunchBox next to your ROM files (or put your ROM files somewhere inside of your LaunchBox folder), you can move the whole thing anywhere you need without it messing anything up. But of course right now I haven't yet added a tool to auto-update all of the paths. This is planned. Thanks, Jason

Most definitely; big thanks to bd for his work on this post. As I had previously promised, I've finally started to integrate these settings into LaunchBox itself (so they automatically populate and such). I just put out version 4.2-beta-1 ( https://bitbucket.org/jasondavidcarr/launchbox-nightlies ) which includes settings for a handful of them. I'm adding them slowly in because I'm testing them one-by-one.

Thanks, Conehead; I'll take a look at that error. In the mean time, I just released 4.2-beta-1: https://bitbucket.org/jasondavidcarr/launchbox-nightlies As always, any testing is much appreciated. Here is the changelog: - New Premium Feature: Game counts can now be added to the sidebar from the Options dialog (with the option to align right if desired) - New Feature: "All", "(None)", and "(Exists)" side bar items can now be hidden, shown, or renamed in the Options dialog; "(None)" and "(Exists)" are now hidden by default - New Feature: New Manage Emulators option is available under the Tools menu - New Feature: LaunchBox now automatically knows proper configurations for select emulators and can automatically suggest emulators and settings for various platforms - Improvement: Emulators now support multiple platforms with different command-line parameters for each platform - Improvement: Emulator command-line parameters can now be set per emulator, per platform, or per game - Improvement: The search box can now be accessed using Ctrl+F; the shortcut for fullscreen is now F11 - Improvement: The search box no longer flickers - Improvement: Empty folders are now added in export packages - Fixed: Touch screen swiping now works with the new themes - Fixed: Side bar scrollbar wasn't showing up or hiding in some cases when adding or removing games - Fixed: Side bar was in some cases not showing items until scrolling after changing filter types

Hi weshollet, I haven't used NullDC as of yet, but you can try putting something like this in your command line parameters: -config ImageReader:defaultImage= LaunchBox automatically adds the ROM file path to the end of the parameters, so hopefully that will work. Do let us know. Also, it's worth noting that there's a list of configurations here: https://www.launchbox-app.com/forum/emulation/command-line-parameters-arguments

Yup, on my short list.

Another way to do it would be to use an AutoHotKey script. I have plans to integrate AutoHotKey into LaunchBox sometime soon, but you could still do it manually for now. AutoHotKey can check for any combination of controller buttons, and then perform an action like do a keyboard combination (Alt+F4 should close pretty much anything). An automated solution for that is coming...

Hey folks, I'm looking to simplify emulation for LaunchBox 4.2. In the very least, I'd like to include this list of settings within LaunchBox so that you can choose an emulator and have it automatically use the right settings. That said, it might be nice if I could include emulators for some platforms out of the box. I'd love to hear feedback on everyone's thoughts regarding this and what emulators they might suggest. I've looked into possibly including a multi-platform emulator like RetroArch or MESS but I have very little experience with them, and I'm not sure if that would be a good idea or not. Open to any and all ideas. The primary goal I have is to make emulation with LaunchBox as easy as possible, while allowing for customization where needed. Thanks, Jason

Great idea; added to my to dos.

Yup, no kidding. I hear you there. I just can't resist the shiny.