LB+BB v13.23-13.27 mouse and keyboard input delay only caused by application

[neosean99]

Launchbox, and BigBox have consistently caused mouse, and keyboard massive delay once opened. This is mostly noticeable while trying to function within Launchbox. I have reported this previously, and is still very much an issue. It damn near makes it impossible to work with your collection without pulling your hair out. Trying to search I have to type things multiple times as they just don't type. Or clicking on things up to 10 times to get them to open. I have reported this before, and I feel the matter was not taken seriously due to the response we received. 

I prematurely marked this solved as a Beta did seem to solve this issue for a bit, or at least make it way less noticeable. It is still present as an issue, and I feel needs to be reposted. I am not a stranger to troubleshooting, computers, or Launchbox. Controllers checked or not in settings this still happens, and only when this is open. My system is beyond capable, and was not an issue prior to v13.23. Upon rolling back to v13.22, this does not happen. This has been replicated on 2 other systems with different mice and keyboards. Please advise. With @____AiR____

System: i7 9750, 32gb Ram, RTX 2060, Windows 10

 

Edited June 3 by neosean99

[MRPLOW21]

I also have this issue

[____AiR____]

Yes, I am still experiencing the same mouse issue when running the latest version of LaunchBox. Every update since version 13.24 has introduced the same bug, making the software navigation basically unusable for me. My mouse moves in a delayed fashion and mouse clicks go unregisterd.  My hardware functions perfectly and works fine on version 13.23 and all previous releases, so I still use that version for now. In the past I've tried troubleshooting - adjusting my software and peripheral settings many times based on how others suggested to resolve the problem but without success unfortunately, but down the line I look forward to get the latest and greatest version of Launchbox working.  I love ya Launchbox!  

[AstroBob]

Hey all, sorry for the delay and issues following up on this, it sounds like enough people are having this issue but we're having a hard time reproducing this on our end. Based on the version cutoff you’re describing, this may be related to controller input handling changes that started around 13.24, especially DirectInput controller polling. It may also be affected by video/audio playback in some setups, so we’d like to try and gather a bit more detail.

We'd love it if you can try the following (I know some of you already have, but for those who haven't)

1. In LaunchBox, go to Tools > Options > Game Controllers.
2. Uncheck Enable Game Controllers.
3. Restart LaunchBox completely.
4. Test whether mouse movement, mouse clicks, and keyboard typing return to normal.

Please also test Big Box separately:

1. Open Big Box.
2. Go to Options > Controller.
3. Disable controller support there as well.
4. Restart Big Box.
5. Test whether the delay still happens.

When replying, please include:

• Which LaunchBox version works normally for you, and which version first shows the issue.
• Whether disabling Enable Game Controllers fixes it after a full restart.
• Whether you use any controller-related software, such as Steam Input, DS4Windows, reWASD, vJoy, ViGEm, JoyToKey, Xpadder, or similar.
• What controllers or input devices are connected, including wheels, pedals, flight sticks, fight sticks, Bluetooth controllers, or virtual controllers.
• Whether the issue happens with all controllers unplugged.
• Whether the issue happens in LaunchBox, Big Box, or both.
• Whether you have auto-play videos or auto-play music enabled.
• Which video playback engine you’re using, if you know.

If disabling game controllers fully resolves it, that is very useful information and points us toward the controller polling/input path. If it still happens with controller support disabled and all controllers unplugged, please mention that clearly, because that would push us more toward the video/audio playback side instead.

Please let us know and we'll try and narrow this down.

[neosean99]

I appreciate the reply. As seen in the previous post, we have all stated that it is not the Disable Controller support solution. It does not fix the issue within LB or BB. It is easier to tell in LB due to functioning with a mouse and keyboard vs usually using a game controller for BB. However, the issue is still seen within BB when manually opening a browser or emulator and trying to function. I just tested this all again with the current beta as well. Still an issue. I would also like to note that it seems to only cause the issues when not in a full screen application. Once you open a game from LB or BB, the inputs are fine within the application. Upon exit, same issue. I do use DS4 Windows with a Dual Sense controller. I have continuously tested to see if this occurs with / without the controller, and with DS4Windows not started on a machine. I use Xinput for my controller when it is connected. If I plug in my native PC Fightstick (Monoprice Dark Matter) in which is Xinput default, the mouse and keyboard input issue still exists. I do not have auto play videos or music enabled. I do have background music, and platform videos within BB, but that would not effect LB. I have already stated the versions that this occurs on, and the version previous that does work v13.22. This has gone on for many versions now, and makes organizing in LB impossible. I'm very frustrated by this at this point. Alot of repeating, and not alot of action for sure. I've been insanely descriptive. At this point, I may have to find another option after 6 years of being happy with this platform. It makes working on simple entries tedious, and borderline impossible. *Please note as I have said this multiple times... I've tested this on 3 different PC's. Different keyboards and mice. This is the only application causing this issue. I am not going to tolerate the repeated suggestion of disabling controllers for the 5th time.

[neosean99]

