@spazfirem I took a look back and the .ini change I suggested is NOT sufficient for 4.19. Looks like 4.19 had a bug with the Aftermath initialization code that is kinda forcing it on. We straightened all that out in 4.20. Sorry about that, I hadn’t realized that was going on. If you look in the log you will see “Aftermath enabled and primed” which indicates that it’s on. Looks like for a binary release the only way to really kill it would be to delete the GFSDK_Aftermath_Lib.x64.dll from Binaries/ThirdParty/NVIDIA/NVaftermath/Win64/. If you can make code changes, then then forcing GDX11NVAfterMathEnabled to 0 in FD3D11DynamicRHIModule::StartupModule should resolve it.