2008-02-08 08:34:01
I know I can play Halo 2 on XP using a third-party tool that basically tricks
Halo 2 into thinking it's on Vista. I'd link to the site, but I just checked
and
it's been taken over by advertiser domain squatters.
That's because Halo 2 doesn't actually need directx10. It has a 'is this vista
check', and it might use a couple of minor new directx 10 direct3d calls (which
can easily be captured and reimplemented in direct3d 9).
The real features of directX10 like Video memory virtualization and gpu
multitasking (which allows Vista to have multiple direct3d accelerated
applications
(including the desktop) all running at the same time in (possibibly overlapping
windows).
-That- is (amongst other reasons) why Vista has a new driver model, which in
turns needs kernel support. -That- is why it hasn't been backported to XP.
-That-
is why its not likely to ever get backported to XP.
DirectX10 itself is a MAJOR milestone for windows, for the windows desktop, a
step that brings it to parity with what linux and osx can do, in fact.
You aren't going to get a proper Compiz or Aqua class desktop for XP because XP
simply can't do this stuff. Vista/DirectX10 can. But, this isn't really
important 'for games' and games requiring directx10 is mostly marketing puff
using minor features that can be easily redirected via a directx9 wrapper.
This is unfortunately because it undermines just how major directX10 really is,
leaving gamers with the impression that its just a cheap tactic to sell Vista.
(Which, to the extent of its use by current games; requiring directX10 IS a
cheap tactic to sell vista.) But directX10 is quite a bit more than what these
games are using. And this cheap tactic is masking that.