KazeoHin
[H]F Junkie
- Joined
- Sep 7, 2011
- Messages
- 9,004
I'm waiting for the mature driver that supports single-cards and eyefitity.
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.
I'm waiting for the mature driver that supports single-cards and eyefitity.
I actually don't know what's wrong with his setup- I'm expecting him to come back and tell us what's wrong.
I'm fairly sure there's a mismatch regarding outputs between a GTX690 and three 4MP panels. My only other point is that it's an awful idea- the card is ill-equipped for that setup, as one GTX690 is barely enough for a single 2560x1600 monitor, and the card only has 2GB per GPU.
only certain games suffer from runt frames/micro stutter with CFX, and even then it's only with VSYNC disabled. Crysis 3 doesn't have any issues with VSYNC disabled, but Sleeping Dogs is absolutely terrible. Same with Far Cry 3, awful...
yeah, you have a single 6970. The drivers are for crossfired cards. It's all in the release notes.
Supports WHAT on single cards? Lawl, there aren't any real issues (besides maybe FC3?) on single cards, what do you want it to fix
Not a CPU problem, I can assure you of that. It's exclusive to AMD cards as far as I can tell (tested on an HD 5850, HD 5870, and HD 6970).This fix worked for this guy. Other people are saying it's a CPU problem, low CPU utilization causing the CPU to go into idle states, maybe disabling power states in the BIOS would fix it.
This driver does not work for Eyefinity.
running 5400x1920 and this driver is a no go.
Waiting patiently for this driver to work for Eyefinity peeps.
Not a CPU problem, I can assure you of that. It's exclusive to AMD cards as far as I can tell (tested on an HD 5850, HD 5870, and HD 6970).
Didn't have these hitching problems on my old GTX 260, nor do I have them on my new GTX 780.
That was exactly my point. My 7970 spans my 3 30" monitors just fine and doesn't fight me at all, the nvidia drivers tell me to fuck off because even though all 3 monitors are 25x16 @60hz "they are not the same resolution".
And as soon as the new drivers fix crossfire for eyefinity I'll be buying a 2nd 7970.
Tried turning AA off in-game, no difference on the 6970. Didn't really expect that to make a difference considering only FXAA was enabled (which is just a shader). MSAA was off.See above ^^^ did you read the link? Disable AA in game, try forcing it through CCC instead.
Tried turning AA off in-game, no difference on the 6970. Didn't really expect that to make a difference considering only FXAA was enabled (which is just a shader). MSAA was off.
Only thing I've found that helps AMD cards in Skyrim is using a framerate limiter (and this doesn't 100% eliminate the hitching, but it does reduce it massively). Unfortunately, using such a limiter causes internal engine sync issues that cause some seriously glitchy behavior after playing for a while.
Techreport said:For a time, Nvidia still held an edge in our latency-focused tests, until AMD addressed some issues with its drivers and recaptured the lead.
I literally have a machine with an HD 6970 (and one 1920x1200 monitor) right next to a machine with a GTX 780 (and three 1920x1200 monitors in Surround) both running Skyrim.Skyrim is pretty good these days. Both that and Fallout 3 is much smoother on my 7970 then my GTX 570 ever was. More GPU power, but still ...
Quite possible it's only fixed for 7000 series cards. Wouldn't be the first time AMD has left older cards for deadI haven't tried the 6970 series from AMD, but single 7970 is smooth as butter in games.
I literally have a machine with an HD 6970 (and one 1920x1200 monitor) right next to a machine with a GTX 780 (and three 1920x1200 monitors in Surround) both running Skyrim.
The computer with the 6970 is hitching, the computer with the GTX780 is not.
Swapping the cards between machines = the problem follows the AMD card.
Quite possible it's only fixed for 7000 series cards. Wouldn't be the first time AMD has left older cards for dead
Edit: Looks like this driver doesn't help a single 7970 much either, check out its frame times in Tomb Raider and compare them the single GTX 680 in the table. The 7970 shows variance, even though it's not in a crossfire config. Looks like single-card systems are still in need of fixes.
So when are they going to fix the horrible stuttering that single-cards are still dealing with
Phase 2 of the driver will come later this month. In Phase 2 CrossFire in Eyefinity resolutions will be supported. There will also be support for DX9 and OGL games in Phase 2. So if you game in Eyefinity, or across multiple displays, or higher resolutions than 2560x1600 then Phase 2 driver is what you will have to wait for. Also, if you want support in DX9 games.
Nope, I'm comparing to the Nvidia results.Look at the picture again. The light one is Fraps, the other one is FCAT. I think you are reading the info wrong.
Nope, I'm comparing to the Nvidia results.
Nvidia shows no variance in either test, AMD shows pretty horrible variance in one of the two tests. There's still a huge difference in how these cards are getting frames rendered, even if AMD is trying to fix it or mask it.
Above Hitman Absolution with the very same AMD GPU and drivers. Notice how all the weird spikes are gone? That's the advantage of FCAT, you record what you see on screen and this is in line with what we see on the monitor. So what does that say about FRAPS ? Yeah, it indeed can show a lot of stuff that really isn't there and perhaps vice versa. That doesn't mean though it is recording non-exsistant stuff, contrary. But is is inserting and leaving out stuff we can not observe visually.
http://www.guru3d.com/articles_pages/fcat_benchmarking_review,1.htmlBeing trendy - websites jumped onto it and are using FRAPS, but the thing is... if you want to expose game stutters you probably should not use FRAPS. Here's why:
Nope, I'm comparing to the Nvidia results.
Nvidia shows no variance in either test, AMD shows pretty horrible variance in one of the two tests. There's still a huge difference in how these cards are getting frames rendered, even if AMD is trying to fix it or mask it.
I know the difference between FRAPS and FCAT, just not seeing how it's relevant to the point I've made.Read up on fraps vs. FCAT:
I know the difference between FRAPS and FCAT, just not seeing how it's relevant to the point I've made.
Nvidia's results still seem to be far better than AMD's here, considering Nvidia's results don't show a problem ANYWHERE in the chain, where as AMD's do.
Not trolling, pointing out a pretty obvious difference...Lol, the only part of the chain which is showing problems is buggy, irrelevant, and not visible to the end user. pleaaaaaase, troll harder
If you'd look at what I was pointing out it might make a bit more sense. There's obviously something still causing high levels of variance the pipeline on AMD and it's masked by the time FCAT gets hold of it.Seriously, statements like "AMD is trying to fix or mask it" is crap that doesn't belong here.
I know the difference between FRAPS and FCAT, just not seeing how it's relevant to the point I've made.
Nvidia's results still seem to be far better than AMD's here, considering Nvidia's results don't show a problem ANYWHERE in the chain, where as AMD's do.
So above two example FRAPS Frametime recordings. You'll agree with me that when looking at the Radeon HD 7790 you'd expect a downright horrible game experience. The problem with FRAPS is this, it can show stuff that is not relevant - most of these weird spikes you see do not relate to what you see on-screen. So the interesting thing is that once you play and visually look at the games being rendered by say AMD, you (for the bigger part) just might not notice or see the latency spikes.
If you'd look at what I was pointing out it might make a bit more sense. There's obviously something still causing high levels of variance the pipeline on AMD and it's masked by the time FCAT gets hold of it.
I never said it showed up in the output, I simply said it was there... which it is.I don't think you do understand the difference. You are speaking of a variance that doesn't even show up on output.
Only conclusion I drew, and pointed out, is that AMD's hardware is still showing high levels of variance in 1 out of 2 tests, while Nvidia shows it in 0 out of 2 tests. Nothing more, nothing less.drawing conclusions without understanding the software =user error.
I never said it showed up in the output, I simply said it was there... which it is.
Unknown-One said:Looks like this driver doesn't help a single 7970 much either, check out its frame times in Tomb Raider and compare them the single GTX 680 in the table. The 7970 shows variance, even though it's not in a crossfire config. Looks like single-card systems are still in need of fixes.
Again, nowhere there did I say it appears in the output, just that I still think single-card configurations need some fixes.But you did say:
When it clearly shows this driver makes the output very smooth on the single 7970 and doesn't need to be fixed.Looks like this driver doesn't help a single 7970 much either, check out its frame times in Tomb Raider and compare them the single GTX 680 in the table. The 7970 shows variance, even though it's not in a crossfire config. Looks like single-card systems are still in need of fixes.
I see variance and still assume there's a problem, one AMD has masked in software by the time FCAT results are generated (which means smoother visuals, but doesn't necessarily mean everything is all rosy). Treating the symptoms is a good start, fixing the root cause is better.You saw a variance, assumed this was a problem (even though the same image shows you this wasn't a problem for the driver to handle) and went on a spree saying the driver needs to be fixed.
Again, nowhere there did I say it appears in the output, just that I still think single-card configurations need some fixes.
I see variance and still assume there's a problem, one AMD has masked in software by the time FCAT results are generated. Treating the symptoms is a good start, fixing the root cause is better.
I'd like to see the entire pipeline operate better, even if they've managed to make the final output appear smoother.
You answered your own question. I'd like to see them fix this early in the pipeline rather than late.Fix what? As explained to you by me and also by the links I gave you from Guru3d, FRAPS captures very early in the pipeline.
Never said it was relevant to gameplay... where are you getting this stuff from? I'm pointing out a difference, I find the current solution to be sub-optimal, and I'm hoping AMD improves their implementation. The fact that it doesn't work in DX9 titles or in high resolutions / eyefinity is already a major downside that they have yet to address.What happens there may or may not be relevant to the actual gameplay.
I'm looking at the results from both FRAPS and FCAT to point out a pretty obvious difference in implementation. I'm talking about lower-level issues than simple "gameplay experience"On the other games in the same review you linked to, there is less varation also for AMD cards. What you need to look at, is FCAT.
FRAPS isn't confusing me, I'm using its results compared against FCAT to determine that AMD solves the metering problem much later in the pipeline than Nvidia. Simple as that.Fraps only confuses you as seen in this thread and makes you see problems that are not there (kinda like guru3d explained FRAPS captures vs. FCAT).
Of course there's masking going on, you can see it in the results. There's high variance early in the pipeline and there's low variance late in the pipeline. The variance has been masked.There is no masking going on. The driver handles this game very well and gives a great and smooth output.
Like I said at the top of this post, solving this late in the pipeline is asking for additional complexity. Additional complexity means the potential for more bugs and additional difficulty in supporting features (we're already seeing API limitations as is...)Even between drivers of the same vendor, you see variations on how it handles different games. Don't worry about that, unless you are creating drivers yourself. Its the output that matters.
You answered your own question. I'd like to see them fix this early in the pipeline rather than late.
Sure there is, because AMD's solution seems so software-driven that it doesn't work AT ALL in most games... Nothing OpenGL or DX9 is helped as of yet.There is nothing to fix as long as FCAT shows a smooth output.
I never said the game would be smoother if they were similar... again, not sure where you're getting that from.That you OCD on some difference between a fraps capture of present and FCAT output, is getting tiresome. If they would be similar, the game would not be smoother. It doesn't make any difference other then it worries you. Try to forget you saw the FRAPS output.
Except it doesn't work in most games on the AMD side of things... at least not yet. That's highly troubling, and tells me AMD's results are never going to be as consistent with how they've implemented their fix.AMD and Nvidia doesn't approch every single game the same way, not even between drivers. As long as the mojo works, it works and there is nothing to fix.
Sure there is, because AMD's solution seems so software-driven that it doesn't work AT ALL in most games... Nothing OpenGL or DX9 is helped as of yet.
They're working on it, but if they have to fix this per-API (or worse, per-game) then it's sub-optimal from an implementation standpoint.
Like I said earlier, just because FCAT comes out clean (in the games that AMD's solution actually works on) doesn't mean their solution is optimal. I'm not complaining about the on-screen results (when it works), I'm complaining about the implementation.
I never said the game would be smoother if they were similar... again, not sure where you're getting that from.
I said I don't agree with AMD's implementation and pointed out several issues I take with it. Nothing more.
Except it doesn't work in most games on the AMD side of things... at least not yet. That's highly troubling, and tells me AMD's results are never going to be as consistent with how they've implemented their fix.
...one more time. I never said it was relevant to the on-screen end-result. How many times do I have to say it?Don't OCD on the Fraps difference vs. FCAT. Its pointless and as mentioned several times from me and guru3d, fraps can sometimes show things that are not relevant to the output.
It's obviously an issue, because we're still waiting for them to actually make it work, at all, on most games... and I'm fairly positive it's because of how high-level AMD's solution is. If the lack of a low-level fix is what's holding them up, that's hardly "nothing"...This is not an issue and we have both waisted a lot of time discussing something you found irregular and didn't understand, making a big fuzz over nothing.