BenQ XL 2411T Not scaling games correctly?

Associate
Joined
30 Nov 2012
Posts
133
This has happened since purchase and has without a doubt been annoying but also fixable; whenever a game is launched for some reason if the game is not natively running at 144hz then my monitor renders the image on what appears to be a slightly smaller screen (maybe 23-22 inch within a 24 inch monitor?), but then runs into the problem of things generally looking a mess due to the monitor trying to display a 1080p image without the required pixels, this can usually be circumvented by editing ini files to make the game render at 144hz, but when trying to play burnout paradise (and i imagine LA noire when i get round to it) the game refuses to render in full screen due to running at 60fps, the monitor believes it is running at 24 inches (checked in settings) and this issue is really starting to bug me, after googling i can find no solution so was wondering if any of you guys could help me? thanks in advance
 
is the game running at the correct ratio ingame? u havent downscaled the monitor to a 22w"(16:10) or 21.5" (16:9) by any chance? inside the monitor settings itself?
 
Yeah games running at the correct ratio and according to the monitor itself its running at 24 inches? :( i tried various different inputs from my gpu to no avail :( any other ideas?
 
no sorry , other then mabe a scaler in ur gfx card options messing something up , mabe the games simply dont support that hz/res ?
 
I'll have a look around for scaler options, and i hope that's not the problem, i would have expected the panel to be able to show signals of a lower hz, may inquire about a return if not. Thanks for the help anyway! :)
 
was about to suggest, go into the nvida control panel and from one of the monitor adjustment menus there's a list, of options, one of which is to perform scaling on GPU or monitor. i had some odd issue where folder windows were stuttering on screen when moving them about. turned out after i changed the scaling to GPU only for both monitors the problem was fixed.

worth a try :)
 
Back
Top Bottom