custom 4/3 résolution on Asus PG27AQN (CSGO)

[kameCS]

hi,
i currently own an Acer 1080p 390hz and i can play csgo with custom resolution 4/3 1920x1440 390hz the graphics are detailed much better than 1440x1080 a pleasure for the eyes.
i am hyped for the new Asus PG27AQN 27" 1440p 360hz
what maximum custom resolution in 4/3 it supports under csgo in 360hz ? the ideal would be 2560x1920.

Can someone who owns this screen confirm that this is possible?

[Crazyness]

Highest resolution on Acer in 4:3 is 2560x2160 at 185hz (teoretically 189 max sometimes it may cause some flickers,some color thingys,etc)
it is derivative from 4k resolution at 3840x2160 at 140hz(max 143 sometimes also some flickers colors etc)

so max safe hertz and res is 3840x2160 140hz
and 4:3 2560x2160 185hz

soon i will post about the biggest thing about the acer 390hz
and the ability to actualy deliver any resolution you want..
(i already made a post about transforming this acer into native 4k 140hz)

example:
Samsung have pannel 32:10 3840x1200 curently not available it was 2020 or 2021 model
120hz!!!! for about 1k $ or E..

and on Acer you can run that same resolution 3840x1200 240hz!!!!

[kameCS]

it's impressive to be able to increase the resolution, on the acer 390hz I can go up in 4/3 to 2040x1530 390hz but I prefer to keep the 1920 native horizontal because the screen is sharper

[Crazyness]

Yes but actualy no..

2560x2160 looks same percentage better as 1920x1440 looks better than 1440x1080

only issue is max hz..

so if you only play csgo,
you will c much more benefit from higher hz than from higher resolution.

1920x1440 390hz > 2560x2160 185hz

in any other case ..
2560x2160>1920x1440

[kameCS]

I am looking to use Asus PG27AQN in 2560x1920 360hz 4/3

[nolikeee]

max res on pg27aqn is 1920х1200

[destroya_cs]

This is certainly frustrating to learn. From what I've been able to find online from all sources, you must be on 1920x1080 (16:9), 2368x1332 (16:9), or 2560x1440 (16∶9) to be able to run 360 Hz (with DSC). 16:10 resolutions (and any others) seem to be locked to regular DisplayPort 1.4 specs (or HDMI 2.0 but those are even lower, wouldn't use). Therefore common non-DSC, non 16:9 resolutions would be 1920x1200 (16:10) @ 360 Hz, 2560x1080 (~21:9) @ 300 Hz, around ~1810x1358 max for (4:3) @ 360 Hz, sorry I don't have exact math on that one just an estimate.

Disappointing that they wouldn't include an HDMI 2.1 port here as AMD 6k, 7k, RTX 3k, 4k series all have it. In this case I don't consider this a true 360 Hz monitor if you're locked in to using 16:9, and considering its a monitor built for the hardcore gamer, a lot of them (us) use 16:10 or other. I would go so far as to say its false advertising but we do our due diligence to suss this out.

If anyone is able to get 360 Hz DSC working on ALL resolutions (not just 16:9 ones) please reply with your findings. Maybe this can be solved in a driver/firmware update, otherwise its a deal-breaker for me.

[m4ste3]

any news on this?

This is certainly frustrating to learn. From what I've been able to find online from all sources, you must be on 1920x1080 (16:9), 2368x1332 (16:9), or 2560x1440 (16∶9) to be able to run 360 Hz (with DSC). 16:10 resolutions (and any others) seem to be locked to regular DisplayPort 1.4 specs (or HDMI 2.0 but those are even lower, wouldn't use). Therefore common non-DSC, non 16:9 resolutions would be 1920x1200 (16:10) @ 360 Hz, 2560x1080 (~21:9) @ 300 Hz, around ~1810x1358 max for (4:3) @ 360 Hz, sorry I don't have exact math on that one just an estimate.

Disappointing that they wouldn't include an HDMI 2.1 port here as AMD 6k, 7k, RTX 3k, 4k series all have it. In this case I don't consider this a true 360 Hz monitor if you're locked in to using 16:9, and considering its a monitor built for the hardcore gamer, a lot of them (us) use 16:10 or other. I would go so far as to say its false advertising but we do our due diligence to suss this out.

If anyone is able to get 360 Hz DSC working on ALL resolutions (not just 16:9 ones) please reply with your findings. Maybe this can be solved in a driver/firmware update, otherwise its a deal-breaker for me.