|
DirectX 9 . 0 b
 Now,
"fundamental" architectural changes and API rewrites may, at sometime hence,
move the 9 to 10.
Minor changes, as for large feature additions, move the
numbers on a point, ie from 8.0 to 8.1
The letter changes either indicate the enablement of
features already apparent in the API, or bug fixes, performance updates, and
the like.
Now, the Software Developer's Kit (SDK) might have slightly
different labelling and it is this, it seems, that has caused some confusion.
The SDK tends to undergo more frequent revsions than the runtime itself so
some its numbers may run ahead of those tagged to the runtime. The DirectX
dudes are, we understand, attempting to find a different way of numbering the
SDK revisons to reflect this. Good on them.
So, on the matter of 9.0x, support for 3.0 shader appears
in the DirectX 9 runtime. This, we understand was to reduce the amount of
'churn' in the API. So when hardware comes along that makes use of the 3.O
Shader, this is, in effect, the enablement of a feature already supported in
the API, hence the letter change from 9.0b to 9.0c, as Fudo pointed out. (If
you're confused, start again at the top.)
There is, we learn, and as Fudo suggested, no DirectX 9.1
or DirectX 9.2 external release, nor are any currently planned. |
