ASUS ROG Swift PG279Q 144hz 2560x1440 IPS G-Sync.

as promised, here's the full review of the PG279Q. took a lot of work and overtime to do all that testing. i must try and cut it back for the future!

http://www.tftcentral.co.uk/reviews/asus_rog_swift_pg279q.htm

Not to nitpick but..
"1) Turbo key - You can select your preferred refresh rate with a turbo key to toggle refresh rates on the fly without needing to access the graphics driver control panel. You can quickly select from 60, 120, or 144Hz (or max overclocked refresh rate if you've used that option). This may be handy while in the middle of a game to match the different frame rates of different games to maintain smoothness. It can also be used to lessen the load on your graphics card and CPU by setting a cap on the Hz for different games."

It takes forever on my monitor to "flick" between them.
 
^^ Depends on the amount of motion onscreen :( in windows it can take upto 20 second to change even if I move a window around but in fullscreen games its generally close to instant.
 
Not if you communicate your intention early enough. The 'time limit' that applies is related to informing the retailer of your intention to return the product rather than the physical return of the product.

Thanks for info, I am trying deal with them but not sure white dot is dead pixel/ stuck or just bleed inside screen or something dirt...
 
I assume the very slight brownish tint on white backgrounds towards the top of the screen would be caused by the luminance being lower in that region of the screen?

I saw Hexus.net and TFTcentral's both show a similar reduction in luminance towards the top.

I'm thinking it must be but just want to make sure there's nothing wrong with it before I declare I'm keeping it :)
 
I assume the very slight brownish tint on white backgrounds towards the top of the screen would be caused by the luminance being lower in that region of the screen?

I saw Hexus.net and TFTcentral's both show a similar reduction in luminance towards the top.

I'm thinking it must be but just want to make sure there's nothing wrong with it before I declare I'm keeping it :)

That would certainly contribute towards it, plus possible white point uniformity issues. So if it doesn't particularly annoy you I'd suggest just keeping it as it is quite normal. :)
 
Did you do any testing at any of the other overclocked speeds? 165hz is actually worse than 144hz for response times, but is it worth using any of the other speeds? eg. 150, 155 or 160? So you can get higher refresh without the response times getting worse than 144hz?
 
Did you do any testing at any of the other overclocked speeds? 165hz is actually worse than 144hz for response times, but is it worth using any of the other speeds? eg. 150, 155 or 160? So you can get higher refresh without the response times getting worse than 144hz?

Set 165Hz, cap your framerate slightly lower and if it works like the older Swift should produce good results.
 
I have settled on 150fps cap running at 165hz and that seems to stop it from spiking to 165 with a couple fps margin.

At that point i suppose 165hz is quite good not because you use 165 but because you can cap it close to its optimum frame rate of 144 ish with no lag.

Its a shame Nvidia doesnt roll this into a simple option in the control panel as its obviously what everyone would want if it was explained to them properly.
 
Last edited:
Back
Top Bottom