Re: DX7 on newer cards
- From: "Sam Brown" <subiNOSPAM@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 30 Aug 2008 15:55:24 +0100
"Chuck Walbourn [MSFT]" <chuckw@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:%23P6Ei0xAJHA.5160@xxxxxxxxxxxxxxxxxxxxxxx
The DX7 rendering path on modern cards is probably not well tested byYeah, that's kind of what I thought. I just wondered if there was
anyone. For Windows Vista, the older APIs were all "lofted" onto DX9, so
they should work better on Vista than on XP.
anything official beyond "DX7 is not supported any more".
I did a bit of further looking, and it's not just NVidia - My
four-year-old Radeon 9800 does it as well. But all of them only
exhibit the problem when using a TnL device. A normal HAL is fine,
as is the reference rasterizer.
It _seems_ to be when I'm uploading texture data. Unfortunately,
the drivers on all the systems I have that let me create a TnL
device are all DX9, so no chance of getting any debug output from
them for DX7 calls!
Also, every so often (and usually the first time drawing a new
set of meshes) DrawIndexedPrimitiveVB returns either DDERR_GENERIC
or DDERR_INVALIDPARAMS. However, calling it again immediately
after the failure with the same params results in success.
So there really does seem to be something very iffy indeed about DX7
these days. The weird thing is, I've been using this engine for
four or five years now (on the same machine in my case) and never had
anything like this happen before. There's nothing in the recent
set of XP updates that might have killed it, is there?
Or am I just doing something completely insane?
Cheers,
- SamB
.
- References:
- Re: DX7 on newer cards
- From: Chuck Walbourn [MSFT]
- Re: DX7 on newer cards
- From: Sam Brown
- Re: DX7 on newer cards
- Prev by Date: No textures with D3DPOOL_MANAGED under Vista?
- Next by Date: WPF D3DImage performs good on XP, bad on Vista
- Previous by thread: Re: DX7 on newer cards
- Next by thread: Effects or not Effects
- Index(es):
Relevant Pages
|
