Jason Carr

I agree, guys, that would be pretty great. There are definitely plenty of UI improvements to be made. I'm going to make a "preview" view the priority here at this point, because obviously it's important to be able to view the metadata outside of the editor window. I do like the platform screen as well; ultimately I'd like to have the ability to do that with other things too, like developer, for instance. I'll start with platform though. That in particular will take some significant development though, so unfortunately this one won't likely be as fast coming, but we will head in that direction. Thank you both for your continued input; it's very helpful and appreciated.

Awesome! Any chance you could share the program you wrote?

Nice! And thanks for sharing your emulator settings!

Hey bd, sorry to hear and sorry for the delay in my response. Unfortunately it sounds like your LaunchBox.xml file must have gotten corrupted when the game crashed your system. Did you happen to have a backup of it? Running the install again over the top of your previous installation won't fix a corrupted LaunchBox.xml file. You'll need to either delete the LaunchBox.xml file or install into a new folder. Unfortunately, though, you'll probably have to start your collection over unless you have a backup of the LaunchBox.xml file. It'd probably be a good idea to have LaunchBox automatically make backups of that file; I'll look to add that feature.

Hi miles, thanks for the note. Yeah, I have batch edits like this on my to do list for sure. In the mean time, I'm not sure how comfortable you'd be editing the XML file, but you could open up the LaunchBox.xml (in your LaunchBox folder) file in a text editor and do a search and replace to batch fix the items. Just make sure you close LaunchBox and make a backup of the file before editing it, just in case something goes wrong.

Awesome, I'll plan it in for 2.17.

Wow, looks like Project64 1.6 uses a completely non-standard way to handle the file paths; they add quotes to them: http://www.pj64-emu.com/faqs/general/how-do-i-use-pj64-with-frontends-htpcs-arcade-or-cabinet-setups/ They changed this with version 1.7 (obviously because it was a bad choice to begin with; it breaks drag and drop functionality and isn't well supported by anything else either). So, hmm. I'll add a to-do to my list to allow not using quotes.

Thanks Draven! All good input; nit-picking is a good thing. I do have some major GUI improvements (such as these) planned out. I'm already pushing the limits of basic Windows graphics, though, so at some point I'm going to need to start doing things with DirectX, so I can implement better animation and the like. So that is definitely on my to-do list, but I do have a number of other more technical things to tackle before I can get there.

Hi death, I've been thinking about this one; probably the quickest way to get support for multi-disc games would be to allow you to use an emulator for the additional apps. That way you could right-click on the game and select "Play Disc 1" or "Play Disc 2". I'd just have to add a "Use Emulator" checkbox to the additional apps screen. How would that work? I can probably work that into the next version.

I think maybe I need to come up with a list of popular emulators and pre-populate these settings. Obviously most users aren't likely going to know how to configure them all properly. I'll add that to my list.

It looks like putting "-nogui -cdfile" into the command line parameters (without the quotes) does the trick.

Alright; I managed to get remember filters into version 2.16 that I just put out. Hopefully I can expand on it with a "kid mode" feature in the future.

Thanks bd00; that's a good idea. I had planned to implement that but for some reason I got sidetracked on it. I might be able to sneak it in to the new version that I plan to release tonight. Also, it's worth noting that I have a "kid mode" feature planned for development that would restrict games based on their ESRB Rating. I haven't started development on this yet though.

Sorry for the delay here Liam. If you can, use your keyboard to go to the Options dialog. What do you have selected for your joystick/gamepad?

Wow, looks awesome jtrain. That's a great idea. I'll look to see if I can implement some sort of collapse or nested option at some point here.

Awesome, glad to hear it.

Thanks, Martin, good idea. I added it to my list.

Just to update this forum post, with dreams' (and others') help I believe I've fixed the issue, should hopefully be putting out a new release tonight.

nmc, I think I've finally got this fixed; if you can, send me an email (just use feedback on the site) and I'll send you a test version so you can confirm that it works. I'll put out the new release tonight if we can get it confirmed. Thanks much for your help. Jason

Thanks nmc, I've narrowed the issue down to the new DirectX controller input. Still haven't figured out why it's erroring for everyone else and not me, but at least I have a lead. Can you tell me if you have SharpDX.dll and SharpDX.DirectInput.dll files in your LaunchBox folder?

Thanks, can you check your Windows Event Log to see if you have any errors in it that might be related? Go to Control Panel > Administrative Tools > Event Viewer > Windows Logs > Application and take a look at the list. It's a bit complicated but I'd really appreciate if you could see if you could find anything; I'm at a loss why everyone is experiencing errors at this point.

So I hear. Can you screenshot me or give me any more details? Don't understand what's going on at this point.

Bah, you're not the only one. I don't understand yet what's going on; I haven't been able to get it to crash myself. Can you screenshot me or give me any kind of details that you have? For now, I've reverted the downloads on the site back to 2.14. To fix it for now, you can download the setup and install over top.

Also, does it happen on a new installation? You can go download version 2.14 from the site and install it over top and things should work properly again.

Bah, I've reverted the downloads back to 2.14. Can you send me screenshots of what's going on? I'm confused because it's not crashing for me.