Jason Carr

Great to hear.

I can't explain why it would have been working before the update, to be honest, other than maybe game controllers got switched on or something. The xinput library is used for game controllers. It's not necessary to run the setup on the other computer as well, only on the one that is having issues. Also, if you're worried about not updating your LaunchBox installation, you can just install to a different folder and then delete it.

Oh, also, no, reinstalling will never overwrite any games or settings.

This is happening specifically because LaunchBox is synced to different computers without installation, which is normal, but unfortunately certain DirectX libraries are required. Users get this message when those DirectX libraries are missing. LaunchBox is not causing DirectX issues; it's simply saying it needs some missing libraries. Re-running the setup program on the computer should fix the issue.

Thanks @Opaklopper; I'll get the update into a beta on Monday probably. @sfn103, that's interesting. Which do you know the best? I'm surprised there's no option for Classical Arabic in the .NET language codes.

Yeah, it didn't really make much sense because the texture was exactly the same size as the object it was being painted on. But ultimately I just had to make the texture a pixel or two larger than the object, which was a trick in itself since I first had to figure out how to stop it from automatically resizing the texture to match the object. Basically we were letting .NET handle too much without explicitly declaring enough of the rendering logic. I still think it was a .NET glitch in that the previous approach should have worked just fine, but thankfully I was able to get around it with some explicit code.

It was something like a math rounding error with the rendering of the wheel. It was actually a real pain to figure out and fix, and looking at the math it *shouldn't* have been an issue. But I ultimately had to fudge the math behind the painting to overlap the drawing by a pixel or two in order to prevent it.

New beta is out guys that fixes some additional issues with changing the platform on games. These issues were new and were introduced with the XML split changes. Game and platform changes in general could use some additional testing because we've found a number of things that weren't saving properly due to the XML split. I think I've caught them all but only time will tell.

@dukeemu I also finally updated your translation files in the latest beta. Per the splash page not being translated, we'll need to manually translate those things. I typically ask for those translations before each new version, so for the next version I'll have you translate all that text and then I can update. The splash screen text is actually not in the translation packages. Per those items in the View menu, those are actually not translated currently, which I know isn't ideal. I did it that way to avoid confusion with folder structures and such. I plan to come back to that eventually, but for now, that stuff is just always in English in order to match the LaunchBox Games Database. I did also fix the overlapping issue in the Sidebar tab of the Options form. Just let me know if there are more of those issues; they're actually pretty easy to fix. I just need to know where they are is all. Thanks again.

@audunv @Wutex I have new translation packages finally available for you guys. Again, so sorry for the delays and thank you very much for all the help. See the first post in this thread for details. New translation packages are available at the end of the first post on this thread. Also, do please read the first and second posts of this thread in their entirety as there are a couple of gotchas that we'll want to avoid before you guys get started. Thanks so much.

Yeah, I've certainly done a lot of optimizations, but there's always more to be done. For example, the games dictionary is keyed by the game ID. Since you can filter and sort by so many different fields, like platform, developer, etc., we still have to loop through every single game to find matches. So that's really the biggest issue...ideally I would make the code behave more like a proper database with key maps, yup. It's all about avoiding looping through everything. At least that's my thought process.

Thanks @Nielk1. We actually do not use an in-memory XML structure. We use custom classes (strongly typed objects), dictionaries with unique identifiers, etc. So in that sense things should be relatively quick. We also do a number of things in backend threads (such as saving), but if you're searching games to populate a list for the user, then obviously a separate thread isn't going to speed anything up. Admittedly though I'm sure there are places that could still indeed use a separate thread. I'm sure there's also algorithms that could be improved upon for the searching mechanisms; we just have to get there.

That sounds awesome though; that's sorely needed. I'll look forward to that!

No we actually don't. The RocketLauncher guys plan to have a new version out shortly I think that works with the new format. LEDBlinky is less of an issue because it already works fine so long as you choose BigBoxSettings.xml in their settings instead of LaunchBox.xml. Arzoo is also working on a new version though, so I don't expect this will be an issue for long.

Thanks @audunv and @flores9. I'll work on getting the Japanese and Norwegian translation packages out now at least. @flores9, that makes sense; I'll add that to my list. Like I said I still need to do some testing/research so it may be a bit yet but we'll get there eventually.

Unless you're using RocketLauncher or LEDBlinky. They both are currently referring to it.

We should create another thread and talk with @Rincewind to see if we can figure out why it's working for him. Sadly I'm going to have to break from this for a bit because I need to get some more stuff out before we leave for Retropalooza next week.

I would hold off on this until we put out the official version (and then I would *still* hold onto a backup copy), but yes, it is no longer used for the betas.

@Maddoc1007 Unfortunately I would need to see the entire XAML in order to help you out there. Can you create a separate thread for that? @martinconroy, I'm gonna go jump off a bridge. Seriously though, I'm clueless at this point. I'm forcing it to use en-US; perhaps something isn't installed that it needs? Any luck for you @orac31? Thanks @imdavid555.

Yeah, we'd probably use SQLite. But yes, it is a ways out and not likely to happen soon.

Hmm...are you using the latest betas? Sounds like we might have a glitch there that I need to look into... We split up the XML recently and are still ironing some things out.

When we do add database support, it will be optional and will not be the default. Access also is not at all a good option because Access would not improve performance. Keep in mind that if we changed it to a database, RocketLauncher integration and LEDBlinky integration would both break, on top of quite a few other integrations I expect. XML is an enabler.

@ckp, multiple threads and cores are used for various things, but when it comes to switching between platforms it does come down to one thread for the majority of it. It's never as simple as "oh I have four cores so it's only pegged if it's at 25%" though. There's hyperthreading and other things that are involved there.

Actually, yes, a proper database backend would likely improve performance, and yes, it is planned for eventually.

@sfn103 @Wutex @audunv So sorry for the delays on those translation packages. I'm finally getting them ready. Unfortunately though there are lots of options for the Arabic translation, and a couple different options for the Norwegian. @audunv, which of these two are what you speak for your native tongue? nb-NO Norwegian (Bokmål) - Norway 0x0414 nn-NO Norwegian (Nynorsk) - Norway 0x0814 @sfn103, which of these is what you speak? ar-DZ Arabic - Algeria 0x1401 ARG ar-BH Arabic - Bahrain 0x3C01 ARH ar-EG Arabic - Egypt 0x0C01 ARE ar-IQ Arabic - Iraq 0x0801 ARI ar-JO Arabic - Jordan 0x2C01 ARJ ar-KW Arabic - Kuwait 0x3401 ARK ar-LB Arabic - Lebanon 0x3001 ARB ar-LY Arabic - Libya 0x1001 ARL ar-MA Arabic - Morocco 0x1801 ARM ar-OM Arabic - Oman 0x2001 ARO ar-QA Arabic - Qatar 0x4001 ARQ ar-SA Arabic - Saudi Arabia 0x0401 ARA ar-SY Arabic - Syria 0x2801 ARS ar-TN Arabic - Tunisia 0x1C01 ART ar-AE Arabic - United Arab Emirates 0x3801 ARU ar-YE Arabic - Yemen 0x2401 ARY Keep in mind that we can label the language without the country code if that makes the most sense, but it is best to choose the correct one from the start before beginning the translation. Thanks.