I could have guessed that is how this "conversation" would go. lol Maybe this wouldn't sound so hostile had someone actually checked into this. @AstroBob I clearly stated we already tried your suggestion multiple times PRIOR to you suggesting! Thats the only solution that's been given, and it's NOT VALID.  The problem is that you didn't read any of it. Why did I waste my time trying to document or state that I've done x y z solutions? This is a joke at this point. I've spent countless hours over the course of 6 years so that I can end up with a platform I can't function in after all my work. Pardon my french but this is complete BS. I CANNOT WORK IN LAUNCHBOX!!! Literally have to click 10 times to get it to register a mouse click on anything while open. Including Launchbox, or any other app open while Launchbox is. It's happening now while i was trying to open Chrome and type this. As soon as I close LB, everything is normal. This isn't worth it after waiting through all of these versions. Literally been an issue for over a year. All that's been suggested is game controllers... nothing further. Nobody actually reads what is written. Nobody read it from the original v13.24 post. From a platform I ranted and raved about, told or shown almost all of my friends, to having to switch to a new platform with multiple admins suggesting the same solution (that we said didn't work) multiple times... Thanks for the help... or lack there of. I strongly challenge you to go back to v13.22 and observe the giant performance increase / lack of issues as well. As I've stated before, my system should be more than capable even after all the updates. 

Edited Sunday at 07:31 PM by neosean99

[____AiR____]

Hi,

 

@AstroBob I want to provide a response to the points you’ve requested and then follow up with an explanation below:

 

·       Launchbox 13.23 is the last version that worked normally for me.

·       Disabling the Enable Game Controllers does fix the mouse issue after a full restart

·       I do not have any specialized controller related software just generic drivers installed by windows.

·       Connected controllers I have are an Xbox controller (wired) and a wireless mouse

·       The issue does not happen when all controllers are unplugged. (I did not test this with the mouse removed though).

·       This issue occurs in the Launchbox program as I do not have BigBox… yet.

·       I do not have auto play videos, auto play music or shuffle music enabled

·       I do not have any specific playback engine on my build.

 

I've recently installed the latest version of LaunchBox 13.27, upgrading it from 13.23. I have previously tested each update from 13.24 onwards but encountered the same peripheral conflict on my machine. For context, my system hardware is an ASUS F15 with 40GB RAM and an RTX 3060 (6GB VRAM) running Windows 11. I am using a wired Xbox controller and a wireless mouse.

 

I've had mixed results overall with troubleshooting, but I ultimately keep reverting back to version 13.23. The mouse issue is still present after installation, though I was able to bypass it temporarily. When the game controller option is enabled the mouse cursor becomes very erratic and fails to register clicks consistently. If I disable the game controller option, the mouse issue persists until the program restart occurs. After restart the mouse moves normally again inside of Launchbox.

 

I repeated the exit/restart process to see if it maintained that result, and it did. Next, I re-enabled the game controller menu option, and exited the software. I then plugged in my Xbox controller and started the software; resulting in both the mouse and controller operating perfectly. After several successful test restarts with both peripherals plugged in, I thought the issue was solved.

 

However, if I unplug the Xbox controller afterward and restart LaunchBox again with only the mouse plugged in, the stuttering/dragging mouse issue returns. It’s as if it’s locked in some sort of loop searching for the controller that I removed? It seems that in order for me to use 13.27 properly, I would need to leave my game controller attached at all times while the software is on, or disable the game controller option and restart the software every time I want to just use the mouse alone. This isn’t a huge deal as I use the controller most of the time when I’m using Launchbox for games but sometimes I use it for movies and the mouse is not functional for that if the conflict is present.  In the 13.23 version, this is a non-issue and I don't have to change any settings at all. Maybe there is another setting creating a conflict in my build, or something in my settings.xml file that needs adjusting I'm not certain.  Just to be clear version 13.27 does work for me if I go through the proper sequence of settings and I leave everything plugged in.  One thing also to mention is that when the mouse conflict is occurring and then Launchbox is closed down it takes a few moments but the mouse controller returns back to normal operation as I navigate in Windows.  Launchbox is the only software where this issue occurs on my system.

 

Just thought I’d share what my experience has been.  Thanks!

[AstroBob]

Hi Folks,

Thanks for the updates on this, and apologies for the delayed follow-up here. We’ve had a few folks out recently, but rest assured we are following these reports closely and doing our best to reproduce the issue on our end.

@neosean99 , apologies as I know you’ve submitted multiple detailed reports, which have been very useful. I also want to acknowledge that you’ve already tried the controller-related suggestions multiple times, and I’m sorry if it felt like we weren’t fully hearing that. No need to confirm anything else for now, as we’re using your existing reports to try and nail this down. For everyone else who has been adding info, that has also been very helpful.

For full transparency, we have not been able to reproduce this exact behavior consistently yet but we are trying our best to get to the bottom of this. Based on the version range and the behavior being described, we’re continuing to look closely at input handling, especially around controller detection/polling and device state changes. At the same time, we’re keeping an open mind in case there is another contributing factor or interaction we haven’t identified yet.

I know this is incredibly frustrating, we're continuing to try and nail this down will share updates as soon as we have something meaningful to report. Really appreciate y'all bearing with us here.

[neosean99]

@AstroBob honestly, the responses and lack of severity have been the frustration. Your last response is valid. I've said where my frustrations lie. I have dropped back to v13.22 and have no plans to update until this has been attempted to be fixed. Unlike @____AiR____ my issue starts on v13.23, but less severe. Once moving to v13.24, LB is unusable. A whole year of troubleshooting on this matter on my own just trying to get my platform to function correctly. As soon as dropping back, I am able to fully function again. I have also tried fresh installs with just a few example games on most versions to confirm it isn't my library causing the issue. Same thing occurs. 

To be clear, this occurs with or without a controller connected. With or without Controllers disabled in settings. I believe @____AiR____, and a few others have replicated this also. I would also like to note that performance has really taken a hit the last few updates I tried. Specifically 13.25 on. Even after opening once, and closing to reopen it is not near as fast on the draw as it was prior to the video codec change (Not saying that is the cause, using it as a milestone).

I appreciate the accountability, and will look forward to progress hopefully.

~Sean

Edited 2 hours ago by neosean99