1: I assume that the process would work with VS 2022 just as well as 2019.
2: Something is wrong, environment variables are missing in path, I am getting error C1083 in VS
3: should I use the VS installer to install everything he installed outside of the VS Installer? (SDK, WDK)
4: should I install same versions as he does in the video like v142 as opposed to v143 which is now available (latest), SDK and WDK or the version he is uses?
Looking in add/remove programs, I see the following listed:
Windows Driver Kit - 10.0.19041.65
Windows Software Development Kit - 10.0.17763.132
Windows Software Development Kit - 10.0.19041.685
Windows SDK AddOn - 10.1.0.0
The two SDKs - one is for VS2019 and the other for VS2022 (can't remember which is which) - I use VS2022 for building the other .sln files such as for the tcc libraries required for SpeedHack to function properly.
Regarding "v142 as opposed to v143"; it's been a while since I manually built the driver (I use a script to auto build), but I think a pop-up dialogue prompts you to retarget the solution at some point during the build - just accept it.
Looking in add/remove programs, I see the following listed:
Windows Driver Kit - 10.0.19041.65
Windows Software Development Kit - 10.0.17763.132
Windows Software Development Kit - 10.0.19041.685
Windows SDK AddOn - 10.1.0.0
The two SDKs - one is for VS2019 and the other for VS2022 (can't remember which is which) - I use VS2022 for building the other .sln files such as for the tcc libraries required for SpeedHack to function properly.
Regarding "v142 as opposed to v143"; it's been a while since I manually built the driver (I use a script to auto build), but I think a pop-up dialogue prompts you to retarget the solution at some point during the build - just accept it.
I am confused whether the versions need to be specific, or whether the latest version is always the better option. Be it the WDK, VS 2019 / VS 2022, SDK.
Also why are all these pre-reqs just not installable through the VS installer?
Not sure what that sdk addon you got installed is.
What is this script? Doesn't that ruin the point of customizing it so it is harder to detect? As you manually pick the manufacturer name and whatnot?
Thanks for the reply, I was surprised, thought more people would reply.
^^ i can understand that he/you do not want to share that tool, considering the amount of work that goes/went into it. But it would sure be nice to publish a recent/compiled CE vs though... (not all of us are VS affiliates in case you are wondering)
ps: I would instantly try it out on 'COD WW2' (for good reason )
)
