ccomrade/c1-launcher

Windows SDK and stuttering

xNeo92x opened this issue · 1 comments

xNeo92x commented

Not really an issue but more an advice.

Installing Windows SDK on Windows 11 doesn't give you the ability to use the Windows SDK command prompt.
You have to download the VS 2022 installer where you can choose to MSVC and CMake. You don't have to install the whole VS.
Then you can use the command prompt.

I tried the pre-compiled files but I had periodic stutters which repeated themselves every 3-4 seconds. As if something would load in, in small parts. Then I compiled the source myself and replaced the files (new compiles files are much bigger then the ones provided here). I also deleted the shader cache before that.
Now all stutters are gone and the game runs smooth as butter under any situation at 1440p@165Hz with max settings with 64bit, DX10.

Hardware:
Ryzen 5600X
AMD RX 6700XT
32 GB RAM

ccomrade commented

Installing Windows SDK on Windows 11 doesn't give you the ability to use the Windows SDK command prompt.
You have to download the VS 2022 installer where you can choose to MSVC and CMake. You don't have to install the whole VS. Then you can use the command prompt.

You're right. VS Code documentation mentions this as well. I've updated the build instructions.

I tried the pre-compiled files but I had periodic stutters which repeated themselves every 3-4 seconds. As if something would load in, in small parts.

This is interesting. Are you sure the prebuilt exes are the root cause? Could you test it again? There's no performance-critical code in the exe. It jumps straight to the update loop inside CryGame.dll after successfully starting the engine. The prebuilt exes should be less problematic actually. Crysis DLLs always use VS2005 runtime, so if you built the exe with modern MSVC, you suddenly have 2 different VS runtimes within one process. This can cause lots of problems, but it should be fine in this case. My theory is that modern MSVC uses slightly different values in some headers of the resulting exes and Windows treats modern and legacy exes differently. More investigation is needed.