• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

What AMD does vs WHat nVidia does...

AMD has some crappy drivers and you can end up with more cpu overhead if using an AMD gpu especially with their slow cpus. The results in Dead Rising 3 are just bizarre to say the least.

look how a 290x is much more cpu limited and just shits itself when using lower end cpus
http://s12.postimg.org/8lfhw1n71/cpu_amd.jpg

the 780 Ti though is much more playable with the weaker cpus and flies with the i3 and above
http://s17.postimg.org/jw6t2sefz/cpu_nvidia.jpg

This is due to the fact that Nvidia's drivers support both of DirectX 11's new multi-threading features, namely Differed Contexts and Command Lists (AMD only supports Differed Contexts). This allows Nvidia's drivers to better-leverage multi-threading.

Conspiracy theory, not to be taken seriously: Is AMD artificially inflating the overhead of DirectX 11 in order to make Mantle look better on low-end APUs?
 
As someone said before... nVidias need for special drivers for every major game release is a sign of weakness in the gpu architecture imo...

1) NVidia doesn't need drivers for every new release and most of the time it's for SLI support


2) You're confusing good game support with lack of good game support. AMD cards need drivers just as often as NVidia. The only difference is that AMD cards don't get drivers as often as NVidia.


The someone else that mentioned this, is making up random stuff based on noting more than his/her own bias.
 
I used to get my panties in a twist over brands back (early 2000's) in the day. Then I grew up, spent money more wisely and grew tired of the arguments.

I don't ever being very brand loyal on computers. I've had Abit, DFI, Gigabyte, MSI and Asus MBs. I've had Intel, Cyrix (yes Cyrix) and AMD CPUs. I've had generic, S3, 3DFX (briefly...sold it to a friend who did SLI), Nvidia (Riva something or other), ATI and the last 2 were Nvidia (though I still use the ATI too).

Buy whatever works for you. There have been times when ATI/AMD kicked Nvidias butt. I'm not sure if that's happened in the last 5 or so years or not, but I hope it happens again. Competition is good. God knows we'd be better of if AMD could put out competitive chips like the old Athlon's and Athlon 64s. Hell, if businesses had just adopted the 64 when they were the best chip, things would be so different today.
 
I don't ever being very brand loyal on computers. I've had Abit, DFI, Gigabyte, MSI and Asus MBs. I've had Intel, Cyrix (yes Cyrix) and AMD CPUs. I've had generic, S3, 3DFX (briefly...sold it to a friend who did SLI), Nvidia (Riva something or other), ATI and the last 2 were Nvidia (though I still use the ATI too).

Buy whatever works for you. There have been times when ATI/AMD kicked Nvidias butt. I'm not sure if that's happened in the last 5 or so years or not, but I hope it happens again. Competition is good. God knows we'd be better of if AMD could put out competitive chips like the old Athlon's and Athlon 64s. Hell, if businesses had just adopted the 64 when they were the best chip, things would be so different today.

It doesn't really matter when AMD is ahead in price/performance. Nvidia has a ridiculous following of loyal fans who don't particularly care. AMD just isn't good enough no matter what. AMD dominates some segments right now.

This is due to the fact that Nvidia's drivers support both of DirectX 11's new multi-threading features, namely Differed Contexts and Command Lists (AMD only supports Differed Contexts). This allows Nvidia's drivers to better-leverage multi-threading.

Conspiracy theory, not to be taken seriously: Is AMD artificially inflating the overhead of DirectX 11 in order to make Mantle look better on low-end APUs?

They're just moving forward. The versions of windows that have directx 11 are going to be freely upgraded to windows 10 with dx12. They already are improving multithreading there
 
1) NVidia doesn't need drivers for every new release and most of the time it's for SLI support


2) You're confusing good game support with lack of good game support. AMD cards need drivers just as often as NVidia. The only difference is that AMD cards don't get drivers as often as NVidia.


The someone else that mentioned this, is making up random stuff based on noting more than his/her own bias.

AMD cards do not need drivers as often. Its called superior architecture. Even pascal will be heading GCN route.
 
It doesn't really matter when AMD is ahead in price/performance. EDIT: Both Camps have a ridiculous following of loyal fans who don't particularly care. AMD just isn't good enough no matter what. AMD dominates some segments right now.

Now corrected your post to get rid of the flame bait, the rest of your post where do they dominate? I see no segment where they dominate in recent history (past 3 gens), and this shows up in marketshare figures too, when AMD had product that can match or beat nV in comparative bullet points their marketshare went up. Look at the 4xxx and 5xxx generation, they grabbed marketshare from nV.


They're just moving forward. The versions of windows that have directx 11 are going to be freely upgraded to windows 10 with dx12. They already are improving multithreading there
This happens for both camps, but AMD seems to be in the lead for now but both camps drivers are still raw.
 
Last edited:
AMD cards do not need drivers as often. Its called superior architecture. Even pascal will be heading GCN route.


Thats BS, what happened to every month WHQL release? nV was the one that was releasing less drivers in the past, at least WHQL, which actually costs money to release.

It was funny when AMD was releasing monthly drivers many people were touting that and were complaining nV wasn't, now its flipped around because AMD hasn't been able to do that?
 
Thats BS, what happened to every month WHQL release? nV was the one that was releasing less drivers in the past, at least WHQL, which actually costs money to release.

It was funny when AMD was releasing monthly drivers many people were touting that and were complaining nV wasn't, now its flipped around because AMD hasn't been able to do that?

I think it's silly regardless of who does it. With GCN I don't think they need to as much as they did with 5000 and 6000 series but monthly drivers don't impress me unless there are some significant performance gains. The "Up to" claims never really pan out.

