Blur Busters Forums

Guys, I bought Acer 390hz currently. I have flicker problem at 390hz. At first it was working fine, but a few minutes later it started. Is this a problem with my drive or a problem that can happen with any drive? I tried most of the solutions in the thread, but the only one that really seems to have worked is: I went back to 360hz by disabling OC in the OSD, I created a custom resolution in the NVIDIA panel, I set it to 390hz, I set the timing to "Manual" and that's it, no I changed none of the timings that NVCP gave me, and then the flicker stopped. Has anyone used it like this? Do you know if that way would work "worse" than the original way of the monitor without custom resolution at 390hz? Can this change anything regarding inpug lag or response time?

A second very lay question, how do I know if the VBR is working correctly? If I point my phone's camera, should I see it blink?

.

The only problem is that I got the second hand monitor and they don't sell this model new in my country anymore. The tip of creating custom resolution and leaving the timing on "manual" in NVCP seems to have solved it. Should I be concerned? Will I have the same performance? If I had the same performance I would have nothing to worry about.

What I did was go into the custom resolutions and see what timings they were giving me on automatic with the monitor's default OC settings. Then I went back to 360hz by turning off the OC in the OSD, I created a custom resolution of 390hz with the same timings and polarity settings and I tested it and everything worked, after that I left the OC on the monitor on. The monitor didn't blink even once, no ficker so far. I'll leave the print of how the custom resolution turned out. This print is of the timings I got through "390hz native monitor". Then I created a custom one with manual times and put the same settings.Could I be missing something by this regarding the "overclocked native" 390hz of the monitor itself? Is there any way to improve further? Thanks

.

BTRY B 529th FA BN wrote: ↑

29 Jul 2023, 08:04

Seen my first 2 flickers with this second RMA, lol

lol acer is full of shit.. there is no way they did anything to it with the 2nd RMA repair.. it came back sooner than I thought too

it hasn't even been running for more than an hour and it's flickering worse and worse now

EDIT: taken down and getting ready for a 3rd RMA.. captured video of the flickering but this time I opened up Windows Time and Date in the lower right hand corner so their "technicians" can see it's still having issues; issue captured July 29th by video with proof provided, smh

Are you trying the third unit of the XV252Q and all fickered? What bad luck! Did you even try to create custom resolution at 390hz and manual timing in NVCP as I said in my previous answer? Did they even blink?

Crazy you have had all these issues...

Feel bad for you, but I will say this monitor for the $$ is absolutely insane, mine of course works flawless. Hopefully you can get one that works perfect for you. I hope you look back and atleast did what I said to do, if you have already then I guess the panel is bad!! Good luck

Yeah that sucks, sorry you have continued issues. I have had 3 of these monitors and 1 of them did have the same problems you have, but they were evident before the return window was up so I was able to return it and get it replaced.

Yesterday I went to test playing without the custom resolution with manual times in NVCP, I tried again the "native" 390hz OC way of the monitor and it didn't blink, strange, but I know that any time it will blink, at least that's what I feel lol. Yesterday was a cold day, and the monitor is next to the window, could this have any explanation? I just wanted to try to feel if there would be less Input Lag that way, because it is "native" and with the times of the monitor itself and not the ones I set in the NVCP, honestly I can't say if I felt a difference. Anyway, I'm playing Valorant poorly on this monitor compared to my old Alienware AW2518HF (freesync model). But I still haven't convinced myself that the monitor is the problem, maybe it's just faster than my Alienware and I need to get used to not passing the aim on enemies. I also didn't play for 5 days before changing the monitor, maybe that's it, I'll test more.

One thing I noticed, on the desktop while I'm working it doesn't blink, in Valorant it practically doesn't blink, at least it hasn't blinked lately, if it blinked it was one time or another. In COD, perhaps because it is a heavier game, it blinked a lot at 390hz, it wouldn't blink if it had a custom resolution with manual timing in NVCP. Does this have something to do with the temperature of the monitor or video card? Or I can just leave the custom resolution with manual timing in NVCP and get rid of it forever, at 390hz. But I'm afraid I'm losing some monitor performance in "native" 390, either for some different timing than it is in "native OC" mode.