search

crocokyle / Valorant-Ultrawide-Fix

Scales the UI and game to an ultrawide ratio without stretching. This does not increase horizontal FOV and does decrease vertical FOV
27 stars 2 forks source link

Duplicate of #7 Taskbar on another monitor results in the wrong aspect ratio #10

Closed crocokyle closed 3 years ago

crocokyle commented 3 years ago

I do have the same problem, could it be because of I (or we) have a monitor above the main one? My logs: SysSetup_log.log ValorantLauncher_log.log install_log.log

Originally posted by @Jugistyler in https://github.com/crocokyle/Valorant-Ultrawide-Fix/issues/8#issuecomment-772839881

crocokyle commented 3 years ago

@Jugistyler when you run the Ultrawide Launcher, does the game start up on the correct monitor? Should have been monitor number 1 which has a resolution of 3440 x 1440?

Also does your Windows Taskbar have autohide enabled or disabled?

Mr-Stetson commented 3 years ago

Yes, it starts in correct monitor and detects the correct resolutions. Taskbar Autohide is disabled. Here is my monitor orientation if it helps: Screenshot (2)

crocokyle commented 3 years ago

@Jugistyler Thanks for the screenshots. I'm starting to realize how important the taskbar position is to this script. not exactly sure why, but I'd be willing to bet that if you move the taskbar to the bottom of the monitor you want to play on, it will work properly. This is not a solution, but let me know if that works and I'll update #7 so I can work on this when I get time.

crocokyle commented 3 years ago

@Jugistyler I can confirm that placing the taskbar on another monitor causes this issue. It doesn't appear that there is an immediate fix for it. It seems like the entire script is dependent on the taskbar for some reason. Since this and #7 are the same issue, I'm going to close this as a duplicate but feel free to check back or comment in #7 if that worked for you. I think the only workaround is to move your taskbar at the moment.

Sorry, I know that's not a proper solution. This may go beyond my script and have more to do with Valorant itself, but I'll keep trying to find a workaround when I get some time.