• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Where's the logic?

Jeff7181

Lifer
Microsoft creates DirectX...
Microsoft + nVidia = Xbox
nVidia + DirectX 9 < ATI + DirectX 9

???????

Get what I'm saying? MS and nVidia slept together and Xbox was born... I guess it was a one night stand that left one of them pissed off so now MS is sleeping with ATI... otherwise you'd think nVidia's hardware would be more optimized for DirectX 9 than ATI's.
 
The GPU in the Xbox is like a GF3.5 and that's a DX8 part, so your logic doesn't follow thru.

There was an interesting interview with Nvidia's chief scientist that touched upon the development of Cg and HLSL. A snip:

FiringSquad: Could you give us more details on your recent decision to emphasize HLSL over Cg?

Kirk: You?re already seeing the ramifications of it as we begin to work more closely with Microsoft and optimize more and more for working with HLSL but let me give you a little history. Go back, say around two to three years when we started working on the FX architecture, we began to realize that complex programmable pipelines were going to require a high level language, and at that time there was no HLSL and we were working with other people in the industry including Microsoft to try and promote a programming language but we were not able to get any interest. So we started our own effort to develop Cg because we knew it would be required, whether or not anyone else thought it was important or not.

As we started out with Cg it was a great boost to getting programmers used to working with programmable GPUs. Now Microsoft has made a major commitment and in the long term we don?t really want to be in the programming language business and that?s not where our expertise is but its something we had to do, there was no other choice available. I think now that we have the opportunity to work collaboratively with Microsoft on HLSL for DirectX that?s a much more efficient way for us to work than to do it on our own.


It sounds like Nvidia tried to take the lead in the development of high-level languages and got clipped for trying to blaze the trail rather than follow along. Unfortunately, being first doesn't necessarily equal winning the race.
 
I wasn't saying that the Xbox uses DX9... I'm saying Micrsoft and nVidia created the Xbox... since they worked together on that, you'd think they would have worked together a bit behind the scenes on DX9... but it doesn't appear that way does it?
 
Still doesn't make sense. Xbox was done 2 years ago and DX9 is more than just the elements that Nvidia is struggling with. Despite the fervent ATI aficionados protests, FX cards ARE DX9 compliant, but currently have poor performance running PIXEL SHADERS, which are but a subset of DX9.

Also, if Nvidia was a set with DX9 as you think they should be, can you imagine the howls of "Collusion!" and "Being in bed together to screw ATI!" that would be heard.

Of course, we all know how helpful M$ was in setting or following HTML "standards". *cough*
 
doesn't ati have the contract for the GPU in xbox2? if yes, microsoft isn't really showing favoritism...they just want whatever's hot (or there's probably some behind-the-scenes crap going on...which is probably more likely)
 
Yeah... I guess you don't get what I'm saying. =) Either that or you choose not to so you can explain something that has nothing to do with what I'm actually talking about. =)
 
Back
Top