Jason Carr

Thank you all; I have these translations all updated for the next beta.

I've addressed this recently; there is no documentation on how to properly launch Damon PS2, and I haven't been able to figure it out. Nothing is working for me, and Google searches give me nothing as well. I think we're going to have to reach out to the developer if we have any hope for getting it figured out. Feel free to reach out yourself if you'd like to. Yeah, I'm definitely planning on it. I should have a new version out soon with MAME support, although it may be rough around the edges due to Android often requiring specific old MAME sets.

Hmm, that image file extension is .png.gif, which definitely raises red flags. Is it just gif images that aren't displayed? Gif is a pretty terrible choice for a screenshot.

Yeah, that's puzzling. It doesn't make any sense why restarting LaunchBox and DS4Windows wouldn't fix the issue. I still believe it's a glitch with DS4Windows, but I can't prove that, and I also have no idea where to look to get that resolved. Regardless, PS4 controllers will work in LaunchBox even without DS4Windows, just by selecting the "Wireless Controller" option that shows up (at least when plugged in, I haven't tested that one over BlueTooth). I've looked into this several times before, and I've never been able to replicate it. Can you test to see if it has anything to do with the Region of the image?

We've actually had a wiki before, but it just never really got filled with content, so I ended up just getting rid of it. The problem there is that it would need to be filled with info by folks who are knowledgeable about everything. So if you're just learning theming, you'd have a long way to go before you could fill it with that content. I may create a wiki though here soon, as our audience has grown quite a bit since then. I'll want to create it myself though if we're going to get one going.

It was an easy fix; should be fixed for the next beta.

I have this on my list to fix, and I am able to replicate it @Undertherainbow. Hopefully I can fix it here soon.

Hi @angryherbalist, you can get most of this information in the following places: In the Readme.txt files in the three theme folders inside your LaunchBox folder In the LaunchBox\Themes\Documentation.pdf file In the custom themes YouTube videos here: Forgive me for not addressing each individual question, but most of this information is available elsewhere, and it would take me an hour to respond to everything. Feel free to follow up with questions after you've reviewed things.

Yeah, that is definitely the first time I've ever seen that, pretty weird. Yeah, it would be worth trying a clean version of LaunchBox to see if you have the same issue. You can just install LaunchBox to a different folder than your existing setup, and see if it works.

@LordEvyl We'll need more information on what you mean here. Are you seeing this error when browsing the games database website? Or in LaunchBox?

Wow, that's goooooood.

To be honest, if we put it on the poll, history tells me that it would not be highly voted. Most people would look at it and go "what's GameBase?" and then ignore it, as that's how items like this typically go. That said, I do see the value in the feature, so hopefully we can add it in eventually.

7-zip is included with Big Box; it appears that it's trying to extract libraries that Big Box needs to run correctly on startup. If it's never returning, then all I can figure is that maybe it's a file permissions issue or something of that nature. You could try deleting the LaunchBox\VLC and LaunchBox\CefSharp folders to see if that helps.

I'm not certain, but I think this might be an issue with DS4Windows, as I was seeing this problem myself even before we made any changes to the controller code. I had the exact same issue.

The reason why XInput was developed by Microsoft in the first place was because of these horrible inconsistency issues with DirectInput. But if we only supported XInput, people probably wouldn't like that too much.

Ugh, okay. So the issue is that DirectInput-based devices are horribly inconsistent with how they report their status. In order for me to be able to detect when a stick or a trigger is moved, I have to know when it's not being touched, and when it's being moved (of course). Unfortunately, there are apparently some DirectInput devices that don't behave as expected. For example, no movement for one device might be 0, while 0 might mean pressing up with another device, so it's somewhat of a nightmare. I wanted to avoid making the user have to calibrate every single device, but at this point I don't really know what else to do. It's possible that I can still make it all work by disabling the triggers and the right stick for DirectInput devices, as those are what seem to cause issues, but then of course DirectInput devices won't work at all with the right stick or triggers.

Try unselecting it to see if that fixes the issue. It may be a stray controller or something that is interfering. Uncheck it and let me know what all you see in the drop down.

Hi @Namedos; first off, killing LaunchBox and/or Big Box with the Task Manager is asking for trouble. LaunchBox and Big Box stay open in the background (should be a max of a minute or two) after closing in order to finish saving all settings and data. If you kill it, it won't be able to save stuff and you'll likely eventually end up with corrupted or missing data. I strongly advise not to kill it with Task Manager unless you're 100% certain that the process is locked up, which should be very rare. You will end up messing up your data if you keep killing unnecessarily. If Big Box isn't starting, it may be related to the above. It also may be that you just need to wait a minute or two for the saving process to actually finish (you may be starving it from previous Task Manager kills).

Okay, the problem is that the DirectInput version is causing issues when you have Use All Controllers checked. Not sure what we're gonna do about that at this point.

What do you have selected for your controller? Are you using Use All Controllers?

Okay, thanks. Do you have "Use All Controllers" checked? What is the name of the controller in the drop-down list? Also, have you tried beta 4?

Beta 4 is out now with a hopeful fix for PS4 controllers with DS4Windows, when "Use All Controllers" is checked. Everything is working properly for me now in that case, in my testing. This may also possibly fix the issues with controller input over the Steam Link, but I'm not sure about that. If anyone uses that scenario and can test, I'd appreciate it. As far as I am aware at this point, controller input over the Steam Link is the last remaining issue with the controller overhaul.

I'm sorry to hear; there's probably not a lot we can do, sadly. Everything is hosted over here in the US, and sometimes the Internet can be fickle when transferring things overseas. If you have access to a VPN, that can often help.

I'll need more information. What controller are you using?

I looked into this; DS4Windows will give you options for three different controllers in LaunchBox: XInput (Xbox 360/Xbox One) Controller (XBOX 360 for Windows) Wireless Controller #3 is there and works properly via DirectInput even with DS4Windows not running. #1 works properly via XInput simulation, which is the one I would recommend using. #2, however, does not work properly. It's apparently simulating an Xbox controller via DirectInput, and something isn't working as expected. The issue is that if you select to Use All Controllers, it attempts to use all three. It should work fine if you uncheck that and select one of the other two. I'll see if I can just disable #2.