paladin181

I see that. GOG Galaxy 2.0 is really nice, at least in theory. In practice it's still a broken mess, and given their track record for actually making working software, I was hoping for this or another front end launcher like to make a difference. Feel free to take out the spoilered info if it's against the rules to mention other launchers like this one. I love Launchbox (it's why I bought the license) but the community seems to be going a different direction from me.

GOG support please!! Not to mention Origin, Uplay, Bethesda, Battle.net, and Epic...

allan_rex92 said Hey thanks for the reply... I Even tried the Emulator Link that you gave, its still giving me the same error. And to answer your question i'm currently using VBA-Link :- http://www.vbalink.info/download-gba-emulator.htm I Specifically need to use this emulator cuz i wanna play the game Legend of Zelda - Four Swords(GBC), and this game required atleast 2 players to play, so i need to use the 'Link' function under the options so i can open 2 windows of VBA-Link and link them with eachother for two player game play. Can you run the game on the emulator outside of Launchbox?

Jason Carr said Lol, nope, don't mind at all! Details are good and help me solve the problem. I understand how some devs get pretty worn out taking feedback from users, but in all honesty I'm just tickled pink to have so many great users. This is what I loathe, however: DAMMIT, YOUR APP DOESN'T WORK Gee, thanks. I'll totally fix that. Yes, I get those emails. And spreading the word of LaunchBox is always appreciated! Thanks Kamyk! I'm constantly advocating this product because it works. It is truly a great way to manage a library. I'm currently adding all my games from Steam and GoG to it, with the installers linked as "Additional programs" and it's working well so far. Due to a few limitations, I'm using the favorite marker as an "Installed" marker. Works pretty well with the custom filters. Maybe an option to add custom fields or to be able to filter by "NOT" having a specific text in a field would be ok.

kamyk2000 said Was trying to add to the previous reply so I didn't doublepost, sorry. Thank you for the welcome, and the reply Here's what I was typing about what I found out. -------------------------------------------------------------- Ok, I just saw in my emulator settings that every Emulator listed in Launchbox has something similar to "-L "cores\desmume_libretro.dll" set as a default command line parameters in the edit emulator settings window. IMAGE REMOVED TO CONSERVE SPACE They all seem to be command lines relating to cores in RetroArch. I have no idea if they were inserted when I added RetroArch, or if they were all set like that from when I installed Launchbox, and I have no clue if those entries are supposed to be there, but every emulator listed (that I added or not) has them. And guess what happens when I delete that line for the Nintendo DS entry? Suddenly No$GBA works, and even works if I set No$Zoomer as the default start program. Imagine that. I discovered this because I just added my GBA roms, and VisualBoyAdvance emulator, and it wouldn't run either. It kept telling me "File type -L invalid" and I couldn't figure out what the heck it was talking about. It certainly didn't get any "-L" from my input. So I looked in the edit emulators again, and I found those command lines. Removing the one for Nintendo Game Boy Advance made all my .gba roms work, so I removed it from my Nintendo DS entry too. So, problem solved. However, what I still need to know from the Dev or someone is are those entries supposed to be there? Were they installed when I installed Launchbox? I have added and fiddled with hundreds of roms metadata at this point, and I'm certainly not going to uninstall the program and then reinstall it to find out, but I also don't want to just arbitrarily remove those entries from every "default command line" if they shouldn't be removed. I'd imagine they were added with RetroArch, as I've not experienced this issue and I've fully removed RetroArch without successfully using it due to the interface. I have no entries under any of my Emulators that correspond to cores\xxxx_libertro.dll. Searching "libretro.dll" on google pulls up RetroArch pages. So that's a pretty safe assumption. I'd say remove them from everything since you are not using RetroArch anymore.

I use DeSmuME and No$GBA for different functions (NDS and GBA games) and I have absolutely no issues with them. A few questions: What operating system are you using? What version of LaunchBox? What are the extensions of the files you are trying to load? Can you load the games outside of Launchbox with either DeSmuME or No$GBA? I believe I started using DeSmuME because No$GBA didn't want to work right for me in Launchbox (for the NDS games, it works like a charm for GBA games), but I'm not really 100% certain anymore as I set this up quite a while ago. It may be because I couldn't get No$Zoomer to work right through Launchbox for NDS games, now that I think on it. I don't have any special parameters set up in my Emulator config, or individual game configs either. I hope you find some of this information useful.

Jason: Thanks for the prompt response. The only error message I get is a Windows message "Launchbox has stopped working." The program shuts down completely and must be restarted. I just attempted to get a failure for the exact error message (searching for troubleshooting info, etc) but it did not fail. This indicates to me that it is not a 100% failure and may not be exactly what I initially thought it was.

For future reference, to remove a platform, you simply have to remove every item tied to that platform, or change their platform to something else.

OS: Windows 7 Ultimate (x64) Version: LaunchBox Version 4.6 Premium Issue: When right clicking a game where the launcher or additional apps are located on my external drive, if the drive has gone into sleep mode and needs time to access, the action crashes LaunchBox. The device is a Seagate Free Agent 1TB USB external HDD. Would it be possible to get a timeout extension on requests to devices like this before crashing the app? It's not a huge deal; once the drive wakes up LaunchBox can read from it normally and can access any title with a file located on the device. It is an inconvenience however should I forget to click on it elsewhere to wake it up.