The DirectX 9.0c perhaps is the last DirectX run time that support on Windows XP platform since DirectX 10 doesn’t support XP. Maybe it could be reduced if someone else writes a Galium3D compatible driver for the current hardware generation of AMD.Download DirectX 9.0c is available download now. Taking all together this would be even more work then option 1. A custom Direct3D 10 runtime can use this interface. This way you can add a additional custom interface to such a driver. While AMD have started to open up their Spec it becomes possible to write your own driver for their hardware even for Windows XP. Personally I would not touch this again without OpenGL 3.x.Ģ. There is a high chance that the Wine Project will go this way and that there work can be ported over to Windows XP. This is what the Alky Project tries before they give up and released anything they got (not much IMHO) as open source. Technical, for someone outside of the inner circle (Microsoft, nvidia, AMD, other IHVs), there are only two ways getting Direct3D 10 applications run on Windows XP.ġ. The only benefit is that this allows running an asset pipeline on non Vista systems. This limit it mostly to the compiler for shader and effects. The only part of Direct3D 10 that works on Windows XP today are some elements of the D3DX10_?.DLL as long as they don’t need a device. Therefore early tech previews of Direct3D 10 required a beta version of Vista.
The reason for this is that the SDK never includes a D3D10.DLL which contains the runtime. This includes working with the Reference Rasterizer. There was never a DirectX SDK that contains a working Direct3D 10 for Windows XP.
Your information’s are wrong at this point. I do not rember which it was in, but some people have posted a url to it in reactos forum. ms did release a beta for xp in a directx sdk. It exists directx 10 for windows xp from ms, you need to known where to look for it. GreatLord wrote:as many time before I point this out
0 kommentar(er)
