Vulkan Development: ReShade seems nefarious...

  • Derjyn
  • Topic Author
More
9 months 3 weeks ago #1 by Derjyn Vulkan Development: ReShade seems nefarious... was created by Derjyn
I recently installed ReShade (I've been using it for years, this was just a recent return to fiddle with a game's visuals), and as an aside I am working on a game engine using C++ and Vulkan for fun and knowledge expansion.

Now I'm a bit miffed, as I get to look at warnings and such related to ReShade as I'm debugging and running tests, CI/CD, bla bla bla. Why in the world would ReShade be getting involved with my own raw metal development projects, when I installed it for a single game? I've deleted the ProgramData/ReShade folder in the hopes that it get out of my way, however now I get warnings related to validation layers in my application, as it can't find ReShade JSON files any more.

I love ReShade, but this is bad from a developer's standpoint. I am in no way linking to or referencing ReShade in my development project. I simply installed ReShade for a single game.

How do I get rid of ReShade, stop it from stepping into my development project(s), and in the future if I want to prevent this (what would be classified as malicious/risky) behavior if I install it for a game: what sort of settings would I need to tinker with to allow for ReShade to run for the game, but stay the heck out of my projects, uninvited?

If I were to take a project into a more serious state, doing an audit of security and various external libraries that need to be managed... I'm more of an opt-in sort of person. I don't need to be tracking down some external utility that thinks it should be involved without explicitly telling it to do so, having a finger on it's pulse, and total control of when/why/how it does get involved if I so choose to integrate with it.

I don't mean to bash ReShade, and I'm leaning towards this scenario being caused by a misstep I made somewhere, but that's benefit-of-the-doubt reasoning. I'm having a hard time finding how this happened, since I have a very pretty basic raw metal codebase in the project where I noticed this behavior, linking and referencing only standard platform libraries and Vulkan. That's it.

Please Log in or Create an account to join the conversation.

We use cookies
We use cookies on our website. Some of them are essential for the operation of the forum. You can decide for yourself whether you want to allow cookies or not. Please note that if you reject them, you may not be able to use all the functionalities of the site.