Soldato
- Joined
- 19 Feb 2007
- Posts
- 15,835
- Location
- Sol
Seems good so far but then again I play like 3 games XD
Last edited:
Please remember that any mention of competitors, hinting at competitors or offering to provide details of competitors will result in an account suspension. The full rules can be found under the 'Terms and Rules' link in the bottom right corner of your screen. Just don't mention competitors in any way, shape or form and you'll be OK.
I think the VVR OLED flicker issue is monitor related. on my aw3423dwf I used to get it with gsync on, but with this new MSI 360 I don't get it, saying that I don't run gsync anymore on this monitor as it really isn't needed.Installed the new Studio via NVapp. All's good innit. Gsync is left off as usual, VRR Flicker on OLED is still an issue in certain games and GPU accel apps like Photoshop.
Only full gsync ultimate could deal with it apparently, as the full Nvidia module is needed, perfectly tuned to that panel on each frequency. The cheap scallers they put into most monitors these days don't have such fancy abilities, that's why flickering with vrr will never go away till that gets improved - or so I've seen few times posted by industry insiders over the years. This flicker happens on all panels but oled are fast enough to make it much more visible than IPS or TN etc.Yeah implementation will play a part, the newer firmware shave improved it but it's still there on gen 3 QD-OLED even is less than previous FW versions.
It's all about the cost, Nvidia used expensive FPGA as that was easier than producing specialist chips for relatively small number of such monitors on the market. Now we have panels produced with cheaper scallers but definitely with trade offs.But yes at 240Hz it's a non issue being off anyway. Gsync has always been a bit iffy ever since Nvidia ditched the dedicated Gsync Ultimate format I think going by online comms.
Something in you system might be locking it (maybe even AV or some silly anticheat, can't trust those modern kernel level ones) or your OS is partially corrupted.Has anyone been having a weird issue where they have to reboot to install a graphics driver recently? I've never had this issue until the past 3-4 driver releases. If I try to install it after I've been using the PC for a while the graphics driver just says "failed" on the installation summary. Rebooting seems to clear whatever the issue is and it installs fine. I've even tried shutting all my current open windows to make sure nothing is using the graphics card. So odd.
I think if the OS was the issue it would lock me out of installing it completely. I'm kind of assuming it probably is some background software that's doing it. I might try doing a DDU too though.Something in you system might be locking it (maybe even AV or some silly anticheat, can't trust those modern kernel level ones) or your OS is partially corrupted.
If you have recent enough Windows 11, you can do simply repair using Windows Update option - it just reinstalls all of your OS but imports all settings etc. back to it (sans very custom stuff that is against MS defaults, like telemetry turned off etc.). It takes on my machine 15 minutes or so in summary and every time I messed up my OS (I played with it a lot in the past) it always recovered to fully working state and I did not have to reinstall anything.I think if the OS was the issue it would lock me out of installing it completely. I'm kind of assuming it probably is some background software that's doing it. I might try doing a DDU too though.

Yeah I've done repairs in the past so I'm not too worried about doing it. Just kind of would like to see exactly what the issue is for future reference so gonna do things one at a time and see what works. Just slow since I've gotta wait for another driver update, not bothered enough to go installing old drivers and testing since i'm not having any other issues.If you have recent enough Windows 11, you can do simply repair using Windows Update option - it just reinstalls all of your OS but imports all settings etc. back to it (sans very custom stuff that is against MS defaults, like telemetry turned off etc.). It takes on my machine 15 minutes or so in summary and every time I messed up my OS (I played with it a lot in the past) it always recovered to fully working state and I did not have to reinstall anything.![]()