Recent content by eddman

Yea, I had read that sometimes it's the other way around, where GPU manufacturers ask MS to add features they want to an upcoming Direct3D. That claim was posted on neowin in the comments section. It makes it look as if MS is the one that designs the chip architecture, which just sounded like...

Came across this odd claim: I've never seen anything about that. Last I checked MS says what features the graphics API supports and chip companies design their architectures to support it. Isn't that the case?

So it seems DDraw 1 received some Direct3D related stuff before D3D itself was ready. Found another readme, this one in SDK 2, that talks about interface name changes from Reality Lab to Direct3D; I guess DDraw 1 was supposed to work with Reality Lab API?

I was looking around in DirectX SDK 1 and saw the following inside the ddraw.h file: What are those about? I was under the impression Direct3D was introduced with DirectX 2, considering there's no d3d.h or d3dim.dll in SDK 1.

Dege just added interface numbers to dgvoodoo's trace log. It's now much easier to determine the DD/D3D. https://www.vogons.org/viewtopic.php?f=59&t=95377&p=1201478#p1201478

I went back and looked at the logs from a few games but now can't find CreateVertexShader. I have no idea what's going on. Perhaps I made a mistake, or losing my mind. Quite certain I saw it. I do see the SetVertexShader interface, although there are no shaders, and no Validate. I also...

Some early D3D8 games have Direct3D8Device::CreateVertexShader in the log, but I don't see vs.1 anywhere (or ps.1). If it doesn't actually use shaders, what's that interface used for?

I thought about going through the d3d.h files from old SDKs. The following seem to be all the D3D interface differences in the Direct3D and Direct3DDevice sections. (x) denotes a removed interface from previous versions. Direct3D 2 (3 has the same interfaces) Direct3D 5 Direct3D 6 Direct3D...

Hadn't noticed it was deleted. This one should last 14 days: https://transfer.sh/Ni5O09jaH9/AoW2.7z

Encountered another odd 2D game; Age of Wonders II. There is a Direct3D option in its configuration tool. I see Direct3D related traces in the log, like IDirect3DVertexBuffer7. The log file is too large to attach, even in zip format. EDIT: https://file.io/VD5DW7GqD8hN

Hey, I didn't even think about also checking the dependencies, since I thought the traces would suffice. Thanks. I guess the process going forward has to be to check dependencies first, and then traces.

Not crashes, I wrote d3d8 is mostly fine. It's just not handled as well as d3d9, and has lower performance (not too bad though), and visual glitches in some situations. The main issue is older d3d games. Visually they seem to be ok (although I haven't tested many), but the frame rate is in low...

Yea, that's correct. I was going based on the table from page 1, since it doesn't have any DDraw related interfaces listed for 5. I checked ddraw.h from SDK 5, and turns out DirectDrawSurface3 was introduced with this release, not DX3. There's also a DirectDrawColorControl.

Comparing d3d.h from SDK 2 and 3: What these differences do exactly?

Comparing the ddraw.h files from SDK 2 and 3, the only differences are: The first ones are comments. I don't know what display mode "e" is. It seems DirectDraw 3 isn't really a thing. Going by the corresponding DX release numbers, we apparently have DirectDraw 1, 2, 6 and 7.