From the info this article gave, it does not render G-sync obsolete. It sounds like it will introduce a 16.7ms of latency on 60hz monitors, and it may also slightly disrupt the time sequence (though not sure on that either).I think the real question now is. Are you willing to drop the money on a garbage TN panel in the short term to get Gsync and lock yourself to nvidia hardware based on that monitor?
Or do you wait until display port 1.3 monitors come out and render gsync obsolete. I would imagine Nvidia GPU's are going to support vblank in dp1.3 once it is ratified. Considering how long I tend to keep a monitor vs. a GPU I'm willing to wait a while and see what happens.
If DP 1.3 is ratified in 60-90 (from the PC Per article) days I would imagine panel makers will adopt the spec quite fast because of the onslaught of 4K and its need for a better display standard.
I think the real question now is. Are you willing to drop the money on a garbage TN panel in the short term to get Gsync and lock yourself to nvidia hardware based on that monitor?
Or do you wait until display port 1.3 monitors come out and render gsync obsolete. I would imagine Nvidia GPU's are going to support vblank in dp1.3 once it is ratified. Considering how long I tend to keep a monitor vs. a GPU I'm willing to wait a while and see what happens.
If DP 1.3 is ratified in 60-90 (from the PC Per article) days I would imagine panel makers will adopt the spec quite fast because of the onslaught of 4K and its need for a better display standard.
I think the real question now is. Are you willing to drop the money on a garbage TN panel in the short term to get Gsync and lock yourself to nvidia hardware based on that monitor?
Or do you wait until display port 1.3 monitors come out and render gsync obsolete. I would imagine Nvidia GPU's are going to support vblank in dp1.3 once it is ratified. Considering how long I tend to keep a monitor vs. a GPU I'm willing to wait a while and see what happens.
If DP 1.3 is ratified in 60-90 (from the PC Per article) days I would imagine panel makers will adopt the spec quite fast because of the onslaught of 4K and its need for a better display standard.
Yes. Thank you for providing a better clarification I could ever do.Well, I got what Erenhardt meant
snip
Yes. Thank you for providing a better clarification I could ever do.
All this G-sync\free-sync looks like a pig with a bow tie and not a proper solution. And while it is hard (at least for me) to bash a free features, nv is a big offender here, asking $100 for a beta sub-solution.
The original article made it sound like it may be free on some laptops, but made no mention of monitors. I imagine things are different on how the monitors interface with the GPU. I don't honestly know.So AMD's is literally the same thing as Nvidia's. :|
Then what was with the "software overhead" BS that guy wrote in his article?
I wonder when Hawaii based boards will support displayport 1.3. 60-90 days. I dont' think you understand how standard committees work. Standards don't get ratified that quickly. Will the 290 and 290X even work with these DP 1.3 monitors?
AMD told you free-sync wouldn't require hardware. Seems that free-sync requires a monitor logic board and that is not part of the DP 1.3 standard. So you tell me. Is this logic board free? Will panel makers include it? Keep in mind that it isn't part of the DP 1.3 standard thus far. Do you trust AMD to do the legwork and get this logic board into monitors?
Seeing as they already lied to you about being a 100% software solution. Guess what. That isn't the case. They're using a controller board just like nvidia. Like I said. What AMD tells you and what they do are different things. AMD's marketing is not to be trusted. This is a prime example of that.
PCPer has a story on this BTW:
http://api.viglink.com/api/click?fo...VIDIA-G-Sync&jsonp=vglnk_jsonp_13892033092116
You should give that a good read, it sheds some light and truth on free-sync not being "Free".
All that is needed for this to work, as AMD explained it, was an eDP connection between the discrete GPU and the display, a controller for the screen that understands the variable refresh rate methods of eDP 1.0 specifications and an updated AMD driver to properly send it the signals. The panel can communicate that it supports this variable refresh technology to the graphics card through the EDID as resolutions and timings are communicated today and then the graphics driver would know to send the varying vblank signals to adjust panel refresh times on the fly.
Freesync will not be free. And it will not deliver the same experience.
I cant really see any (good) solution that doesnt require a large buffer. Either on the GPU or the monitor.
Even 290X will not support freesync, even if we imagined you got the monitor.
There's a simple solution that doesn't require a buffer, and AMD is doing it - they predict how long the frame will take. And 290X will not support freesync? Why not? AMD says it's a firmware update for the extra display connectivity tech, and the VBLANK control is already built into the driver. Please, share why you're CERTAIN that it cannot work.
No offense, but you're the AMD employee, you tell us why it will be certain to work when:
1) PCPer stated - per Kurjari - that new monitor logic boards are required.
2) Displayport 1.3 is not supported by Hawaii
Put simply, your statements do not reconcile with Kojuri's (#1). And he is the head GPU engineer at AMD from what I understand.
I just feel confused here. You told us that you're affiliated or employed by AMD. With that being the case, why don't you contribute and actually tell us something of worth?
I don't know if you work with Warsam - he posts in the CPU forum frequently, and is an AMD employee. Yet he discloses that fact in his sig. Anyway, his agreement with moderators is that he cannot serve as a PR/advertisement mouthpiece, and must get approval prior to posting such threads. I don't know if that same applies to you, but i'm not sure if everyone is aware that you're affiliated/employed by AMD. Warsam's posting conditions were dictated by Idontcare and jvroig. I'm not sure if you underwent the same vetting process that warsam did, but it sounds like you didn't. You're also not disclosing your employment in a sig, either. Which I feel would be great, since you're the AMD guy - you could be a valuable resource for those who have questions. You could be a valuable resource. What isn't valuable, with all due respect, is a PR/advertising mouthpiece. Nobody is interested in that. Jvroig stated such to Warsam when he was being vetted as an AMD rep.
As far as I see it, you're the AMD guy, why are you putting the burden of proof on US? Do you understand how ridiculous that is? I don't mean any disrespect or anything, but I really feel that you should be coming to us with information in this respect and if you don't have anything to share, why bother with rhetorical questions? I mean you're from the source. You're working with AMD.
When asked about a potential VESA standard to enable dynamic refresh rates, Petersen had something very interesting to say: he doesn't think it's necessary, because DisplayPort already supports "everything required" for dynamic refresh rates via the extension of the vblank interval. That's why, he noted, G-Sync works with existing cables without the need for any new standards. Nvidia sees no need and has no plans to approach VESA about a new standard for G-Sync-style functionality—because it already exists.
Nvidia responds to free sync demo:
http://techreport.com/news/25878/nvidia-responds-to-amd-free-sync-demo
If you aren't familiar with eDP, don't feel bad. It's a connection type used in tablets and notebooks and isn't used at all in desktop configurations (some all-in-one designs do use eDP). But here is where it might get interesting: the upcoming DisplayPort 1.3 standard actually includes the same variable refresh rate specification. That means that upcoming DP 1.3 panels COULD support variable refresh technology in an identical way to what we saw demoed with the Toshiba laptops today. DP 1.3 is on schedule to be ratified as a standard in the next 60-90 days and from there we'll have some unknown wait time before we begin to see monitors using DP 1.3 technology in them.
All these solutions require monitors and GPU to behave differently than they do now. They require tech to allow new techniques to be used. These new technologies must also be compatible with the old technologies. Perhaps someday in the future they can get rid of the backward compatibilities, but we aren't there yet.Why not just have the LCD monitor hold the image till the GPU sends a bit telling the monitor it is time to refresh. Now this would only work up to a certain max refresh rate then you run into problems( though could use VSync for max refresh rate.) but below that it would work just fine. Seems like that wouldn't be a problem to implement.
I don't know if you realize this or not, but I added that link to the OP about 12 hours ago.![]()
All these solutions require monitors and GPU to behave differently than they do now. They require tech to allow new techniques to be used. These new technologies must also be compatible with the old technologies. Perhaps someday in the future they can get rid of the backward compatibilities, but we aren't there yet.
This is what they are doing, but with a few complications.If all that is done now is the monitor simply draws what is in the GPU frame buffer every refresh rate. The only change for the GPU would be to send an extra bit of information when the frame buffer is changed. Now the monitor controller would be a larger change. But with what they can already do it with variable refresh rates it shouldn't be a problem.
Both could be backward compatible with no problem.