Jason Carr

This is probably a very long way off. Thanks @alfredolvera. Looking into it.

Thanks for the reminder @bundangdon. Both of those things are indeed missing. I'll see what I can do.

Lol, unfortunately it's not quite that easy. But that does make sense. Probably won't make it into 7.15 though.

As much as I know there are a handful of very vocal users who really, really, really want that feature, at this point I still don't think it's all that common of a request. It is by far and large the biggest and most difficult task to accomplish of anything I have on my list, so I don't want to just jump into it until we at least put it onto another poll to confirm whether or not it's really a popular request.

Good to know @Styphelus; I'll look into it.

Beta 7 is out now guys; it should fix the bug(s) mentioned above. Here's the only other addition in this beta: - New Feature: Two new options have been added to Tools > Options > Search: "Use Community Star Ratings when Filtering or Arranging by Star Rating" and "Minimum number of community ratings in order to use". These will allow you to specify whether or not you want to use the community star ratings when filtering and arranging your collection, and how many community votes are required before considering the value. As far as I'm concerned, I think this provides all the added functionality and flexibility that most people will want in LaunchBox for the community ratings, so I'm planning to move on to Big Box next, which still needs all the community rating stuff. If, after trying the new beta, there's still a feature that you feel like you're missing, please let me know. No guarantees as to what will make it into the next official release, but I do need to know if there's a glaring omission. Let me know if you guys run into any further bugs as well. Thanks as always.

@y2guru I don't believe I did. Still on my plate.

Hey guys, I'll need a lot more details in order to troubleshoot this, including specific games and what fields are missing or not updated. I can't figure out any issues unless I have specific information there. It's also important to note that LaunchBox will download updated information from the games database only once a day, so you don't always get the very latest changes when downloading metadata.

@millah22 Unfortunately it will probably be a while before we add support for a third monitor, just because we have many more popular requests to implement first. I should have the new beta out later today, though.

@MartinC Can you send me a zipped package of the broken data? I'll need your entire LaunchBox\Data folder. That will help me pinpoint the issue. Please make sure to PM it to me instead of posting here to avoid privacy concerns.

LaunchBox does cache playlists on startup, so that must be what was taking so long. That part of the process is mostly CPU-dependent. Good to know that it was causing a major difference in startup times though. I might come back to re-address it.

Apologies, but nope, that's not on my to-do list. Yeah, I may do something about this if it's not too difficult before the next beta. Thanks Neil, just fixed this for the next beta.

You should be able to run the official version setup from the LaunchBox\Updates folder. Just install over top and everything should be fine. This has come up before; unfortunately .NET does not provide a good solution for that. Of course anything is possible, but I would have to reinvent the wheel in order to make it happen, so that's not likely to happen any time soon. There are certainly things that can be done, though, such as trapping all plugin errors and handling them separately, but that by definition won't catch everything.

Yeah, I've noticed that as well. It's irritating but I have no idea why it's happening or how to fix it. I'm guessing it's DirectX-related though.

As stated above, we figured out that this is caused by at least one plugin: the add to games database plugin. Please try removing all plugins and let me know if you still get any errors.

Okay, so I was finally able to reproduce this guys. Turns out it has to do with using a smaller resolution on your main monitor than the resolution used on your marquee monitor. Thankfully it was relatively easy to fix once I figured that out, so the next beta should have a fix for this.

Beta 6 is out now guys with the aforementioned bugfixes. Please let me know if there are any bugs or errors that remain in this new beta. Going forward, my goals are to get the community ratings stuff integrated into Big Box, and add community ratings into the missing relevant places in LaunchBox as well. So that's next. After that, we'll probably look to put out the official release.

I'm not sure if that's related to the latest beta or not, but that is indeed an error with that plugin. I'm not sure which one it is, @sagaopc. Can you contact the author?

Ah, so this *is* plugin-related. We'll need to talk to @UnderwoodNC to hopefully get this fixed for the new versions.

Sega Genesis is still broken in the retroachievements.org API. Scott over at retroachievements is working on a fix.

This one baffles me as I can't find code anywhere that would cause this. It's possible that it could be fixed with the same fix from above, but I'm slightly doubtful. Let me know @FistyDollars if you still get this after the next beta comes out in a bit. Also, do you have any plugins installed?

@Killerdog @alfredolvera I'm hoping this is fixed for the next beta, but I'm not 100% sure. Please let me know once the beta comes out shortly. It looks to be an issue with decimal number parsing because number format differences between different countries. I hope I've got it fixed though.

Also should be fixed for the next beta.

Thanks; fixed for the next beta as well.

Good catch. Turns out this was caused by the single quote in the title being converted to the HTML code for a single quote. Fixed for the next beta.