With nvidia, the WHQL thing might be for fringe hardware that requires WHQL drivers. The actual certification is neither here nor there. Their WHQL drivers were giving people crashes and restarts. Some people had to go to older drivers
 
https://www.youtube.com/watch?t=130&v=GZ19JCTOGfI

Eg. of why gameworks is the suck. TressFX usable on consoles, hairworks kills titans.
The "TR Remastered Edition" used some watered-down version of TressFX 2.0 which looked like shit.
So most likely the Crapbox One is using a watered-down version of TressFX 3.0. Being an E3 demo they probably have everything cranked to 11.

On the PC version of TR, TressFX murders fps for everyone.
 
The "TR Remastered Edition" used some watered-down version of TressFX 2.0 which looked like shit.
So most likely the Crapbox One is using a watered-down version of TressFX 3.0. Being an E3 demo they probably have everything cranked to 11.

On the PC version of TR, TressFX murders fps for everyone.

I was playing with tressfx on with a q9300 and a HD5770 with good fps. That game, like most AMD games, simply ran well.

As far as looks, just check the vids. Looks good especially with snow on it. It's also on the animals at the same time. Minimum that means its running pretty well.

Also with dx12 they might end up with minimal impact for turning it on with asynchronous shaders, Which nothing for nvidia below maxwell 2 has.
 
I was playing with tressfx on with a q9300 and a HD5770 with good fps. That game, like most AMD games, simply ran well.

As far as looks, just check the vids. Looks good especially with snow on it. It's also on the animals at the same time. Minimum that means its running pretty well.

Also with dx12 they might end up with minimal impact for turning it on with asynchronous shaders, Which nothing for nvidia below maxwell 2 has.


Hey look explain to me how asynchronous shaders well help with tessellation and the GCN architecture vs nV's SMM architecture.
 
They're just moving forward. The versions of windows that have directx 11 are going to be freely upgraded to windows 10 with dx12. They already are improving multithreading there
Uh, what? That doesn't fix the problem at all.

That just means new DX12 games will run with low-overhead. All existing DX11 titles will continue to run in DX11 mode, and continue to thread better on Nvidia drivers as long as AMD doesn't support DX11 command lists, even on Windows 10.
 
Last edited:
Hey look explain to me how asynchronous shaders well help with tessellation and the GCN architecture vs nV's SMM architecture.

I never said it would help with tessellation?? They've improved tessellation separately from that. Why are you even mentioning tessellation?
 
you were talking about tressfx and how asynchronous shaders might help with minimal impact with it on in DX12.......

under a specific game that tressfx for hair that uses tessellation. I want to see how your thinking before I comment on it.
 
Last edited:
you were talking about tressfx and how asynchronous shaders might help with minimal impact with it on in DX12.......

under a specific game that tressfx for hair that uses tessellation. I want to see how your thinking before I comment on it.

I was thinking they could do the physics calculations more efficiently by running them parallel to the graphics elements. Should be obvious that's what I meant.
 
I believe TressFX uses the directcompute Microsoft standard, and is relatively light on system resources.

Also all AMD GCN GPUs support asynchronous shaders, but nvidia only now has Maxwell which supports it, any nvidia GPU below Maxwell cannot do async shaders which will be a big deal with DX12 and VR.
 
ok look man read this thread lots of good stuff in there, its not one of those cure alls that you seem to like to talk about for AMD hardware. I don't really like to go off topic too much

https://forum.beyond3d.com/threads/asynchronous-compute-what-are-the-benefits.54891/

If I thought it was a cure all I wouldn't have said no to the tessellation. If you are wanting to say it will do nothing, then that's just wrong. It will help with somethings.

is there or are there particular posts that show what you intend?
 
If I thought it was a cure all I wouldn't have said no to the tessellation. If you are wanting to say it will do nothing, then that's just wrong. It will help with somethings.

is there or are there particular posts that show what you intend?


I'm not saying it has no help, depending how how a program is made makes a huge difference with async shaders.

there are many posts in there that are relevant,

Just simplifying a lot because this topic will get very complex, think of async shaders like hyperthreading.

Graphics related tasks are already very parallel in how work is done on the gpu. Where async shaders help is when the CPU is waiting for the GPU to finish a task. So things like physics or things that use compute, will get a boost when using them.
 
Thats BS, what happened to every month WHQL release? nV was the one that was releasing less drivers in the past, at least WHQL, which actually costs money to release.

It was funny when AMD was releasing monthly drivers many people were touting that and were complaining nV wasn't, now its flipped around because AMD hasn't been able to do that?

nVidia used to have less driver-dependent hardware... That has changed, and thus so has the conversation...

Hard to understand?

(ps If any person here said one thing back then and now says another, you have a point... But dont blindly lump me or others into groups of people that foolishly defended AMDs need for more frequent drivers, and then act like we have switched stances... 'back then' I would have been anti-driver-dependency too, and hating on AMD for it)
 
nVidia used to have less driver-dependent hardware... That has changed, and thus so has the conversation...

Hard to understand?

(ps If any person here said one thing back then and now says another, you have a point... But dont blindly lump me or others into groups of people that foolishly defended AMDs need for more frequent drivers, and then act like we have switched stances... 'back then' I would have been anti-driver-dependency too, and hating on AMD for it)


No they are actually now similar, AMD is using a VLIW SMID, AMD's GCN architecture was made for compute performance in mind, as with nV's when they made Fermi. Kelpar's architectural changed to some what wider then Fermi which is where Kepler was able to do more with less.

Edit:

They are both scaler architecture now this is what makes them good compute architectures, now how it pans out in the future we will see. We weren't really talking about the which drivers were doing more based on architecture
 
Last edited:
Back
Top