AMD: "[Developers use PhysX only] because they’re paid to do it"

Because only Fanboys will buy such a "closed" system. All the other people will go with a intel system.
Maybe you should join AMD's PR Team...

WOuldn't only fanboys buy a closed system of Nvidia video cards in which you need two of them to do any meaningful physx in games ?


See I can throw the fanboy word around also. I'm so cooo l!:cool: even got the cool smiley to prove it.:oops:
 
WOuldn't only fanboys buy a closed system of Nvidia video cards in which you need two of them to do any meaningful physx in games ?

Wait: nVidia cards are a "closed system" with their PCIe? :oops:
The last time i checked the features you can use the cards in any PCIe-16x slot, you can run OpenCL and DC applications and the two main graphics apis. But yeah, it's a "closed system" because you can only use nvidia-only features with a nvidia card... :???:
 
Why is that ? The board will still ship with pci-e slots. They will just support a maximum of 1x
a)If the chipset supports only 1x, then the 5970 will also be capped at 1x.


b) If it was possible, rest assured INtel would have done it and launched larrrabee. :???:

c)If the chipset unlocks to 16x for amd while throttling intel/nv to 16x, that will be breaking the PCIe spec, while having the sticker. IOW, nv has parts with PCIe 16x stickers, AMD has chipsets with 16x stickers, which is why when you mate one to the other, they have to work together. Please do not think any of PCI-SIG members' lawyers are that big idiots. I do not have access to their contracts, but I can guarantee you that all members swear not to play dirty when you mate to parts with identical stickers. That's what makes these groups work.

SLI is a sw hack, one level over PCIe, so they are free to play dirty there.
 
Amd and intel arlready have their own sockets that are not compatible with anything else. Why can't AMD say oh we have a hypethread slot esp for our graphics card.

Did you think that through? So AMD is going to make chipsets that only work with its graphics cards and graphics cards that only works with its chipsets and in doing so hands the entire desktop PC market over to Nvidia? Nice plan.

PhysX adds value for Nvidia's customers. What value does a proprietary peripheral interface add when it does exactly the same thing that an existing widely adopted standard does?

It is, however, comparable to :

