Jason Carr

Hi Toast, in general, I am trying to avoid distribution of old versions, because LaunchBox has been developed so quickly and there have been plenty of versions out that have had so many issues. Really, though, the latest versions of LaunchBox should actually be faster and use less RAM if configured properly. Have you tried using the latest and turning off the RAM cache under Tools > Options > RAM Cache? Also, using default Windows styles might help some too. Per the "not officially supported" thing, I believe the only stuff that doesn't work on XP are the wizards, as they use Vista+ controls. So I would still very much recommend using the latest release, and just turning off the RAM cache. If you still have performance issues and feel like it was faster and used less RAM with the 2.x releases, then something isn't right. The 2.x releases were pretty wasteful with resources, especially RAM.

This should have nothing to do with premium, but could be a glitch with 4.2. Hmm, maybe because Amiga is an emulated platform it's clearing it out to use an emulator instead? Does it work to use an emulator with 4.2?

Martini, I just put out a beta release that should at least help the issue. If you would, please go to Tools > Options > General > Updates and check the box to enable updates to beta releases. Then you should be prompted to update on restart. Can you test it for me and let me know how well it works for you now? Thanks, Jason

Hi Martini, good to know. I'll see if there's anything I can do to speed it up.

Ah, I see, yeah. That'd be a challenge.

Not necessarily...those images wouldn't be that big (could distribute platform images with LaunchBox). We'd most likely allow the user to customize them too.

Very nice, arcade. At some point I would like to add icons to the platforms.

Thanks, Duck. Wish there was something I could do to get past that, but alas, it's a hopeless battle. Anti-virus software is a virus in itself. I would recommend using Microsoft Security Essentials (free I believe with Windows), though I haven't used it in a long while.

Thanks, gotcha. Unfortunately there's nothing I can do about these false positives. Anti-virus software is known for being a virus in itself and crippling legitimate applications for little to no reason. I might recommend using Microsoft Security Essentials instead; though I haven't used it in a while, it is known for not being as much of a problem.

Hi martini, not as of yet. Though this feature is planned and is priority for the moment. I hope to add it very soon (batch downloading images and data).

Hi Franz, you're right. Ideally the size of height of the artwork would auto-adjust. Part of the issue is that you don't always view one platform at a time (sometimes games are mixed together), so it's a bit of a challenge to implement. That said I think I could do better than what we have. I'll add it to my to-do list. Thanks, Jason

Hi Franz, welcome, and thank you very much for the purchase. Per the window sizing issue, I think Brad is probably right; it has to do with an improper shutdown. I'll look to see if there's anything I can do to fix that. Per your license name, that is good to know. It's possible that there's an issue in communicating the name via PayPal. If you would, tell me your real name, and I'll send you a proper license. Thanks, Jason

Hi SuperPat, that is a good idea. I'll add that to my to-do list. Thanks, Jason

Hi HMKeele, if you populate the Application Path field for the game, DOSBox does, in fact, ignore anything in the autoexec section. However, the solution is to simply leave the Application Path field blank, and then manually start the game in the autoexec, after you run your other custom commands. The dosbox.conf file is used properly, but if a game is specified the autoexec section is specifically ignored. Hope that helps.

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.