Jason Carr

Don't worry, we'll be getting another one that's pretty much exactly the same (with a few improvements). This was very much worth it for us to do because of the additional exposure we're gonna get.

Hi @Eirulan, this is really just an issue with the data that came over from thegamesdb.net for that particular game. Yes, if it gets fixed in the database, emptying out the notes field should fetch the new notes using the update metadata wizard.

Hi @krunchmuffin, the Rocket Launcher guys will have a new version out shortly to fix this issue.

This one has been very hard to pinpoint, as it does not seem to be affecting everyone, and I have not been able to replicate it. Any details you guys can provide as to what games it's happening with would be appreciated. Also what fields or images are missing, etc. Specific games with specific details would be helpful, including the ROM's file name.

Thank you @Wattoo; I'll get the translation in when I get back next week. @ounaazh I can certainly get you premium if you want to do the translation, no problem. It will take me a bit to get a translation package out to you, but hopefully I can get that to you next week.

Sadly not at this point, James. We're still working on adding features like that. But no worries, it should most likely get refused by the moderators.

Thanks all. I'll be back into development on Monday with the live stream. @wallmachine and @Kriven I'll look into those bugs then as well. @Lmagnus87 I'll be looking into the possibility of adding it to the Windows store but at this point I'm not sure. We'll have to see what the requirements are and such. @wallmachine That logo issue probably has to do with the math I had to fudge a tiny bit in order to prevent the ugly lines from appearing under the images. An easy fix should be just to add a pixel or two of empty padding to the image itself. I can get back to it to tweak it a little though too; we probably just need to change the numbers a bit.

I use CrashPlan for everything currently, and I highly recommend it. They will encrypt all your files with your password, and supposedly they don't even have access to them. I've been using them for 5 years and never had any issues at all. Not to mention they've saved me from hard drive failures many times. I've literally uploaded (and downloaded) over 25 TB to their servers.

Hi master, this is because when you downgraded it went back to using your old LaunchBox.xml file. Just delete your LaunchBox\Data folder and restart LaunchBox and you should be good.

Thanks monkus. This is always helpful.

Hi @andyco47, the Rocket Launcher stuff should continue to work so long as you leave the old LaunchBox.xml in your LaunchBox folder. However, with the new release, any changes you make won't be reflected in the old XML file so they also won't be reflected in Rocket Launcher.

Hi @wize, go to Tools > Manage Platforms in LaunchBox. Then manage the platform and add the image as a clear logo. Then you may have to go into the Big Box options to refresh the platform logos under Image Cache.

Awesome, no problem @Thordelan. LaunchBox Big Box Custom Themes Documentation.docx

Hi @ZedSpot, there's a separate CustomField section that contains this data. Search for <CustomField> and you should find it I think.

Went ahead with the official 6.10 release guys because I needed to get it out before I leave for Retropalooza tomorrow. Thanks for that error report @Sithel; I expect that's mostly a fluke (it's the type of error that really should never happen and likely has more to do with a .NET glitch than anything else, but who knows). Let me know if you keep seeing that. @ckp It's possible we have a remove image glitch, but it's not widespread. I've tested and can't seem to reproduce the problem. If you keep seeing it, let me know the file names of the images specifically so I can troubleshoot. 512 MB should be plenty big for the RAM cache setting. It is normal for images to pop in a split second after scrolling to them with the new version, at least the first time the images are loaded after restarting LaunchBox. It's a trade off for basically improving the responsiveness of everything in general. We can come back to this at some point, though. Things can always be improved. Thanks guys; let me know if anyone sees any issues with the official release.

Congrats @Wattoo! Take your time and enjoy your family. I just put out the official 6.10 release so no rush at all at this point.

@nyny77 That would be up to the individual translators. I can provide the Word document if anyone would like to translate the theme documentation PDF file.

Thank you @AFaustini and @dukeemu; I have all the translation changes ready for the official release. I'm just about to put it out here.

Not that I know of unfortunately. I suppose it might be possible to trick the interface into using a folder, but I doubt it. I think most likely we'll need to make some code changes in order to support opening a folder for the ROM.

Good point. Only problem with that though is we'll be back to some of the exact same issues because people won't know how to use it properly out of the box. Though it would fix the issue for Lightspeed.

Yes, it does sound like the best solution for the future here would be to allow you to add additional folders to parse without changing the default folder that is used for saving. That complicates a lot of things (I cringe at the thought of how the platform folders dialog is going to look), but I agree that that would be a good thing to add. Good thinking @Johnnydement.

Thanks @Antropus. Put some major work into performance for these betas. @ckp It used to just delay the scrolling instead, so I think this is a better solution. Try increasing your RAM cache.

@Maddoc1007 On the File Actions dropdown at the bottom of the download page there should be an option to "upload a new version". Let me know if you have any issues there. @shinra358 Good to hear about the wheels. Unfortunately caching background images wouldn't help much with anything. The reason why it's effective to cache the wheel images and stuff like that is that they can be large images and they're resized down to a smaller cache size to make them load and render more quickly. When it comes to background images, though, the full resolution of the images is typically required so it wouldn't provide any benefit to cache those. @Sithel Good find on that. I'll get that fixed before the release tomorrow. @WolfRamiO Are you saying it's scrolling too quickly when you move with the joystick? We could allow you to adjust the scrolling speed for that; can you create a ticket for it? @AFaustini Looks like we must be missing that. I'll add it to my list. Thanks all, I did just put out a new beta that adds some additional performance tweaks to the LaunchBox image caching stuff, as well as fixes two issues: - Fixed: Paths were not being saved relatively when importing games and copying or moving files - Fixed: Games and platforms in the CoverFlow and wheel views in Big Box can now be selected with the mouse

Thanks @SpaceMidget75, agreed on all points. When you add images in the Add/Edit dialog they are indeed copied. The originals are left in place.

There are unfortunately other issues here with setting LaunchBox image folders to locations that shouldn't be modified. Any time LaunchBox downloads new images of course they're added to the folder, or any time a user removes an image it's deleted from the folder, etc. I can understand the confusion though; perhaps we should make it clear that you shouldn't set your LaunchBox image folders to locations that you don't want LaunchBox to manage. We've run into similar issues with people using the same image folders between various frontends, and we did add a workaround so that files weren't unnecessarily renamed, but at some point LaunchBox needs its own image folders that it can actually write to. If LaunchBox can't change the images in those folders, then it can't change users' collections, so not allowing images to be deleted is really not an option here. The only solution would be to copy files to the folders instead of expecting that users will never modify the images in their collections.