Re-Volt "DDERR_UNSUPPORTED Can't get texture surface DC"

[BinqAdams]

Hi!

This happens when it is loading textures.

I'd like to try Re-Volt with RTX Remix, and the existing GoG wrapper seems to draw everything to a render target or something.

I tried one or two config options.

Here is the log and config!

dxwrapper-revolt.log

dxwrapper.log

[elishacloud]

I didn't support DC's from a MipMap level. However, I added partial support for that. It has some limitations and won't work on emulated surfaces.

You can try the build here: dxwrapper.zip (removed)

[elishacloud]

You can try this build: dxwrapper.zip

[BinqAdams]

You can try this build: dxwrapper.zip

Thank you elisha, I have posted on the RTX Remix discord :)
I'm not able to test right now, but I am sure those in the discord are excited to try it.

it would be amazing to see this game with full path tracing!

[BinqAdams]

You can try this build: dxwrapper.zip

Hello! I did a quick test, I didn't spot any difference from the previous behaviour (the error message still appears, and many things are not being rendered).

dxwrapper-revolt.log

[elishacloud]

Thanks! I was afraid of this. The game might require emulated DC MipMaps. Here is the new error message:

14228 21:36:44.637 m_IDirectDrawSurfaceX::GetDC Error: Emulated DC not supported from MipMap level: 1 surface: {0x2100f,128,128,512,0,1,0,0,00000000,{0x0,0x0},{0x0,0x0},{0x0,0x0},{0x0,0x0},{0x41,0,32,0xff0000,0xff00,0xff,0xff000000},32,{{ DDSCAPS_COMPLEX  DDSCAPS_MIPMAP  DDSCAPS_SYSTEMMEMORY  DDSCAPS_TEXTURE },0x10080,0x0,0x0},0}

Just in case, can you try with this update and sent me the logs: dxwrapper.zip

[Entityexist]

dxwrapper-revolt.log

here you go there is a big change some surfaces are showing up :D

[elishacloud]

Ok, try this. It may show a few more surfaces: dxwrapper.zip

[Entityexist]

dxwrapper-revolt.log this is how it looks now

[Entityexist]

Hi ElishaCloud,

I'm working on analyzing the rendering flow of the game Re-Volt, which uses Direct3D 6/7 with pre-transformed vertices (D3DFVF_XYZRHW) for most of its rendering – including 2D UI, transparent geometry, and even some 3D effects. I was wondering if DxWrapper could be extended to intercept these DrawPrimitive/DrawIndexedPrimitive calls using RHW-based FVF formats and reconstruct an approximate world-space representation of these vertices.

What I'm proposing

When the app calls IDirect3DDeviceX::DrawPrimitive or DrawIndexedPrimitive, and the FVF includes D3DFVF_XYZRHW, the wrapper could:

• Parse and copy the vertex buffer from system memory (most of them are VERTEX_TEX0, VERTEX_TEX1, etc., structs with x,y,z,rhw,color,specular[,u,v])
• Use the current viewport and projection settings (available via GetViewport, GetTransform, or already cached) to "reverse-project" them
• Optionally dump the reconstructed world-space positions (even if approximate) to a side log or external tool

Use cases

This could be especially helpful for:

• Debugging UI and semi-transparent geometry positioning
• Remix-based remastering workflows (even if 2D) to help align effects to real geometry
• Identifying visual elements in screen-space for mods or replacements

Reference from the game engine

In Re-Volt, calls like these appear in draw.cpp:

D3Ddevice->DrawPrimitive(D3DPT_TRIANGLEFAN, FVF_TEX1, verts, numVerts, D3DDP_DONOTUPDATEEXTENTS);
Where FVF_TEX1 is defined as:

#define FVF_TEX1 (D3DFVF_XYZRHW | D3DFVF_DIFFUSE | D3DFVF_SPECULAR | D3DFVF_TEX1)
And vertex structs are:

typedef struct {
float sx, sy, sz, rhw;
DWORD color, specular;
float tu, tv;
} VERTEX_TEX1;
Possible implementation hint
In the wrapper you could do something like:

