Window Region Coordinates not working on 2nd monitor
Moderator: MiRai
6 posts
• Page 1 of 1
Re: Window Region Coordinates not working on 2nd monitor
Looks like it may be a display scaling issue in Windows 10? My main monitor is at 125%, secondary at 100%. Could that be the problem?
League of Extraordinary Multiboxers
Posts: 4591
Joined: Sat Feb 15, 2014 11:14 am
Location: In the dining room, with the lead pipe.
Re: Window Region Coordinates not working on 2nd monitor
Yes, definitely. You will normally need them to both be set to 100%.
Re: Window Region Coordinates not working on 2nd monitor
The problem with that is it makes all my other text (Firefox), etc. so small as to be almost unreadable. My monitor is 32 inches. This was never a problem before, is it only an NVIDIA problem?
League of Extraordinary Multiboxers
Posts: 4591
Joined: Sat Feb 15, 2014 11:14 am
Location: In the dining room, with the lead pipe.
Re: Window Region Coordinates not working on 2nd monitor
No it's a scaling problem, and its lies.
There are some things in ISBoxer to attempt to deal with it, but essentially scaling does all rendering off screen, and then redraws the final composite for your viewing pleasure. This causes a bit of grief, because the offscreen render is at native resolution, and that determines the positioning, but when ISBoxer is querying for positioning, it is getting the final sizes. It might work better if ISBoxer queried for the native resolutions, and set positioning based on that - but I don't really know. Needs some more experimentation.
Presumably if you have a 32inch with tiny writing, you have a 4k monitor. This is pretty much when this phenomenon was noticed - when 4K monitors that make everything TEENY WEENY came out. I use Visual Studio and SQL Server Management Studio in my day job, and they just don't deal with scaling particularly well either, 4 years down the track.
Anyway, so the options generally are, set the scaling to 100% on both monitors. If you don't like the tiny writing, then in Windows, change the resolution of the problem monitor to be something non native. Like if you have 3840x2160, change it to 2560x1440. That way stuff will be bigger, but Windows wont do any scaling. The end result will be pretty much the same, although certain things wont look at fine, and ClearType wont work very well.
There are some things in ISBoxer to attempt to deal with it, but essentially scaling does all rendering off screen, and then redraws the final composite for your viewing pleasure. This causes a bit of grief, because the offscreen render is at native resolution, and that determines the positioning, but when ISBoxer is querying for positioning, it is getting the final sizes. It might work better if ISBoxer queried for the native resolutions, and set positioning based on that - but I don't really know. Needs some more experimentation.
Presumably if you have a 32inch with tiny writing, you have a 4k monitor. This is pretty much when this phenomenon was noticed - when 4K monitors that make everything TEENY WEENY came out. I use Visual Studio and SQL Server Management Studio in my day job, and they just don't deal with scaling particularly well either, 4 years down the track.
Anyway, so the options generally are, set the scaling to 100% on both monitors. If you don't like the tiny writing, then in Windows, change the resolution of the problem monitor to be something non native. Like if you have 3840x2160, change it to 2560x1440. That way stuff will be bigger, but Windows wont do any scaling. The end result will be pretty much the same, although certain things wont look at fine, and ClearType wont work very well.
6 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 3 guests