d3d8to9 inclusion issues in Remix 0.5.0

I would like to add that including the wrapper is a great idea and a time saver for projects, and greatly appreciated with this update. However, the current implementation has some issues that need to be addressed making it a less reliable option to elishacloud's dxwrapper for Remix projects and somewhat negating its benefits. I have linked to messages within the discussion that highlight the issues present.

Crosire's implementation of d3d8to9 is great for plug-and-play functionality but elishacloud's implementation allows for some finer controls and better debugging options that testers have noted have great impact on their ability to handle certain edge cases.

Issues

• Per discussion today in the Remix Discord, including d3d8to9 by default as has been done in Remix 0.5.0 is a great time-saver but can come with some unintended side-effects.
  • Some configuration utilities and other applications will hook into D3D8 and will fail to start up with a wrapper present
  • Utilities (such as UnrealEd for UE2 titles) will render in Remix, complicating usage when vanilla rendering is more useful and efficient or causing GUI issues that need to be debugged
• Release packaging script has included file as d3d8to9.dll instead of d3d8.dll, must be manually renamed to apply to game EXEs
• Shadow of Destiny/Shadow of Memories (Konami) fails to launch with crosire implementation, works with elishacloud's; this could potentially be due to better error handling but has not been investigated

Requests

• Elishacloud's implementation features more verbose logs for troubleshooting than the crosire d3d8to9 wrapper which is used in Remix
• When using Elishacloud's dxwrapper, processes can be excluded from wrapping; this allows edge cases that perform poorly with wrappers or do not need Remix injection to be ignored safely. Such a feature would significantly improve the included wrapper.

Expected behavior

• When included with correct name d3d8.dll will apply automatically to games that use d3d8.

Start with the release packaging script and the included d3d8to9 wrapper, then review the linked Discord discussions for the reported startup, rendering, logging, and process-exclusion cases. Done means the wrapper is packaged with the correct d3d8.dll name, supports the requested troubleshooting and exclusion behavior, and preserves expected game and utility launches.