YES! incredible! Is it any way to know: how, wich and how, DLL advanced features and helpers of D3D 9 are being used in this demo?
Rest assured, most of the trickery is in their own code. They have been evolving their texture, geometry and sounds synthesizers (and the toolset to design them) for many years.
As far as features of D3D9… I would imagine 2.0 pixel & vertex shaders, maybe 3.0.
(ryg/fr here)
very little. we use the usual kernel32/gdi32/user32 stuff you’ll see in most windows apps, d3d9/dsound of course (no d3dx or anything) and the glu tesselator to convert the font outlines to triangles. that’s pretty much it.
d3d9-wise, we use some 1.1 and a lot of 2.0 vertex/pixel shaders and no vendor-specific trickery.
So when is Iguana going to make a demo ? Heartquake II ???
YES! incredible!
Is it any way to know: how, wich and how, DLL advanced features and helpers of D3D 9 are being used in this demo?
Rest assured, most of the trickery is in their own code. They have been evolving their texture, geometry and sounds synthesizers (and the toolset to design them) for many years.
As far as features of D3D9… I would imagine 2.0 pixel & vertex shaders, maybe 3.0.
(ryg/fr here)
very little. we use the usual kernel32/gdi32/user32 stuff you’ll see in most windows apps, d3d9/dsound of course (no d3dx or anything) and the glu tesselator to convert the font outlines to triangles. that’s pretty much it.
d3d9-wise, we use some 1.1 and a lot of 2.0 vertex/pixel shaders and no vendor-specific trickery.
So when is Iguana going to make a demo ? Heartquake II ???
Yours Truly, el Cabron 🙂