ASUS ROG Swift 500Hz Announced!

[daviddave1]

In the video about the PG27AQN you sent, around 12 minutes, what I can hear him say is the following:

- 21 NITS at PW=10 which is not very usable in practice
- PW=50 provides a good balance between clarity and usable brightness
- 150 NITS measured at PW=50

I understand you don't want to negate the benefits of better motion clarity by walking around with sunglasses trying to spot enemies, but that's not at all how I feel like with the brigthness I'm using. I feel like my brightness is completely sufficient and adequate.

I am sorry you are right; He did say 150 nits provides a good balance between usable nits and brightness. That makes the 390hz Acer with VRB on extreme also acceptable. I am definitely not on that side.
Again i rather play on the Acer 540hz with 480 nits with no backlightstrobing then on a Asus 540hz with 150 nits!! with backlightstrobing.
Thank you for your input though. It's interesting to see that some people don't mind 150 nits on a competitive fps monitor. I always thought that's impossible and that's on me.

[daviddave1]

I tweeted the following to hausgames:

"Hello @hausgameS_ @HardwareUnboxed says the PG248QP has 300 nits with ULMB2 100 pulsewidth. Thats lower then the 348 nits XL2566K DYAC. @OptimumTechYT says PG248QP HAS 352 nits with ULMB2 100 pulsewidth.Making the PG248QP brighter then XL2566K with backlightstrobing. Who's right?"

He answered:

"The PG248QP is bright enough for me with ULMB 2 ON, where as the PG27AQN was definitely not. I feel ULMB2 on PG248QP isn't bright as DyAc+, but bright enough."

[kameCS]

Does the monitor allow you to play in 1440x1080 stretched at 500/540hz?

[daviddave1]

Does the monitor allow you to play in 1440x1080 stretched at 500/540hz?

yes a chinese youtuber said so

[Discorz]

But then then it becomes unclear what the nits are with medium and short pulse. 30 and 150 nits? That cannot be correct. Can someone please explain?

Makes perfect sense. Shorter the pulse width, lower the brightness - trading off brightness for motion clarity. Half the pulse, half the nits. That's how it's always been with strobing. When strobing, backlight voltage is boosted, so initial nits is no longer ~420 but ~1200 nits. They can do this because backlight can safely handle higher peaks when flashed for shorter periods. ULMB PWidth 100 is doing 25% duty cycle meaning its cutting MPRT and nits to 25% (u can find ULMB duty cycles here). And here is one example of how changing pulse width under photodiode looks like.

at Pulse Width 100: 1200 x 0.25 = 300 nits, or for MPRT 1.85 ms x 0.25 = 0.46 ms
at Pulse Width 50: 1200 x 0.125 = 150 nits, or for MPRT 1.85 ms x 0.125 = 0.23 ms
at Pulse Width 10: 1200 x 0.025 = 30 nits, or for MPRT 1.85 ms x 0.025 = 0.05 ms

Since Optimum measured somewhat higher ~350 nits, peaks would be ~1400 nits. I wonder if "G-SYNC Esports Mode" affects brightness and that's why they got different measurements. Who knows! Could be before/after calibration case too.

On a PG248QP at 540 Hz you don't need to use less than Pulse Width 60 (15% duty cycle) as that would give you perfect motion sharpness all the way up to ~4000 px/sec. But in case u find yourself eye-track faster than that, then sure lower it even further. But higher speeds would probably be unrealistic to eye-track on 24" 1080p dispaly. Fun fact, if u want almighty CRT-like MPRT that would be 90+ PWidth.

[daviddave1]

But then then it becomes unclear what the nits are with medium and short pulse. 30 and 150 nits? That cannot be correct. Can someone please explain?

