Vrr flicker is still there. Quickest and easiest way to tell: open Lagom black level page whilst at 175hz. Take notice of the first few squares. Change monitor to 60hz, and you will see that the same first squares are raised slightly compared to 175hz.
World first QD-OLED monitor from Dell and Samsung (34 inch Ultrawide 175hz)
- Thread starter Grim5
- Start date
It's definitely active because I enabled the refresh rate monitor overlay through the monitor at the same time to check and it was matching the framerate I was getting (which is anything from 100-175 depending on area, it's not the most optimised/efficient game). You can see it's definitely g-sync flicker because the on-screen refresh rate drops suddenly down to around 100-120 from 170+ when the "flicker" happens. It's to do with the games poor load in. It seems to cause frame time spikes for a split second while it streams in assets. I haven't found a mod to solve it either. It's a very extreme case admittedly.
The condition is unsteady framerates, especially quick frame drops. Sometimes a game that flickers at release due to frame drops or bad frame pacing, can become flicker free due to optimisation meaning better frame pacing and the elimination of frame drops. Others may see flicker in a game, that doesn't happen for you, due to their pc struggling with pacing more than your own config.
In the lagom test I described a couple of posts back, the fact that the first boxes are raised slightly at 60hz vs 175hz proves the flaw isn't fixed. The vrr flicker is manifested from that issue.
I get that but something has obviously been fixed or improved as we have several people here saying they don't see the same flickering they had before the firmware update.
Yep. Even if not fully fixed. It is a huge improvement. To the point I don't see the small things I saw in select games. I'll take it
I'm still seeing it. I'll give it some time. I bought the monitor after many claims from owners that it didn't exist on the new qdoled, as it was fixed because of the gsync module. Even asked people to do the lagom test. I bought it and it was there, then slowly after some time opinions swapped from "it doesn't have vrr flicker" to "ok yes I have now experienced flicker".
I don't think anyone on here has ever said it wasn't there? At 175hz, it was much more noticeable, at 144hz less so (which is why some like @mrk kept using 144hz instead), I found the same experience too with 144 vs 175, couldn't really see it too much with 144 but immeditately noticeable with 175hz.
Be good to get more people posting on it though as perhaps there could be some combination of settings or/and hardware affecting it.
For what it is worth:
- only have this display connected to my 3080
- vsync on, low latency turned to ultra in NVCP with gsync on for both windowed and fullscreen
- latest game ready nvidia drivers with the hotfix
- no fps caps anywhere
Last edited:
Yeh happened in here, it was within the first weeks of release. Mrk was the first to acknowledge my test and saw the raise between 175 and 60. Even just in the last page someone claimed its fixed. I just point out that it isn't, as there maybe others like myself who already used OLED vrr for a few years, are happy but read that these new screens have fixed the biggest issue, only to be disappointed. On other forums when I first discovered the raise on the LG c9, it took nearly a year for people to acknowledge it (the raise, not flicker as vrr and 120hz didn't become available for a year due to no HDMI 2.1 gpus out yet). In the OLED screen boom of the last few years, I feel those inky blacks are so impressive that small flaws get easily overlooked.
If after a couple of weeks, I notice it has overal reduced, ill be sure to give an update, but from initial impression yesterday mine still has the same flicker in scenarios that trigger it.
I tried your lagom black test there and yes in 60hz mode, the first 2 black squares are slightly raised but I'm not sure how or what this means with regards to the flickering?
All I know is, literally before the monitor firmware update, the flickering you could see with 175hz in these scenarios:
- xbox gamepass open fullscreen with discord open to one side
- remnant 2 first mission after entering the red crystal (light/dark grey cloud)
- hogwarts, in the forbidden forest at night
- starfield on planets with dark grey setting
- menu/loading screens
Flickering is gone now, at least on my end.
Is there any other games, tests, areas where it shows for you? I don't have oblivion so won't be able to test it.
Man of Honour
Gsync only needed for full screen not windowed, you may find instances where WIndows spazzes out as some apps don't play ball with gsync being forced outside of fullscreen 3D. Windows DWM itself won't ever render above the refresh rate anyway or below it so no need for it to ever be on for anything outside of fullscreen.
Also I did some extended research and low latency mode can be left off as it's a lgacy setting that has no bearing for modern Gsync/VRR displays.
I've gone back to native 10-bit too btw, just prefer the peace of mind of native 10-bit, plus it's 144Hz so not a huge loss from 175Hz.
I just keep it on now as so many games aren't true fullscreen even when they say fullscreen, especially with dx 12 titles, most games are actually borderless fullscreen. Of course, you could set it on per profile per game basis but too much faff.
Low latency is good for titles not dx 12 and where reflex isn't included, it also acts as a fps limiter too when used in such titles. Reflex on will always override low latency setting though.
Last edited:
Good lad. This is how I feel too. Even though everyone says 8bit is fine. I find 144hz is plenty for my needs. Something about using 8 bit feels wrong to me
I tried 175hz for a bit and thought, I can't see the difference. Will just enable it for Counter Strike in game and that's it I recon.
Even better than mrk keep finding excuses to send his monitor back hoping to get one back with newer firmware?
The flicker is a manifestation of the near black raise you see in the lagom test. The further the hz is from 175 the more the near black raise.
For example: If you play a game with a steady 60fps, you won't see flicker but your near black will be raised. If you play a game that has bad frame pacing or frame drops, as the fps bounces around the near black will look like it is flickering eg bouncing from 175 to 100 quickly. The near black at 100 is different to 175, and as it happens quickly it will look like flicker to the eye.
This is also why people find 144hz makes it undetectable to their eye. By reducing the framerate you are raising the near black ever so slightly, meaning the range for the bad frame pacing is reduced.
Last edited:
Rtings have updated measurements on input lag:
Not sure what their figures were before though.
Did you read the whole thing? It literally shows you
