OK guys, I've put the monitor through its paces this weekend, if you can't be bothered to read it all, end of the day it's awesome, buy one! Oh and don't fiddle with NV inspector settings!
Bit of a background, I had the x34 and it went back, mainly due to g-sync scan lines - games used to test at the time and were affected were Tomb Raider 2013, Alien Isolation and Dying Light. For some reason I couldn't see any issues with Elite, Rust, ARK or Act of Aggression, probably because Elite is dark and the others are low FPS. Other problems were coil whine, IPS glow and disappointment with general build quality.
OK so my point is I've been pretty anal with testing this thing, particularly the g-sync flicker.
I spent most of Sat basically trying to look for problems. First of all, I set up the same as was on the x34 test by setting the fps cap to 95 in NV inspector and v-sync to force off (more on this later) as this should force g-sync to engage. I turned on the monitors inbuilt fps counter to compare to steams - with g-sync is on, the two should...well.. sync and both read 95!
No flickering at all in Alien and DL, BUT TR 2013 DID flicker and took me ages to figure out why - unlike the other two, this has an in-game monitor refresh rate setting which I also set at 95hz. I eventually realised this sets the MONITOR speed, not the graphics card (and should have been left at 100). With no difference between the two values and with v-sync off, if the g-card fps were to exceed the monitor by a slight amount, I simply wouldn’t notice. Either upping the in-game refresh rate, or lowering the NV cap to increase the distance between the two values solved it. I then spent ages trying to recreate the flickering with other settings and other games with no success under the cap and then purposely allowed the g-card fps to exceed the monitor which induced flicker - so I proved the statement from Nvidia's website the long winded way that turning v-sync off and allowing the refresh rate to exceed the monitor's will induce flicker.
I then experimented turning g-sync on and off and here’s the interesting thing. In NV inspector, the default setting for v-sync is "3D application settings", BUT turning g-sync on overrides this to "force ON". I've since concluded that this is for good reason (from above), the v-sync is basically acting as an fps cap for g-sync and I'm pretty certain even at max, it's g-syncing, not v. Cut a long story short, don't faff about with fps caps etc, just stick to the defaults!
To further prove there was no flicker and this wasn't just v-sync masking it all (I still wasn't settled in my head!), I set fps caps to 60-80 fps with no problems in multiple games. I then removed the fps cap (so everything back to default, remember v-sync is still force on), but then disabled SLI so games ran at roughly the same rate, again, no problems, smooth as butter!
I then played MGS V pretty much all day Sun, even with SLI on, this game ran at around 66-100hz all the time, pretty much sitting at about 80 and rarely hitting 100hz. Therefore, g-sync was constantly on - no flickering at all! Turning g-sync off, god WHAT A DIFFERENCE! You don't realise it until it's not there!
The IPS glow isn't a problem, even on dark games like Elite and Alien, I would only notice it on loading screens and when I purposely looked for it.
No coil whine at all, running at 70% brightness for a good 8-10 hours constant
Basically chaps, in my experience this is a cracking screen!
EDIT:
Some more pics
http://i1308.photobucket.com/albums/s602/hadri1983/20160212_214343_zpshnxlpwps.jpg
http://i1308.photobucket.com/albums/s602/hadri1983/20160212_212618_zps3mua2utk.jpg
http://i1308.photobucket.com/albums/s602/hadri1983/20160212_212608_zpswcpgb4sw.jpg
