Search the Community
Showing results for tags 'data execution prevention'.
Found 1 result
Looking at the sticky threads here regarding Windows support, the advice is now considerably out of date with KSP 1.2.2 running on Unity 5. Especially: Data Execution Prevention does not break KSP. If it did before, it doesn't now. Turning this off is a bad idea. User Account Control does not break KSP. The installation folder just needs Modify permissions granted to BUILTIN\Users. icacls "%programfiles%\[ksp-folder]" /grant Users:(OI)(CI)M does the job if needed. Steam users don't need to do anything. The Program Files folder does not break KSP. Just needs permissions adjusted as above. Windows 10 does not break KSP. (OK, no one from Squad says that but I keep hearing it from others.) My problem is bad computing advice is being suggested just to make KSP and some of its more esoteric add-ons work, which is unnecessary and just exposes players to computing abuses. And this bad advice is still stickied in this support forum despite it being false. Claw hasn't been active since early 2016 or I'd have sent him a personal message about this. Is there someone else who can verify what I'm saying and edit the Known Issues and Self Help thread accordingly?