I think DX9 features are finalised, but I dont know if the implementation is locked down yet.
That means Matrox could have trouble if they release a card that is meant to be DX9, but MS changes the way the data is meant to be accessed.
If the Next Big Thing is programmable, such as the SoundBlaster Live series, they could write an upgrade to change how it interprates data.
Then they could release it now, saying DX8.1 compliant, with some DX9 features (Displacement mapping MUST be Matroxs baby, so that will be compliant). Then after DX9 is released, they could release a firmware update if needed to implement the DX9 only features.
This way they gain another few months for driver development. If the DX9 features can be ignored until the DX8.1 ones are fully optimised, all the better. It will be probably another 6-12 months after the release of DX9 untill any of its features are used in anything other that benchmarks/demos that optimisations can wait.
Ali
That means Matrox could have trouble if they release a card that is meant to be DX9, but MS changes the way the data is meant to be accessed.
If the Next Big Thing is programmable, such as the SoundBlaster Live series, they could write an upgrade to change how it interprates data.
Then they could release it now, saying DX8.1 compliant, with some DX9 features (Displacement mapping MUST be Matroxs baby, so that will be compliant). Then after DX9 is released, they could release a firmware update if needed to implement the DX9 only features.
This way they gain another few months for driver development. If the DX9 features can be ignored until the DX8.1 ones are fully optimised, all the better. It will be probably another 6-12 months after the release of DX9 untill any of its features are used in anything other that benchmarks/demos that optimisations can wait.
Ali
Comment