- disabling SLI on non-nVidia chipsets (oh, wait... that's a common use of a standard hardware interface!)
- disabling "PPU" PhysX when display adapter is not from nVidia (again, common use of a standard hardware interface)

I must have missed the announcement of industry standards for hardware and software to accelerate physics or to enable multiple gpu rendering. SLI is not a "common use" of anything, it is a proprietary feature of Nvidia hardware and software.

SLI is a sw hack, one level over PCIe, so they are free to play dirty there.

Exactly.
 
And you have proof of that slanderour bite at Nvidia concerning B:AA and the AA code they gave them?


I didn't think so.

Sure...

http://www.hexus.net/content/item.php?item=20991

Last bit down at the bottom there. Eidos was legally prohibited by Nvidia from removing the VendorID lock despite the fact that they wanted to remove it for the good of their customers. That e-mail was also published elsewhere but I don't have time currently to do a proper google search for it.

Also reference various threads about end users removing the VendorID to enable working in game AA on ATI cards which triggers the games DRM preventing the user from saving their games.

Reference also that AMD attempted multiple times to enable in game AA both before and after the games release.

Also various articles mentioning Nvidia's "proprietary" IP protected AA method used in Batman: AA is amazingly similar to standard methods of providing AA for the rendering method used.

Regards,
SB
 
Sure...

http://www.hexus.net/content/item.php?item=20991

Last bit down at the bottom there. Eidos was legally prohibited by Nvidia from removing the VendorID lock despite the fact that they wanted to remove it for the good of their customers. That e-mail was also published elsewhere but I don't have time currently to do a proper google search for it.

Also reference various threads about end users removing the VendorID to enable working in game AA on ATI cards which triggers the games DRM preventing the user from saving their games.

Reference also that AMD attempted multiple times to enable in game AA both before and after the games release.

Also various articles mentioning Nvidia's "proprietary" IP protected AA method used in Batman: AA is amazingly similar to standard methods of providing AA for the rendering method used.

Regards,
SB

"Eidos’ legal department" does not equal Nvidia.

"It’s also worth noting here that AMD have made efforts both pre-release and post-release to allow Eidos to enable the in-game antialiasing code - there was no refusal on AMD’s part to enable in game AA IP in a timely manner."

And that is pure bullshit from Mr. Huddy as Eidos is on record as saying They refused to help.
 
Last edited by a moderator:
After deleting and editing a few posts, I just want to remind you all that we should try to keep things civil here.
 
"Eidos’ legal department" does not equal Nvidia.

"It’s also worth noting here that AMD have made efforts both pre-release and post-release to allow Eidos to enable the in-game antialiasing code - there was no refusal on AMD’s part to enable in game AA IP in a timely manner."

And that is pure bullshit from Mr. Huddy as Eidos is on record as saying They refused to help.
After Eidos retracted the Tomb Raider: Angel of Darkness patch that included the nvidia embarassing benchmark, I am not inclined to believe a word they say.

This has happened time and time again from members of the TWIMTBP program (DX10.1 support removed, patches retracted, etc.) and yet somehow ATI/AMD is at fault for this?

Open your eyes.

-FUDie
 
http://www.pcgameshardware.com/aid,...Nvidia-responds-to-AMDs-attack-on-Physx/News/


So did PCGH or Nvidia rephrase that claim to something completely different, that it much easier for nvidia to answer? Seems way below PCGH's normal standards, and more like both question and answers were coming from NV PR.

This snippet from the answer to the seconded question could be more true.

"We have been told that some AMD spokespeople talk about PhysX being like 3DFX's GLIDE API - that's even more of inaccuracy analogy, games written for GLIDE simple would not run on any system without a 3DFX card"

The original Unreal and UT games needed over 40 patches just to get OGL and DX to work. If you had 3DFX, yuo had nothing to worry about. ATI, Nvidia, S3, Trident, Intel or whoever, you hoped the next patch would get the game to work right. And they sued CL over the Glide rapper they wrote for the GeForce256 line. It worked great, hell, even worked better than OGL or DX at the time they wrote it.
 
After Eidos retracted the Tomb Raider: Angel of Darkness patch that included the nvidia embarassing benchmark, I am not inclined to believe a word they say.

This has happened time and time again from members of the TWIMTBP program (DX10.1 support removed, patches retracted, etc.) and yet somehow ATI/AMD is at fault for this?

Open your eyes.

-FUDie

Keep believing what you are being fed then. It's still crap even if it is ATI feeding it to you.
 
Keep believing what you are being fed then. It's still crap even if it is ATI feeding it to you.
So you deny that Eidos retracted the TRAOD patch? Revisionist history at it's best. This patch was available for download and was benchmarked, then it was removed and future patches didn't include the benchmark. How convenient for nvidia. Let's not forget the Assassin's Creed DX10.1 patch that was scrapped.

It's not ATI shovelling the bull here.

-FUDie
 
Let's not forget the Assassin's Creed DX10.1 patch that was scrapped.
It's not ATI shovelling the bull here.

-FUDie

It was AMD which worked together with ubisoft. And it was ubisoft decision to remove the path. Maybe AMD should do a better work with the devs.


"Ubisoft are at the forefront of technology adoption, as showcased with the fantastic Assassin’s Creed title. In this instance our developer relations team worked directly with the developer and found an area of code that could be executed more optimally under DX10.1 operation, thus benefiting the ATI Radeon HD 3000 Series."

http://www.rage3d.com/articles/assassinscreed/index.php?p=5
 
Last edited by a moderator:

I don't know if this is random blub or a freudian error:

Once PhysX is selected and the developer plans to have a PC version, we will work closely with them to provide whatever engineering and technical assistance to make the PC version as good as it can be ...

They help only PC developers, but not console developers? Are PC developers less capable? Or are they the only ones with GeForces (thus GPU PhysX)? Do non-PC games have PhysX-halo?

Don't want to read to much into it though ...
 
Back
Top