Yes but don't buy those things, you can't use the frame doubling below the min range with this monitor. You need the max range >= 2.5 * min range for frame doubling to work. But for a simple firmware update it is pretty awesome, of course.
Announcement
Collapse
No announcement yet.
It Looks Like AMD Will Support FreeSync With Their New Linux Display Stack
Collapse
X
-
Originally posted by duby229 View Post
The trekkies already got me with this one..... It's not Vulkan, It's Vulcan!
Just kidding. Don't let nvidia fanboys get under your skin, most of them lack basic fundamental common sense.
It seems some people got it, that's nice
Comment
-
Originally posted by Namenlos View Post
Since November AMD implemented frame doubling, so if your higher freesync range is 2.5 times the lower, the lower one does not matter. Same with NVidia, though I do not know if they double their frames in soft- or hardware. Once you are above the max monitor refresh range you have either vsync off, which results in tearing (and somewhat lower latency/input lag) or you have it on, which results in a tear free display (with an input latency of max 16ms at 60Hz) - so if you stay above the monitor refresh rate both adapive syncs technologies don't differ from non adaptive sync approaches.
Comment
-
Originally posted by jf33 View PostThanks for the information. What about dri2?
I actually tried counter strike go with dri3 offloading just now and it is much better. There is still bad tearing, but it seems the second huge problem - old (sometimes *very* old) frames being inserted randomly seems to be gone. Possibly since https://cgit.freedesktop.org/xorg/dr...ff10fb94d395fa.
- Likes 1
Comment
-
Originally posted by atomsymbol
How is that different from sending 2 images to the display every 16.6ms when I configure FRTC to 30Hz (33.3ms) and the display is at constant 60Hz?
adaptive refresh rates > fixed refresh rates
When your card can do an average of 70 fps, even w/ frtc, you won't get that perfect frame times, taking each frame exactly 16.66 ms to render and display. Taking the rendering of frame 0 20 ms and for frame 1 13 ms is no big deal with a synchronised display. It is with a fixed frame rate: you get tearing w/ v-sync off or stutter w/ v-sync on.
You can't just calculate your frame times out of your average fps. Average fps is an extremely smoothed out, useless value, when it really comes to the feeling of the visuals. Frame times do always differ, for some games it is worse, for some not a big deal, but they are always unsteady.
If you render 99 frames, each in 9 ms (~"111 fps") and one frame takes 100 ms (~"10 fps") you have one really bad stutter but still an average of ~101 fps. This big difference is of course exaggerating, if there is no memory shortage, reload/streaming issue or something like that, but that's how it works.Last edited by juno; 15 February 2016, 06:56 PM.
Comment
-
People keep talking as though fs is limited to a min refresh of 40hz.
Maybe that's all the current crop of monitors support but the standard is much more flexible.
- Likes 2
Comment
Comment