I am aware that the game doesn’t officially support ultrawide. According to what I’ve seen, I should be able to run it in Windowed mode and see black bars on the side. But I don’t, I see my desktop, and it runs behind my taskbar. I have run it in Windowed mode before, but occasionally the window will get messed up and I can’t get it back to the right aspect ratio and window size.
I’ve tried adjusting the variables.txt file and that’s just made things worse. Hoping someone has a suggestion. Also hoping Blizz sees fit to add proper borderless fullscreen support for all resolutions.
I’m having the same issue in single player, and I don’t remember having this issue. I’m fine playing with black bars on the sides, but I’m not going to bother otherwise. It’s a bit ridiculous.
Fullscreen = gives the black borders,
windowed fullscreen = is the same thing but your able to move the mouse off the sc2 screen when not in a match, as well as keeping the sc2 window up when alt tabbing out of it in match.
Windowed= is the resizable movable screen windows and seperates sc2 from being stuck on the monitor it currently lives ( usually your main)
chances are your on windowed dirtygremlin and need to resize it to fit the screen or switch to fullscreen.
Yes, I understand the different screen modes. I still have the visual bugs regardless of which windowed mode is chosen.
I can still lock cursor to the screen, it’s just incredibly annoying. Hard to believe a AAA can’t (won’t) patch this when a garage shop dev would have resolved this immediately, if they didn’t already have the foresight to test it and patch before release to begin with.
First, you might be behind on the times, Dirty Gremlin. It’s not a matter of AAA or garage anything. The game has been in maintenance mode for over half a decade. Anything that isn’t game breaking isn’t likely to ever be fixed.
Second, seeing that there has never been a deluge of this kind of report, it is evidence that it was never a widespread issue across the playerbase. Meaning, it points to something unique to your system environment.
And if it is, that’s fine. No studio can account for the nearly infinite combinations of system environments.