Makes perfect sense. Shorter the pulse width, lower the brightness - trading off brightness for motion clarity. Half the pulse, half the nits. That's how it's always been with strobing. When strobing, backlight voltage is boosted, so initial nits is no longer ~420 but ~1200 nits. They can do this because backlight can safely handle higher peaks when flashed for shorter periods. ULMB PWidth 100 is doing 25% duty cycle meaning its cutting MPRT and nits to 25% (u can find ULMB duty cycles here). And here is one example of how changing pulse width under photodiode looks like.

at Pulse Width 100: 1200 x 0.25 = 300 nits, or for MPRT 1.85 ms x 0.25 = 0.46 ms
at Pulse Width 50: 1200 x 0.125 = 150 nits, or for MPRT 1.85 ms x 0.125 = 0.23 ms
at Pulse Width 10: 1200 x 0.025 = 30 nits, or for MPRT 1.85 ms x 0.025 = 0.05 ms

Since Optimum measured somewhat higher ~350 nits, peaks would be ~1400 nits. I wonder if "G-SYNC Esports Mode" affects brightness and that's why they got different measurements. Who knows! Could be before/after calibration case too.

On a PG248QP at 540 Hz you don't need to use less than Pulse Width 60 (15% duty cycle) as that would give you perfect motion sharpness all the way up to ~4000 px/sec. But in case u find yourself eye-track faster than that, then sure lower it even further. But higher speeds would probably be unrealistic to eye-track on 24" 1080p dispaly. Fun fact, if u want almighty CRT-like MPRT that would be 90+ PWidth.

