Open Retroeer opened 4 months ago
@garrynewman I have a decent enough suspicion that this may be caused by ?
Here's a completely fresh project still having the same issue, and trying to uninstall and reinstall the issue still persists https://github.com/user-attachments/assets/d7c6dcd2-b8fc-483c-891f-540be5eb44ef
Despite a recent commit, this issue seems to still persist
This also happens to me when using the Windows key, please look into it aswell
Just adding some more context for when this gets looked at again:
@Retroeer tried it on an older build of S&box when it wasn't an issue and it still happened, so it's probably something related to Windows 11 rather than S&box.
I'm on win11 and don't get the issue
I get the issue as well.
I'm not expecting a fix without debugging, but at this point I'm not sure what to debug, I've closed every non-critical application on my computer and it persists, so unless the solution is deleting sys32 I'm out of ideas here, and I would like to imagine I don't need to reinstall my entire operating system just to solve this
I've had this issue happen to me a few times, however it seemed to only happen when I had a external controller plugged in and once I unplugged it it was fine.
We already went through that and every other possible troubleshooting you can find online. Nothing worked afaik unless there's something we weren't told.
I can confirm I have this as well
Confirmed only way to fix this is by reinstalling Windows 11.
I am once again having this issue, seemingly caused by opening a second instance, as I did not do that prior, I guess I'm cursed with this again until I reinstall Windows, again, yayyyyyyyyy
It seems there may be some kind of file getting mangled by sbox causing this behaviour? I've nuked the entire sbox directory and reinstalled, the issue persists, nothing changed between from when I didn't have the issue to when I started having it again, aside from opening a second instance, could opening a second instance be changing some kind of file? I've practically run out of ideas and there's been little to no communication regarding this, I really do not want to reinstall my operating system every couple of weeks and this issue makes sbox absolutely infuriating to use. https://github.com/user-attachments/assets/047707ca-765d-4da0-bad5-cba09f6a17a5
If you make the small mistake of alt tabbing, a thing I would imagine many people commonly do, even unknowingly, your entire flow is interrupted for about 2-4 seconds, this is an issue that people get around by using the tilda key, I've been trying to force myself to use this button but it makes things really annoying when all I want to do is just switch windows, not click around the editor, because if you do that, clicking back in will yank your mouse away from you, to which you're greeted with staring at your monitor and twiddling your thumbs like an idiot for a couple seconds. I understand that Facepunch staff do not have this issue, I'm not sure what causes the issue, I will happily do literally anything you ask of me to figure out what this issue is, I can't however continue reinstalling my operating system every couple of weeks, nobody should be forced to do this to escape an annoyance.
I’ve reinstalled windows recently and have been testing via a second instance. Maybe it just happens with time.
Describe the bug
If you alt tab in play mode, your mouse gets glued to the viewport for long enough to start driving me insane and to write the issue in the first place
*Edit: after not getting it after a few attempts this seems to be inconsistent
To Reproduce
Expected behavior
The mouse should be free, free I say!
Media/Files
https://github.com/user-attachments/assets/a0b17b0e-782b-405b-832c-2c657a411757
Additional context
No response