if ((FVF & D3DFVF_XYZRHW) == D3DFVF_XYZRHW) {
// Intercept vertex buffer
// Reverse project: Unproject screen-space back to world using RHW and known matrices
}
For inverse transformation, something like D3DXVec3Unproject() (or custom math) could be used, given current D3DVIEWPORT, Projection, and View matrices.

Let me know if you think this could be a viable addition to DxWrapper or if you'd prefer such functionality to live in an external tool. I’d be happy to help prototype it if needed.

Thanks for all your incredible work maintaining DxWrapper!

i think this is just not possible or dumb question

[Entityexist]

🔧 Proposed Wrapper Hack for Remix Support (minimal pipeline emulation):

In the game code (see SetViewport() in Re-Volt's draw.cpp), viewport values like size, perspective scale (pers), and screen extents are computed manually. These values could be used to synthesize a dummy perspective and view matrix and inject them into Direct3D via SetTransform(), even if the game never uses them.

For example, within dxwrapper or a hooked IDirect3DDevice7 implementation, when DrawPrimitive() is called with RHW vertices, you could:

1. Synthesize a perspective matrix based on RenderSettings.GeomPers, aspect ratio, and screen size (already known in-game).
2. Create a dummy view matrix — e.g., camera at (0,0,-distance), looking at origin.
3. Call:
   device->SetTransform(D3DTRANSFORMSTATE_PROJECTION, &proj);
   device->SetTransform(D3DTRANSFORMSTATE_VIEW, &view);

📎 Code Reference from Re-Volt:

// Called at every resolution/camera update
void SetViewport(REAL x, REAL y, REAL xsize, REAL ysize, REAL pers)
{
RenderSettings.GeomPers = pers;
RenderSettings.GeomScaleX = xsize / RealScreenXSize;
RenderSettings.GeomScaleY = ysize / REAL_SCREEN_YSIZE;
RenderSettings.MatScaleX = GeomScaleX * pers;
RenderSettings.MatScaleY = GeomScaleY * pers;

D3DVIEWPORT2 vd = {};
vd.dwSize = sizeof(vd);
vd.dwX = (DWORD)x;
vd.dwY = (DWORD)y;
vd.dwWidth = (DWORD)xsize;
vd.dwHeight = (DWORD)ysize;
vd.dvMinZ = 0.0f;
vd.dvMaxZ = 1.0f;

D3Dviewport->SetViewport2(&vd);

}

[elishacloud]

dxwrapper-revolt.log this is how it looks now

I found a few new errors in the log. Try the latest build here: dxwrapper.zip

which uses Direct3D 6/7 with pre-transformed vertices (D3DFVF_XYZRHW) for most of its rendering

What makes you think these are pre-transformed vertices? When a game sends D3DFVF_XYZRHW vertices it is expected that they are already transformed.

I was wondering if DxWrapper could be extended to intercept these DrawPrimitive/DrawIndexedPrimitive calls using RHW-based FVF formats and reconstruct an approximate world-space representation of these vertices.

DxWrapper already intercepts these calls. My understanding is that it isn't possible to fully reconstruct something that is already transformed. However, it can be guessed at. If the game calls a function like TransformVertices then you could see the vertices before they were transformed.

Optionally dump the reconstructed world-space positions (even if approximate) to a side log or external tool

This might be a lot of data. I am not sure how to keep from dumping the same or similar data and there could be dozens of calls per frame. But it is certainly possible to dump this data.

Let me know if you think this could be a viable addition to DxWrapper or if you'd prefer such functionality to live in an external tool.

This is certainly possible, but I am not sure if or when I could get around to it. You are welcome to create a function that can do this type of logging and create a pull request for it. I already have a similar function to export out surfaces/textures, see here.

In the game code (see SetViewport() in Re-Volt's draw.cpp), viewport values like size, perspective scale (pers), and screen extents are computed manually. These values could be used to synthesize a dummy perspective and view matrix and inject them into Direct3D via SetTransform(), even if the game never uses them.

Something like this has already been done in the latest pull request here: #199