dgVoodoo2 VS renderdoc

Parts of DX5 and previous, such as the "retained mode", are missing from current versions of Windows entirely. Much of the remaining implementation is buggy and introduces render artifacts.

Open source projects such as dgVoodoo offer a solution to run old games, by re-implementing old DirectX and Glide on top of current DirectX [1], similar to how Wine runs DX games on Linux on top of OpenGL or Vulkan.

[1]: https://github.com/dege-diosg/dgVoodoo2

I have not tried this myself, but there are two compatibility wrappers that implement old graphic APIs for modern systems - nGlide and dgVoodoo2.

Voodoo2 for added stability in old games

It's a wrapper for old DirectX 7/8/9 games that makes them use DirectX 11/12/Vulkan instead: https://github.com/dege-diosg/dgVoodoo2

This... here's a link to the github. Click on Releases to get the latest build (it'll be the first zip file without _dbg (debug) in the title).

Try using dgVoodoo2. https://github.com/dege-diosg/dgVoodoo2/releases

You can always use dgVooDoo [0] to translate Glide to DirectX. With great performance, too.

[0] https://github.com/dege-diosg/dgVoodoo2

How to install DGVoodoo2 for use with Windower: download the latest non-dbg, non-api, non-source-code: .zip https://github.com/dege-diosg/dgVoodoo2/releases Unzip it. Move dgvoodoocpl.exe and MS\(x86)\d3d8.dll (just the d3d8) into -- playonlineviewer folder for retail or the same folder that your loader exe is in for private server (you can overwrite any old one in there if you like). Right click on dgvoodoocpl.exe and run as administrator. At the top right press Add and select the same folder as you selected earlier (playonlineviewer folder for retail and/or the folder of the private server loader). On the General tab, set your Adapter(s) to use / enable to your graphics card (note that, if the game won't launch after these steps, then try going back, selecting the same folder again in the dropdown menu at the top, and change it back to All, but it should work most of the time with your graphics card selected and will make sure that graphics card gets used. -- known to be necessary with SurfaceBook laptops, and maybe with external graphics card enclosures as well (untested)) On the DirectX tab, set VRAM to 512 MB (higher if you're using HD textures) and unckeck dgVoodoo Watermark at the bottom.

heh https://github.com/baldurk/renderdoc#readme is all "RenderDoc is intended for debugging your own programs only. Any discussion of capturing programs that you did not create will not be allowed in any official public RenderDoc setting, including the issue tracker, discord, or via email" but the 3 of the 4 screenshots are of dota2 :-D

Still, that looks handy for sure

He's pretty clear about it every time it's asked. Tracing copyrighted games is legally questionable, and tools like RenderDoc are often abused by people to do illegal asset ripping/reselling.

Baldur explains why he won't implement bindless texture support in this issue: https://github.com/baldurk/renderdoc/issues/850

Unfortunately the main developer for Renderdoc is against adding ray tracing support : https://github.com/baldurk/renderdoc/issues/2317

RenderDoc bug report: https://github.com/baldurk/renderdoc/issues/2800

Remember that Renderdoc is open source: https://github.com/baldurk/renderdoc/. This means you can build it with symbols and attach a debugger.

Renderdoc works by inserting itself as a Vulkan layer, which means it can change the output of functions if it so chooses. As you can see in the RenderDoc version of vkEnumeratePhysicalDevices it changes how devices are returned, and this likely is the reason the order changes.