Jason Carr

Thanks guys; I have this fixed for the next beta. Hoping to put it out later today.

I think originally things were implemented this way because the Notes field was sometimes used for manual Notes, and folks didn't want it overwritten. If you clear out that field and then scrape it again, you should get the notes from the database. Per the star rating, I *think* it will update the community rating, but perhaps not the user's rating.

Believe it or not, I haven't heard of anyone really trying it yet (and I don't really want to jailbreak my own Switch at the moment). So sadly, I don't have any news on this yet. That said, if it runs Android and has access to the Play Store, I see no reason why it wouldn't work.

@g0d53nd Ugh, it looks like either Windows is messed up in the way that it communicates with your phone, or your phone is messed up, one of the two. I haven't seen that before, unfortunately. If you have another computer available to you, you might try that. I'm really not sure how that functionality would get messed up. You might try rebooting both your PC and your phone to see if that makes any difference.

Key bindings are currently not available in LaunchBox. LaunchBox is designed to follow standard Windows keyboard and mouse control; we've never added customizable keyboard shortcuts or keyboard navigation in LaunchBox itself. I'll add it to my list of items for the next community poll, although I don't think that request has received much attention in the past. LaunchBox does not use settings from BigBoxSettings.xml. The LaunchBox settings are all in Settings.xml.

Okay, so obviously it's picking up clear logos (at least that one). Try going to Options > Image Cache > Refresh All Images in Big Box just to confirm that it's not an image caching issue. Beyond that, I would think that it must be a video driver issue. Can you try updating to the latest video drivers available?

Thank you guys; yes, that does look like a corrupted installation of .NET. @greggo Let us know if repairing .NET (per the above) fixes the issue for you.

@lukeymundo This must be either a configuration issue, or a some sort of a video driver issue, I'm guessing. If you edit your platforms in LaunchBox, do clear logos show up for them here?

Hi guys, sorry for the trouble. Most likely this was caused by a stray game controller of some sort. The easiest thing to do would be to reset the LaunchBox settings by deleting the LaunchBox\Data\Settings.xml file. However, you'll lose your LaunchBox settings that way (you won't lose any data though). Otherwise, you'll have to edit the Settings.xml file to remove the window sizing settings.

@dov_EL That can be fixed by adjusting the startup screen timing settings in the emulator settings.

I haven't really come up with a solution yet. I still haven't figured out what on earth Retroarch is doing in that regard, or how it could be a new issue. I do plan to look into it soon.

Oh, ha. I didn't realize the Quest was for Android. That's a better answer than I could give. Thanks @neil9000.

@arzoo I did change the controller mappings code for the latest releases; I'm sorry I didn't give you any warning for that. I hadn't considered it, since my controller board uses keyboard mappings instead of controller mappings. Anyways, for existing users the mappings will stay in the previous settings file, but they unfortunately won't be updated when changes are made, and won't be used for new users. There's a new InputBindings.xml file that shows up with the latest version of LaunchBox and Big Box. The syntax of it should be fairly obvious. Basically, in order to support both new and old versions of LaunchBox, LEDBlinky should look for that InputBindings.xml file, and if it exists, use it. Otherwise, it should use the existing logic inside of the Settings.xml (for LaunchBox) and BigBoxSettings.xml (for Big Box) files. Let me know if you have any questions and I'll help with whatever is needed. Again, sorry for the late notice on that.

Thank you @alexposad. I have this integrated for the next beta.

Screenshot Title and Screenshot Gameplay already exist. What do you mean by a "Versus" folder for games of the fighting genre? I believe we've had a Maps, etc. field on previous polls, but I'm not positive. I'll add that to my ideas list for the next poll. Additional apps should work well enough for that currently though.

Hi @Thornback, I've confirmed that nothing has changed in the code either in the theme or in Big Box, but I do faintly remember someone else reporting this a while back (I think). @CriticalCid and I have tested this and neither of us are seeing this issue on our machines, and it doesn't seem to be related to DPI. I know video drivers can be an issue for stuff like this, so I would recommend trying to update your video drivers. Other than that, I'm pretty much out of ideas.

Hi @d8thstar, I've previously used Big Box via the original Oculus, but I haven't tested anything with the new Quest. But technically, anything should be able to run in a virtual environment. If you use a controller, you should be good to go as far as I know.

You mean Kodi on Android? I assume Kodi on Android provides some mechanism to launch external applications. Or did you want to launch Kodi from LaunchBox?

Unbroken Software is hiring! We are looking to fill a full-time software developer position. The applicant will be working on LaunchBox, Big Box, Music Box Alpha, and/or LaunchBox for Android applications, as well as any future applications that we may build, all of which are written in C#. Details are below: Full-time six months contract-to-hire, with the goal of it turning into a permanent full-time position At least 3 years of professional experience with C# software development required Examples of written C# code will be required Local to (or willing to relocate to) Modesto, CA is a plus Experience with ASP.NET MVC, WPF, and/or Xamarin is a plus Experience with LaunchBox and/or emulators is a plus People skills are a plus College degree not required (we don't care either way) Time frame is flexible, but we are looking for a candidate ASAP Depending on the candidates that we receive, we may reach out to headhunters, but we wanted to give the LaunchBox community the first opportunity. If you're interested, send your cover letter and resume to support@unbrokensoftware.com; we will reach out to candidates that we are interested in. Thank you very much! We look forward to hearing from you.

We may indeed have an issue with multiple XInput controllers. I'll be reviewing that here soon. Sorry for the trouble. Hi Terminates, this is one issue that I haven't figured out. Button combinations are working in all my testing for Retroarch in 10.5. What buttons have you assigned to exit and what controllers are you using?

Odd, what browser are you using? I just tested that URL in Chrome and Firefox and it works fine for me.

Hi @nullNOVA, did you have any controller issues before the latest releases? Was it working properly with 10.1? Issues like this that I've seen elsewhere seem to have been related to BlueTooth. Do you have these issues if you try plugging in your controller with a USB cable? I'm trying to get to the bottom of this stuff.

Thanks for sending me your data folder @Tinker. I'm not sure how this could happen outside of manual tinkering, but I do see the issue here. LaunchBox expects that all the files in the LaunchBox\Data\Platforms folder are named with a proper platform name, and that every game that is listed inside of that XML file has the exact same platform name. For whatever reason, I'm finding games in your XML files where the name of the platform tag (for example "Arcade Classics") does not match the name of the XML file (for example "Arcade Shoot 'Em ups.xml"). That mismatched platform name is likely to cause a bunch of issues. I can only assume that this must have happened by manually copying and/or renaming files in the Platforms folder. As far as fixing it, your best bet is to rename the files back to match the platform tag that is listed on the games, and/or delete the files that have that issue.

Sorry for the lack of responses here, but generally people aren't quick to respond to posts that report issues but don't give any relevant information.

Hi xtopher, let's try and figure this out one system/core at a time. Let us know what cores you're trying and what isn't working. The first step would be to try manually loading up a rom for that core without LaunchBox to see if the issue is just that Retroarch isn't working for that core or rom file. You could also need bios files for certain cores. Generally, if you're seeing a black screen on startup with Retroarch, it means something isn't working with that core for Retroarch, and not likely an issue with LaunchBox.