Pixio PX329 is working perfectly.
Slightly off topic but how do you like that monitor? It’s been one I’ve kind of had an eye on for a bit and now that you say it works perfectly with Nvidia’s implementation I am very interested in it.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Pixio PX329 is working perfectly.
Slightly off topic but how do you like that monitor? It’s been one I’ve kind of had an eye on for a bit and now that you say it works perfectly with Nvidia’s implementation I am very interested in it.
Am I the only guy running a 1080Ti on a g-sync monitor but doesn’t give a fuck nor use it?
Uncap my FPS and boom, no fucks given about g-sync.
You must love tearing. But seriously, you've never even turned it on? Why not? G-Sync doesn't even add latency.
Never turned it on. Never felt the need to try it, never bugged me.
I have the 27” Dell 1440p 144hz 1ms gaming monitor. Forgot the model # sdg27r or some crap.
So you spent an extra $100+ on a monitor for a feature you never turned on or used... That just doesn't make good sense.. but each to there own I guess.
Sounds like you did not pay careful attention to the beginning of the installation. You are first given a driver or driver with geforce experience option. The geforce experience is the default so you must have simply clicked on "agree and continue" without noticing it.Did anyone else have the GeForce experience greyed out so you had to install it? This is the first time this has happened.
Am I the only guy running a 1080Ti on a g-sync monitor but doesn’t give a fuck nor use it?
Uncap my FPS and boom, no fucks given about g-sync.
honestly it was a bit of a pain to enable freesync with my amd gpu.
Looks like joker productions put something up. Did not watch it yet.
How so? Alt+R "click Freesync on".
Should we run with vsync on or off?
Does nvidia enable "software/GPU" LFC when going below freesync range?
That flies in the face of everything i have read.
Ok so he has freesync enabled
He has vsync enabled
He says if he goes below the freesync range of his monitor, he gets tearing
He says he enables vsync to cap frames.
Now based on what i have read (im no expert), you do not enable vsync when you have a gsync/freesync enabled. It defeats the purpose.
The other thing i thought was odd in his video, is he says he sees tearing when below freesync range. Now i have 2 problems with that. First is he has vsync on, so he should NEVER have tearing. Second is I assumed nvidia enabled LFC when running a monitor that has a VRR ratio of at least 2.4x, just like AMD, this would mean again zero chance of tearing. VRR via gpu would kick in and start duplicating frames based on an algorithm.
So if we have any "experts" out there:
Should we run with vsync on or off?
Does nvidia enable "software/GPU" LFC when going below freesync range?
Oopy Doopy3 hours ago (edited)
Edit: Did more research, you should enable v-sync globally in the nvidia drivers. Nvidia does indeed do something funky. Optimally, you enable v-sync in the nvidia drivers and then set a framerate cap (optimally with an in-game limiter) 2 frames below your refresh rate to minimize input lag. You should not use v-sync. If you want your fps capped, you could: A: Use Nvidia Inspector to set a global cap or a per application cap B: Use Adaptive v-sync. This caps your framerate at your refresh rate and syncs to the display, and drops v-sync when you dip below the refresh rate. (I suspect this is what Joker intended to do but misunderstood/forgot) C: Use rivatuner to cap the fps (this is the lowest input lag option, but requires additional software to run with all your games) Maybe nvidia does something with the driver to change the way v-sync works when g-sync is running, but if not then turning on v-sync completely negates running g-sync/freesync. You'll get that v-sync stutter at variable framerates because....well, v-sync is running. Having run some games with v-sync on and g-sync on, the stutter is real and honestly it seemed worse than v-sync w/o g-sync. I haven't used driver level v-sync though. I imagine your experience will vary from system to system and monitor to monitor, but with my setup, v-sync + g-sync is awful, g-sync + framerate cap is A+. https://www.blurbusters.com/gsync/gsync101-input-lag-tests-and-settings/6/
You sure it’s not turning on by default? I have that Dell monitor and it likes to automatically enable itself whenever I install the Nvidia drivers.
Positive. Because I’d go in there and make sure it’s off.
And also the fact that I’m seeing above 200fps in the games I play would also confirm.
I have not a single FreeSync display in any of our offices currently.How about existing freesync monitors you have? It will be nice to hear your professional opinion for this new feature from Nvidia.
I really hope someone with a "gsync compatible" monitor (xg270hu for extra points) tests it and reports back their findings. I am curious if the vrr range is different when using a nvidia card. I have been waiting on the 7nm Vega, but could be tempted to buy a 2080 instead depending on how things turn out.
Sounds like you did not pay careful attention to the beginning of the installation. You are first given a driver or driver with geforce experience option. The geforce experience is the default so you must have simply clicked on "agree and continue" without noticing it.
Yeah how dare I try to point out what you may have done wrong. And what you are saying now shows that you cant even pay attention here no better than when you were installing the drivers as AGAIN the part where you messed up was at the very beginning before you even get to the custom install option.Sounds like you made a wild ass assumption. I always custom install and uncheck everything but the driver's.
Sounds like you made a wild ass assumption. I always custom install and uncheck everything but the driver's.
Maybe get someone to help you next time as these drivers install just fine without GFE if you click on what you are supposed to...I fixed my issue by reverting back to the old driver's. Even tried to reinstall the garbage they put out today. Even clicked the first option back and forth multiple times to make sure. You know the install with GeForce or not option.
Now based on what i have read (im no expert), you do not enable vsync when you have a gsync/freesync enabled. It defeats the purpose.
That flies in the face of everything i have read.
Ok so he has freesync enabled
He has vsync enabled
He says if he goes below the freesync range of his monitor, he gets tearing
He says he enables vsync to cap frames.
Now based on what i have read (im no expert), you do not enable vsync when you have a gsync/freesync enabled. It defeats the purpose.
The other thing i thought was odd in his video, is he says he sees tearing when below freesync range. Now i have 2 problems with that. First is he has vsync on, so he should NEVER have tearing. Second is I assumed nvidia enabled LFC when running a monitor that has a VRR ratio of at least 2.4x, just like AMD, this would mean again zero chance of tearing. VRR via gpu would kick in and start duplicating frames based on an algorithm.
So if we have any "experts" out there:
Should we run with vsync on or off?
Does nvidia enable "software/GPU" LFC when going below freesync range?
Oopy Doopy3 hours ago (edited)
Edit: Did more research, you should enable v-sync globally in the nvidia drivers. Nvidia does indeed do something funky. Optimally, you enable v-sync in the nvidia drivers and then set a framerate cap (optimally with an in-game limiter) 2 frames below your refresh rate to minimize input lag. You should not use v-sync. If you want your fps capped, you could: A: Use Nvidia Inspector to set a global cap or a per application cap B: Use Adaptive v-sync. This caps your framerate at your refresh rate and syncs to the display, and drops v-sync when you dip below the refresh rate. (I suspect this is what Joker intended to do but misunderstood/forgot) C: Use rivatuner to cap the fps (this is the lowest input lag option, but requires additional software to run with all your games) Maybe nvidia does something with the driver to change the way v-sync works when g-sync is running, but if not then turning on v-sync completely negates running g-sync/freesync. You'll get that v-sync stutter at variable framerates because....well, v-sync is running. Having run some games with v-sync on and g-sync on, the stutter is real and honestly it seemed worse than v-sync w/o g-sync. I haven't used driver level v-sync though. I imagine your experience will vary from system to system and monitor to monitor, but with my setup, v-sync + g-sync is awful, g-sync + framerate cap is A+. https://www.blurbusters.com/gsync/gsync101-input-lag-tests-and-settings/6/
For G-sync to function correctly (frame time variance compensation) you need to enable vsync for the application, either in the game or from the driver. Anecdotally a lot of games vsync options don't play as nicely as the driver level vsync in my experience (especially Destiny 2's in game vsync, that thing causes all kinds of frame time issues), so I've taken to forcing it from the control panel for my games. G-sync will still remove the latency from the double/triple buffering bellow the monitors max refresh rate.
The cap still works, it's just the frame delivery time that gets out of whack.huh? I thought it was a general concession you have gsync and freesync so you don't have to deal with vsync lol. Never used vsync with my freesync monitor works flawless.
Now Maybe it's a different story if you are using 60hz monitor. But Gsync is suppose to automatically cap fps at 144 or 145.
This update led to recurring confusion, creating a misconception that G-Sync and v-sync are entirely separate options. However, the "Vertical sync" option in the control panel actually dictates whether, one, the G-Sync module compensates for frametime variances (see "Upper Frametime Variances" in "G-Sync Range" section), and two, whether G-Sync falls back on fixed refresh rate v-sync behavior; if v-sync is "On," G-Sync will revert to v-sync behavior above its range, if v-sync is "Off," G-Sync will disable above its range. Within its supported range, G-Sync is the only synchronization method active, no matter the v-sync setting.
...
UPPER FRAMETIME VARIANCES
V-Sync Off: G-Sync remains engaged, tearing may begin at the bottom of the display, no additional input latency is introduced.
The tearing seen at the bottom of the display (example: ) in this relatively narrow range, is due to frametime variances output by the system, which will vary from setup to setup, and from game to game. Setting v-sync to "Off" disables the G-Sync module's ability to compensate for frametime variances, meaning when an affected frame is unable to complete its scan before the next, instead of suspending the frame long enough to display it completely, the module will display the next frame immediately, resulting in a partial tear. Not only does v-sync "Off" have no input latency reduction over v-sync "On" (see “G-Sync Input Latency & Optimal Settings”), but it disables a core G-Sync functionality and should be avoided.
V-Sync On: G-Sync remains engaged, module may suspend frames, no additional input latency is introduced.
This is how G-Sync was originally intended to function (see “G-Sync & V-Sync”). With v-sync "On," the G-Sync module compensates for frametime variances by suspending the affected frame long enough to complete its scan before the next, preventing the tearing seen at the bottom of the display in the “V-Sync Off” scenario above. Since this operation is performed during the vertical blank period (the span between the previous and next frame scan), it does not introduce additional input latency (see “G-Sync Input Latency & Optimal Settings”).
That flies in the face of everything i have read.
Ok so he has freesync enabled
He has vsync enabled
He says if he goes below the freesync range of his monitor, he gets tearing
He says he enables vsync to cap frames.
Now based on what i have read (im no expert), you do not enable vsync when you have a gsync/freesync enabled. It defeats the purpose.
The other thing i thought was odd in his video, is he says he sees tearing when below freesync range. Now i have 2 problems with that. First is he has vsync on, so he should NEVER have tearing. Second is I assumed nvidia enabled LFC when running a monitor that has a VRR ratio of at least 2.4x, just like AMD, this would mean again zero chance of tearing. VRR via gpu would kick in and start duplicating frames based on an algorithm.
So if we have any "experts" out there:
Should we run with vsync on or off?
Does nvidia enable "software/GPU" LFC when going below freesync range?
Oopy Doopy3 hours ago (edited)
Edit: Did more research, you should enable v-sync globally in the nvidia drivers. Nvidia does indeed do something funky. Optimally, you enable v-sync in the nvidia drivers and then set a framerate cap (optimally with an in-game limiter) 2 frames below your refresh rate to minimize input lag. You should not use v-sync. If you want your fps capped, you could: A: Use Nvidia Inspector to set a global cap or a per application cap B: Use Adaptive v-sync. This caps your framerate at your refresh rate and syncs to the display, and drops v-sync when you dip below the refresh rate. (I suspect this is what Joker intended to do but misunderstood/forgot) C: Use rivatuner to cap the fps (this is the lowest input lag option, but requires additional software to run with all your games) Maybe nvidia does something with the driver to change the way v-sync works when g-sync is running, but if not then turning on v-sync completely negates running g-sync/freesync. You'll get that v-sync stutter at variable framerates because....well, v-sync is running. Having run some games with v-sync on and g-sync on, the stutter is real and honestly it seemed worse than v-sync w/o g-sync. I haven't used driver level v-sync though. I imagine your experience will vary from system to system and monitor to monitor, but with my setup, v-sync + g-sync is awful, g-sync + framerate cap is A+. https://www.blurbusters.com/gsync/gsync101-input-lag-tests-and-settings/6/
This goes back to when G-SYNC first came out and people were bitching about G-SYNC capping your framerate automatically, so NVIDIA made the cap optional with V-Sync. Without V-Sync enabled you can have unlimited FPS with G-SYNC, but of course G-SYNC doesn't operate outside of the max refresh rate.I was always under the impression that you turn Vsync off if you're using adaptive sync (Freesync / Gsync). When he turned on Vsync that kind of confused me because if you enable adaptive sync, the framerate doesn't exceed the Hz limit, which is tied to the frame rate.
They fixed the crashing a long time ago with one of the first 400 series drivers.I wonder when Gears of War 4 players can upgrade from 385.82 to prevent non stop crashing?
Read my reply to Krenum above. AMD never made this change to FreeSync.huh? I thought it was a general concession you have gsync and freesync so you don't have to deal with vsync lol. Never used vsync with my freesync monitor works flawless.
Now Maybe it's a different story if you are using 60hz monitor. But Gsync is suppose to automatically cap fps at 144 or 145.