Roderick Colenbrander : wined3d: Add reporting of D3DRTYPE_VOLUME capabilties.
Module: wine Branch: master Commit: 616944ae7e990946ad2a6e8235c017a482dfb93c URL: http://source.winehq.org/git/wine.git/?a=commit;h=616944ae7e990946ad2a6e8235... Author: Roderick Colenbrander <thunderbird2k(a)gmx.net> Date: Fri Mar 21 20:57:14 2008 +0000 wined3d: Add reporting of D3DRTYPE_VOLUME capabilties. We assume it has the same capabilities as VOLUMETEXTURE. MSDN is very vague on this topic. Intel/Nvidia/ATI drivers seem to offer nearly the same caps on both, so do that too. --- dlls/wined3d/directx.c | 7 +++++-- 1 files changed, 5 insertions(+), 2 deletions(-) diff --git a/dlls/wined3d/directx.c b/dlls/wined3d/directx.c index 7ed9739..db351ee 100644 --- a/dlls/wined3d/directx.c +++ b/dlls/wined3d/directx.c @@ -2421,8 +2421,11 @@ static HRESULT WINAPI IWineD3DImpl_CheckDeviceFormat(IWineD3D *iface, UINT Adapt if(Usage & WINED3DUSAGE_DEPTHSTENCIL) UsageCaps |= WINED3DUSAGE_DEPTHSTENCIL; } - } else if(RType == WINED3DRTYPE_VOLUMETEXTURE) { - /* Volumetexture allows: + } else if((RType == WINED3DRTYPE_VOLUME) || (RType == WINED3DRTYPE_VOLUMETEXTURE)) { + /* Volume is to VolumeTexture what Surface is to Texture but its usage caps are not documented. + * Most driver seem to offer (nearly) the same on Volume and VolumeTexture, so do that too. + * + * Volumetexture allows: * - D3DUSAGE_DYNAMIC * - D3DUSAGE_NONSECURE (d3d9ex) * - D3DUSAGE_SOFTWAREPROCESSING
participants (1)
-
Alexandre Julliard