Mebbe it's just time to bite the bullet on physics and move on.
So we go from an open and well documented API (DirectX) to a company (MS) having to actually write hardware level drivers for a company for it to be considered open?
As far as I know, Nvidia hasn't made PhysX open or well documented with regards to other company's writing drivers in order to interface with it just as well as their own do.
Nor have I seen Nvidia approaching this in an open manner in order to embrace all hardware and thus expand it's area of influence (Direct3D for example). And considering it's a Proprietary system I wasn't expecting them to. Thus it's not exactly an open standard now is it?
Rather, Nvidia has done everything in their power to make sure it remains a closed and proprietary system (CUDA) while making vague PR blurbs to suggest their rivals could make a driver for it if they wished.
Regards,
SB
So we go from an open and well documented API (DirectX) to a company (MS) having to actually write hardware level drivers for a company for it to be considered open?
And why would you do that if your AMD, so you can have "better" explosions in GRAW... at a big frame drop?. Or to have some cloth move in a robotic manner with a frame drop...This whole "debate is getting way off the mark. PhysX will be come a in game CP Chk box option to see some extra something that will drop you 5 to 10 frames... meh the CPU will rule them all in no time... With Intel and AMD with no loss of frames at all.....
PhysX sdk is available for free, if those extentions are exported or mapped to another language like Open Cl or Brook, it will work on AMD hardware, of course they will still have to create a driver on top of that too.
Raises hand.Mebbe it's just time to bite the bullet on physics and move on.
Mebbe it's just time to bite the bullet on physics and move on.
And why would you do that if your AMD, so you can have "better" explosions in GRAW... at a big frame drop?. Or to have some cloth move in a robotic manner with a frame drop...This whole "debate is getting way off the mark. PhysX will be come a in game CP Chk box option to see some extra something that will drop you 5 to 10 frames... meh the CPU will rule them all in no time... With Intel and AMD with no loss of frames at all..
The guy's crazy as a coconut ... no way in hell does AMD want a PLX->IL/microcode translation layer to support PhysX, it's a fools errand. NVIDIA can't really get burned here, they just let him rant spend and 5 minutes on e-mail ... best case he actually finishes the work and it performs exactly as good as is possible ... which is awful. Most likely case he never gets there, but still nothing lost. AMD can get burned here, best case he never finishes the work worst case he does.Nvidia actually did help out with an independent effort sometime ago, but I'm sure someone will explain why that was just a PR stunt.
A Source near the German magazine Ct says that nvidia will launch the DX11-Chip in October with availability in November.
In the Print release, said one member in the 3DCenter-Forum. Havent read the current release myself.Where does it say that? I can only see older links to Inquirer bullshit in their newsticker.
In the Print release, said one member in the 3DCenter-Forum. Havent read the current release myself.
Now please list the PC games that use Havok and have the kind of PhysX realism that games using PhysX has. I've yet to see one game using Havok that does, IE box window dressing.
Please list the games that use PhysX realistically, aside from window dressings by adding bits of moving eye-candy.
Half Life 2? Throwing a buggy around in the air beats symmetrically moving banners.
Red Faction Guerrilla ...