Blur Busters Forums

The first one disables Data Execution Prevention:
https://support.microsoft.com/en-us/top ... 2419135817

As you can see this one is a huge security risk but obviously I only care about latency.
Paste this into CMD or make it into a .bat file:

@echo off

bcdedit /set nx AlwaysOff
powershell set-ProcessMitigation -System -Disable DEP
powershell set-ProcessMitigation -System -Disable EmulateAtlThunks

echo DEP has been forcefully disabled. Please reboot your system.
pause

If you want to reenable it:

@echo off

bcdedit /set nx AlwaysOn
powershell set-ProcessMitigation -System -Enable DEP
powershell set-ProcessMitigation -System -Enable EmulateAtlThunks

echo DEP has been forcefully enabled. Please reboot your system.
pause

The second one is related to DirectX, supposedly they don't do anything now but there is definitely a difference with them applied:
The only place I found this was on a forum page where no one gave an explanation about what is being changed and this github page with a lot of registry keys I tried as well.
https://github.com/ionuttbara/fidelity/ ... _reg11.reg

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Direct3D]
"DisableVidMemVBs"=dword:00000000
"MMX Fast Path"=dword:00000001
"FlipNoVsync"=dword:00000001

[HKEY_USERS\.DEFAULT\SOFTWARE\Microsoft\Direct3D]
"DisableVidMemVBs"=dword:00000000
"MMX Fast Path"=dword:00000001
"FlipNoVsync"=dword:00000001

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Direct3D]
"DisableVidMemVBs"=dword:00000000
"MMX Fast Path"=dword:00000001
"FlipNoVsync"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Direct3D\Drivers]
"SoftwareOnly"=dword:00000001

[HKEY_USERS\.DEFAULT\SOFTWARE\Microsoft\Direct3D\Drivers]
"SoftwareOnly"=dword:00000001

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\Direct3D\Drivers]
"SoftwareOnly"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\DirectDraw]
"EmulationOnly"=dword:00000001

[HKEY_USERS\.DEFAULT\SOFTWARE\Microsoft\DirectDraw]
"EmulationOnly"=dword:00000001

[HKEY_CURRENT_USER\SOFTWARE\Microsoft\DirectDraw]
"EmulationOnly"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Direct3D]
"DisableVidMemVBs"=dword:00000000
"MMX Fast Path"=dword:00000001
"FlipNoVsync"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Direct3D\Drivers]
"SoftwareOnly"=dword:00000001

[HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\DirectDraw]
"DisableAGPSupport"=dword:00000001
"DisableInactivate"=dword:00000001
"DisableMMX"=dword:00000001
"DisableNoSysLock"=dword:00000001
"EmulationOnly"=dword:00000001

so u dont have floaty mouse movemenet, and your mouse is 1:1 perfect?

ablemor wrote: ↑

21 Dec 2024, 16:56

so u dont have floaty mouse movemenet, and your mouse is 1:1 perfect?

I would say 99% and the 1 % is the mystery lag but it's not noticeable anymore, looks good on recordings as well. Also this is more about Windows itself being poorly configured by default because these two settings along with disabling Write Caching make such a huge difference it's unbelievable.

you need dep to play face it.

JimCarry wrote: ↑

22 Dec 2024, 00:53

you need dep to play face it.

Good thing you mentioned it. FACEIT needs every garbage setting that kills PC performance.

kriegsnake wrote: ↑

22 Dec 2024, 01:56

Hyote wrote: ↑

21 Dec 2024, 12:25

Paste this into CMD or make it into a .bat file:

@echo off

bcdedit /set nx AlwaysOff
powershell set-ProcessMitigation -System -Disable DEP
powershell set-ProcessMitigation -System -Disable EmulateAtlThunks

echo DEP has been forcefully disabled. Please reboot your system.
pause

I think that's normal.

Hyote wrote: ↑

22 Dec 2024, 09:28

JimCarry wrote: ↑

22 Dec 2024, 00:53

you need dep to play face it.

Good thing you mentioned it. FACEIT needs every garbage setting that kills PC performance.

I can confirm that face it anti cheat cost 30 fps on my machine.if someone dont believe me,please do benchmark with face it anti cheat only and cs2.exe and then do the same benchmark with only cs2.exe and compare.i can bet anti cheat will cost fps but how much i cant tell.

Revived this as well because I changed the DirectX settings and now they give me INSANELY snappy input.

Hyote wrote: ↑

20 Jan 2025, 03:29

Revived this as well because I changed the DirectX settings and now they give me INSANELY snappy input.

Have you just reapplied your settings posted above or have you tweaked something additionally?