D3D Proxy Tools in danger?

If they implement this with the concept of a registry key to disable it for a particular application and use UAC to notify users anytime that an exclusion is created, then it may actually be a nice security improvement but wouldn't impact the functionality of applications like steam, etc.. because we could simply create an exclusion for them.

If there is no excluision mechanism, then this is a major problem. The only way to have an overlay would be to implement Microsoft's Games For Windows Live (GFWL) API for this. AFAIK, GWFL is not public, and registration / application process is required to get the API.

Lets hope for the exclusion process!

I haven't really looked into this but, even though I don't like the idea, it really shouldn't cause too much grief.
You should still be able to just hook LoadLibraryExW and watch for the d3dx9.dll or whatever and detour. May have to dig through the iat if the app itself doesn't directly load it, but either way it is still completely possible to make it all work without too much work.

You run the risk of getting picked up as a cheat under games that use Anticheat but this can be avoided with some extra hiding, and I'm not sure how big of an issue this is with Racing Games (Do they make Wallhacks for racing games? )

Screw the entire GFWL sdk crap, you don't need it.

:rofl: What do you mean we don't need their crap to do it. IT'S ALL THEIR CRAP! Direct X, the API, Messaging Pump, Operating System, etc..

Essentially, your proposal suggest using all Microsoft OS features and DirectX (another Microsoft product).

I'm wasn't suggesting that GFWL is the answer to the problem, but I find it humorous that you you would discount it just because it's a Microsoft solution and then propose mis-using two other Microsoft technologies as an acceptable solution.

I apologize for my ambiguous wording in my prior post. It seems as though you took offense to what I said, when I was simply trying to contribute some of my experience to the conversation. Animosity was never intended to be displayed in my first post on this forum.

The whole point I was trying to make was that the lack of proxy dll's is not an issue whatsoever. It may be construed as being a small inconvenience, but with some very basic programming, you have all the tools you need to remove the need for proxy dll support.

Not a major problem at all. You can bypass this using the method I stated above (hook and detour) without having to change your existing libraries. Not only does this remove the need for the proxy dll (which I've never much liked myself anyways, as some applications won't in-folder dll's), but it removes the need to rewrite all of your code to comply with a different framework.

I assumed that you were referring to a graphic overlay in this statement, excuse me if I am wrong.
With OpenGL or DirectX games you can create a very elaborate overlay system with mouse/keyboard input options and nice graphics. I have used these same methods when creating first person shooter aimbots. It can also be done outside of the target process, not interfering with the game memory whatsoever.

Touche. I should have specified that I was referring to the GFWL SDK when I said their crap.

That was not the point I was trying to make at all. I was suggesting that the idea of rewriting all of your existing code and trying to make it work with a feature-limiting API that you will most likely have to pay to use is not the route I would take. Also, I am not following how anything I said would be considered misusing 2 Microsoft technologies. If you would elaborate on that, I would be very pleased.