Tnx. I found it out later also.
I could not believe anyone would play on a monitor with 150 nits or even 30 nits. And did not understand why these options are in there.
It had to be a mistake the way Hardware unboxed CASUALLY said that 150nits! is a good balance between playabilty and motionblur deductibility. (He says this is the ULMB2 video https://youtu.be/LZndZ7NWnZs?si=MxwKDHwOqvYalNS8&t=720 12:02 .)
Evidently these people do exist and dont have a superdark sunglasses expierencie with nits that low. Me personally I feel like a blind man needing a blindman stick to aim with 150 nits. Respectfully.

[Discorz]

I could not believe anyone would play on a monitor with 150 nits or even 30 nits. And did not understand why these options are in there.
It had to be a mistake the way Hardware unboxed CASUALLY said that 150nits! is a good balance between playabilty and motionblur deductibility
Evidently these people do exist and dont have a superdark sunglasses expierencie with nits that low. Me personally I feel like a blind man needing a blindman stick to aim with 150 nits. Respectfully.

Yeah, 150 nits is probably good balance for most people. You must be en exception. I personally never use over ~150 nits and thats in room with plenty of light during day.

[Jefa35]

But then then it becomes unclear what the nits are with medium and short pulse. 30 and 150 nits? That cannot be correct. Can someone please explain?

Makes perfect sense. Shorter the pulse width, lower the brightness - trading off brightness for motion clarity. Half the pulse, half the nits. That's how it's always been with strobing. When strobing, backlight voltage is boosted, so initial nits is no longer ~420 but ~1200 nits. They can do this because backlight can safely handle higher peaks when flashed for shorter periods. ULMB PWidth 100 is doing 25% duty cycle meaning its cutting MPRT and nits to 25% (u can find ULMB duty cycles here). And here is one example of how changing pulse width under photodiode looks like.

at Pulse Width 100: 1200 x 0.25 = 300 nits, or for MPRT 1.85 ms x 0.25 = 0.46 ms
at Pulse Width 50: 1200 x 0.125 = 150 nits, or for MPRT 1.85 ms x 0.125 = 0.23 ms
at Pulse Width 10: 1200 x 0.025 = 30 nits, or for MPRT 1.85 ms x 0.025 = 0.05 ms

Since Optimum measured somewhat higher ~350 nits, peaks would be ~1400 nits. I wonder if "G-SYNC Esports Mode" affects brightness and that's why they got different measurements. Who knows! Could be before/after calibration case too.

On a PG248QP at 540 Hz you don't need to use less than Pulse Width 60 (15% duty cycle) as that would give you perfect motion sharpness all the way up to ~4000 px/sec. But in case u find yourself eye-track faster than that, then sure lower it even further. But higher speeds would probably be unrealistic to eye-track on 24" 1080p dispaly. Fun fact, if u want almighty CRT-like MPRT that would be 90+ PWidth.

Tnx. I found it out later also.
I could not believe anyone would play on a monitor with 150 nits or even 30 nits. And did not understand why these options are in there.
It had to be a mistake the way Hardware unboxed CASUALLY said that 150nits! is a good balance between playabilty and motionblur deductibility. (He says this is the ULMB2 video https://youtu.be/LZndZ7NWnZs?si=MxwKDHwOqvYalNS8&t=720 12:02 .)
Evidently these people do exist and dont have a superdark sunglasses expierencie with nits that low. Me personally I feel like a blind man needing a blindman stick to aim with 150 nits. Respectfully.

It is not only about personal experience, if we talk about competitive FPS games where you need optimal visibility, anything below 250 nits is simply not sufficient. Being used to a mediocre brightness like 150 nits doesn't mean it is good enough.

Not saying you need over 400 nits to see well in game, but 250-300 nits range is the minimum depending on how bright you room is.

[daviddave1]

But then then it becomes unclear what the nits are with medium and short pulse. 30 and 150 nits? That cannot be correct. Can someone please explain?

Makes perfect sense. Shorter the pulse width, lower the brightness - trading off brightness for motion clarity. Half the pulse, half the nits. That's how it's always been with strobing. When strobing, backlight voltage is boosted, so initial nits is no longer ~420 but ~1200 nits. They can do this because backlight can safely handle higher peaks when flashed for shorter periods. ULMB PWidth 100 is doing 25% duty cycle meaning its cutting MPRT and nits to 25% (u can find ULMB duty cycles here). And here is one example of how changing pulse width under photodiode looks like.

at Pulse Width 100: 1200 x 0.25 = 300 nits, or for MPRT 1.85 ms x 0.25 = 0.46 ms
at Pulse Width 50: 1200 x 0.125 = 150 nits, or for MPRT 1.85 ms x 0.125 = 0.23 ms
at Pulse Width 10: 1200 x 0.025 = 30 nits, or for MPRT 1.85 ms x 0.025 = 0.05 ms

Since Optimum measured somewhat higher ~350 nits, peaks would be ~1400 nits. I wonder if "G-SYNC Esports Mode" affects brightness and that's why they got different measurements. Who knows! Could be before/after calibration case too.

On a PG248QP at 540 Hz you don't need to use less than Pulse Width 60 (15% duty cycle) as that would give you perfect motion sharpness all the way up to ~4000 px/sec. But in case u find yourself eye-track faster than that, then sure lower it even further. But higher speeds would probably be unrealistic to eye-track on 24" 1080p dispaly. Fun fact, if u want almighty CRT-like MPRT that would be 90+ PWidth.

Tnx. I found it out later also.
I could not believe anyone would play on a monitor with 150 nits or even 30 nits. And did not understand why these options are in there.
It had to be a mistake the way Hardware unboxed CASUALLY said that 150nits! is a good balance between playabilty and motionblur deductibility. (He says this is the ULMB2 video https://youtu.be/LZndZ7NWnZs?si=MxwKDHwOqvYalNS8&t=720 12:02 .)
Evidently these people do exist and dont have a superdark sunglasses expierencie with nits that low. Me personally I feel like a blind man needing a blindman stick to aim with 150 nits. Respectfully.

It is not only about personal experience, if we talk about competitive FPS games where you need optimal visibility, anything below 250 nits is simply not sufficient. Being used to a mediocre brightness like 150 nits doesn't mean it is good enough.

Not saying you need over 400 nits to see well in game, but 250-300 nits range is the minimum depending on how bright you room is.

The PG27AQN was to dark with its 270 nits. Had to send it back. So did Hausgames, Hausgames do find that the ~300 nits on the pg248qp are sufficiënt. He said the pg248qp IS darker then the Zowies XL2566K. This makes me doubt in buying this monitor cause the XL2566K was not the brightest ( XL2456K was brghter)
I will probely buy it at amazon when its availble in W Europe. If its to dark I send it back and most likely buy the Acer Nitro XV242F 540 hz that uses the same panel but withouth ULMB2.

[Jefa35]

Makes perfect sense. Shorter the pulse width, lower the brightness - trading off brightness for motion clarity. Half the pulse, half the nits. That's how it's always been with strobing. When strobing, backlight voltage is boosted, so initial nits is no longer ~420 but ~1200 nits. They can do this because backlight can safely handle higher peaks when flashed for shorter periods. ULMB PWidth 100 is doing 25% duty cycle meaning its cutting MPRT and nits to 25% (u can find ULMB duty cycles here). And here is one example of how changing pulse width under photodiode looks like.

at Pulse Width 100: 1200 x 0.25 = 300 nits, or for MPRT 1.85 ms x 0.25 = 0.46 ms
at Pulse Width 50: 1200 x 0.125 = 150 nits, or for MPRT 1.85 ms x 0.125 = 0.23 ms
at Pulse Width 10: 1200 x 0.025 = 30 nits, or for MPRT 1.85 ms x 0.025 = 0.05 ms

Since Optimum measured somewhat higher ~350 nits, peaks would be ~1400 nits. I wonder if "G-SYNC Esports Mode" affects brightness and that's why they got different measurements. Who knows! Could be before/after calibration case too.

On a PG248QP at 540 Hz you don't need to use less than Pulse Width 60 (15% duty cycle) as that would give you perfect motion sharpness all the way up to ~4000 px/sec. But in case u find yourself eye-track faster than that, then sure lower it even further. But higher speeds would probably be unrealistic to eye-track on 24" 1080p dispaly. Fun fact, if u want almighty CRT-like MPRT that would be 90+ PWidth.

Tnx. I found it out later also.
I could not believe anyone would play on a monitor with 150 nits or even 30 nits. And did not understand why these options are in there.
It had to be a mistake the way Hardware unboxed CASUALLY said that 150nits! is a good balance between playabilty and motionblur deductibility. (He says this is the ULMB2 video https://youtu.be/LZndZ7NWnZs?si=MxwKDHwOqvYalNS8&t=720 12:02 .)
Evidently these people do exist and dont have a superdark sunglasses expierencie with nits that low. Me personally I feel like a blind man needing a blindman stick to aim with 150 nits. Respectfully.

It is not only about personal experience, if we talk about competitive FPS games where you need optimal visibility, anything below 250 nits is simply not sufficient. Being used to a mediocre brightness like 150 nits doesn't mean it is good enough.

Not saying you need over 400 nits to see well in game, but 250-300 nits range is the minimum depending on how bright you room is.

The PG27AQN was to dark with its 270 nits. Had to send it back. So did Hausgames, Hausgames do find that the ~300 nits on the pg248qp are sufficiënt. He said the pg248qp IS darker then the Zowies XL2566K. This makes me doubt in buying this monitor cause the XL2566K was not the brightest ( XL2456K was brghter)
I will probely buy it at amazon when its availble in W Europe. If its to dark I send it back and most likely buy the Acer Nitro XV242F 540 hz that uses the same panel but withouth ULMB2.

300-350 nits on the PG248QP, which is already pretty good, is with ULMB 2.0 on. Without it the monitor can display over 400 nits which is way enough.
And this new eTN panel is already excellent without BFI, I wouldn't even bother using BFI on it and prioritize a lower input lag + better brightness. That's why I am definitely looking forward the Acer XV242F, it would also allow me to save a few hundreds euros (Asus is overpriced in Europe + extra euros for GSync module...).