First AMD FreeSync Capable Gaming Displays and Drivers Launched, Tested
MojoKid writes Soon after NVIDIA unveiled its G-SYNC technology, AMD announced that it would pursue an open standard, dubbed FreeSync, leveraging technologies already available in the DisplayPort specification to offer adaptive refresh rates to users of some discrete Radeon GPUs and AMD APUs. AMD's goal with FreeSync was to introduce a technology that offered similar end-user benefits to NVIDIA's G-SYNC, that didn't require monitor manufacturers to employ any proprietary add-ons, and that could be adopted by any GPU maker. Today, AMD released its first FreeSync capable set of drivers and this first look at the sleek ultra-widescreen LG 34UM67 showcases some of the benefits, based on an IPS panel with a native resolution of 2560x1080 and a max refresh rate of 75Hz. To fully appreciate how adaptive refresh rate technologies work, it's best to experience them in person. In short, the GPU scans a frame out to the monitor where it's drawn on-screen and the monitor doesn't update until a frame is done drawing. As soon as a frame is done, the monitor will update again as quickly as it can with the next frame, in lockstep with the GPU. This completely eliminates tearing and jitter issues that are common in PC gaming. Technologies like NVIDIA G-SYNC and AMD FreeSync aren't a panacea for all of PC gaming anomalies, but they do ultimately enhance the experience and are worthwhile upgrades in image quality and less eye strain.
"that didn't require monitor manufacturers to employ any proprietary add-ons, and that could be adopted by any GPU maker." -- I definitely like the general idea here, but NVIDIA trying to do lock-in and squeeze even more money out of people with requiring proprietary add-ons is only going to hurt the market; it forces manufacturers to choose either camp limiting markets, or both camps increasing costs. It's bullshit. NVIDIA should work with AMD and the other manufacturers on this, not against them.
Vsync prevents the frame from being written to while it's displayed, avoiding tearing. FreeSync/Gsync makes the monitor wait for the frame to be rendered and ready for display instead of the other way around.
Live today, because you never know what tomorrow brings
Now, if AMD linux drivers could really not suck, that would be awesome.
Because their drivers are crappy. Their FOSS driver is crappy and their propiertary driver is crappy. They are really putting the cart before the horse here. What they really need to do, is just a massive bug hunt with their drivers. Right now they are lacking.
Oh, and its hurting sales, because people won't buy AMD cards because they are known to be buggy. Even after they fix them, its going to take a lot of them to be seen as reliable.
Is this an oblique reference to the sync'ing of the Bismark?
Got them moderator blues I blieve I walk out the do', With these mod-points I been gettin', I 'most never post no mo'
Vsync keeps a frame from being written to the monitor until the monitor is ready for it. Say for example, your card can generate 70 FPS and your display is clocked at 60 FPS, your card will draw a frame, wait for the end of the previous frame, send the newest frame, then start generating the next frame. You lose out on the extra 10 fps that your card could be producing. On the other hand, if you run up against a heavy scene and your card's capability drops to 59 fps, it will take more than a single refresh to draw a frame, so your card re-sends the last frame while it waits for the current frame to finish, finishes the current frame, then sits around waiting for the re-sent frame to finish drawing. You eliminate tearing, but effectively drop to 30 fps. If your engine works a bit different and starts drawing the next frame ahead of time instead of waiting, you get jitters where several frames draw smoothly but eventually catch up with the buffer and stutter while a frame is skipped.
Gsync, on the other hand, moves the waiting to the monitor side. A frame is drawn to the monitor as soon as it is complete. If you're producing frames faster than the max refresh rate, your card might still stop and wait while the frame is being sent, but if your framerate drops, you don't end up in a buffer-skip cycle. Instead of sending every frame by the clock, the card sends the frames as they finish, and the monitor doesn't refresh until it receives the full frame, regardless of whether it produces the full 60 FPS or a lower rate. This wouldn't work well with a CRT since every line has to be refreshed every cycle to maintain constant brightness and minimize flicker, but it works well with flat panel displays where each element is updated simultaneously only when the refresh signal is sent.
I've got a 24" monitor that's 10 yeas old and it's native resolution is1900x1200. Why the regression in recent years back to 1080? You'd think monitors today would have continued advancing. Sure, give them 1080 capability, but still they should have a much higher native resolution by now.
"On a scale from 1 to 10, people are stupid"
Dell U2412M, U2413, U2415 are all 24" monitors with 1920x1200 screens.
Or you can jump up to 27" 2560x1440, 30" 2560x1600 or even 34" 3440x1440
Or you can go to a 4K screen or even a 5K one.
Playing a video with breasts in motion is actually one of the best ways to check for screen tearing issues... :)
Do what thou wilt shall be the whole of the Law