![]() |
|
|||||||
| General Graphics ATI centered discussions do not belong in here. Discussion forum for graphics hardware provided by NVIDIA, Matrox, S3, Intel and anyone else who isn't ATI in this forum. |
| View Poll Results: When will Fermi show up (to buy) | |||
| November |
|
1 | 1.64% |
| December |
|
8 | 13.11% |
| The New Year!!!!!! |
|
52 | 85.25% |
| Voters: 61. You may not vote on this poll | |||
![]() |
|
|
Thread Tools | Display Modes |
|
|
#722 | |
|
Rage3D Veteran
Join Date: Jul 2005
Location:
NY, NY
Posts: 4,585
|
Quote:
I didn't really care either, but I was disappointed Valve didn't optimize thier code, if it was easy enough for someone without access to the source, it was obvious Valve didn't do the work or they weren't allowed to or they did it on purpose.
__________________
|
|
|
|
|
|
|
#723 |
|
SLIZONE Forum Support
Join Date: Mar 2003
Posts: 3,548
|
You know. I played the game. Did some benchmarks. And analyzed PhysX. Then I played and beat the game. then I uninstalled it. Its a good game. And fun. But I have no interest in it beyond my single playthrough and possible future benchmark tests. The funny thing about it is I overwrote the the default AA mode with a driver profile setting so I could enable SLIAA. So I never used the ingame's AA setting. And used a forced setting from day one. |
|
|
|
| Advertisement (Guests Only) |
|
Login or Register to remove this ad
|
|
|
#724 | |
|
noko
Join Date: Sep 2000
Location:
Orlando, Florida, USA
Posts: 2,697
|
Quote:
Batman AA is not an ATI/AMD project or developement, it is not ATI/AMD job to make their game, program for it or even be concerned about it. ATI got concerned because players, users complained about it and found what they found. Nvidia was the one that started to mock ATI in not having AA for the title, not being part of developement, even though it could be forced in the control panel meaning right from the start ATI hardware actually did support AA but not as efficiently as if it was done inside the game. Of course Nvidia bragged at how PhysX was so powerful when their GPU was used and not tell anyone that the cpu path was utterly castrated by one thread while AGEIA made PhysX to be multithreaded and use as many cpu cores as was availble in a machine. Get a good I7 with eight threads working with physics and Nvidia PhysX GPU ability would probably not shine as much. As for HL2 it was Nvidia poor support of minimum standard of DX9, initially 24bit FP was the DX standard which R300 supported and performed well. Nvidia supported 16bit FP usable and 32bit FP which was unusable or extremely slow, which caused the water looking like crude on Nvidia hardware. Nvidia also had issue with FarCry with lousy rendering using FP16. Not HL2, not Farcry, it was Nvidia FP32 was too slow to be useful while 16bit FP could be done but in many cases had quality issues and was not the API standard. So Nvidia did not support the API very good is the reason, developers had to go through hoops to make it work. I guess things don't change that much considering now what Nvidia is doing. Nvidia didn't complain to much back then because (actually they did, loudly against 3dmark because it showed how poo poo Nvidia stuff really was when using DX9) it would bring even more attention to their lack lusty hardware of that period.
__________________
Q6600 at 3.2gzh, Gigabit DSL 3, 8gb DDR2 800, eVga GTX 260 (216), 750w LSP PS, 320gb SATA2, 24" Accer LCD. Computer A/C cooled. Vista 64 Home Preimium Foxcon, 780G, Athlon 64 X2 5600+, eVga 8800 GTX, 4gb Mushkin PC800 DDR2, 120GB HD, Win 7 RC1 64bit XBox 360 on 55" HDTV, AWESOME! Last edited by noko : Today at 10:32 PM. |
|
|
|
|