Posted: . At: 6:50 AM. This was 11 months ago. Post ID: 18083
Page permalink. WordPress uses cookies, or tiny pieces of information stored on your computer, to verify who you are. There are cookies for logged in users and for commenters.
These cookies expire two weeks after they are set.

The Stalker 2 dev build has leaked on the Internet.

  1. Crash logs
  2. Build installation
  3. Required files
  4. All guns in Stalker 2 so far
The Stalker 2 splash screen.
They leaked the Stalker 2 roadmap.

The Stalker 2 development build has been leaked on the Internet, this is a 208 GiB download and includes a playable build of the Stalker 2 game. It’s the entire project directory with both the release and debug binaries, object files, and more. There are tons of clutter that isn’t present in the release version. This is amazing.

Here is one of the game scripts as proof.

gamedata/scripts/OnGameLaunchScripts.cfg
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
[0] : struct.begin
   SID = DebugEditorGameLaunch
   ScriptsArray : struct.begin
      [*] = XStartQuestBySID rootgraph
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E01_MQ01
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E02_MQ01_NoIntro
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E02_MQ01
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E02_MQ02_KosoyHunt
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E02_MQ03
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E02_Sphere_Rihter
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E02_Sphere_Varta
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E03_MQ01
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E03_MQ01_KillBandits
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E03_MQ01_KillVarta
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E03_MQ02
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E03_MQ03_AllInclusive
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E03_MQ03_Naked
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E03_MQ04
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E03_MQ05_Iskra
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E03_MQ05_Varta
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E03_MQ06
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E05_EQ02_PsiDestroyed
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E05_EQ02_Zombies
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E05_MQ01_Spark
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E05_MQ01_Ward
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E05_MQ02
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E05_MQ03
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E05_MQ04
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E05_SQ01
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E05_SQ03
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E05_SQ04
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E05_SQ05
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E07_MQ01_Spark
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E07_MQ01_Ward
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E07_MQ02_Spark
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E07_MQ02_Ward
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E08_MQ01_Spark
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E08_MQ01_Ward
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E08_MQ03_Spark
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_E08_MQ03_Ward
      //[*] = XExecuteAdditionalScript OnGameLaunchScripts_SQ81
	  [*] = XPauseScheduledEmission
   struct.end
struct.end
[1] : struct.begin
   SID = DebugEditorGameLaunchBeginPlay
   ScriptsArray : struct.begin
      [0] = XExecuteAdditionalScript RKDebugEditorGameLaunchBeginPlay
      [1] = XHideMinimap
   struct.end
struct.end

And another one. This seems to define a task to clear a depot of bandits.

gamedata/scripts/OnGameLaunchScripts_E03_MQ01_KillBandits.cfg
1
2
3
4
5
6
[0] : struct.begin
   SID = OnGameLaunchScripts_E03_MQ01_KillBandits
   ScriptsArray : struct.begin
      [*] = XStartQuestNodeBySID E03_MQ01_SetCharacterParam_DepoBanditsWeak
      [*] = XStartQuestNodeBySID E03_MQ01_SetCharacterParam_DepoBanditsStrong
   struct.end

The Stalker 2 executables. It comes with an Editor?

The Stalker 2 leak does come with an editor? This is amazing, you could have a look at the map in the editor and find hidden stuff. Apparently, there are quite a few leaked builds. The password might be 2.0.2.1 this was in the Stalker 2 leaks Discord. GSC forgot to privatize their torrents from search engines and a data miner was randomly searching for stuff and found the entire S2 build encrypted if you want to wait 5,783,128,169,837,158,197,871+10e17 years to break it (in the best of conditions) be my guest or if you believe they’ll find the encryption key, which might be around somewhere. Maybe in a locked crate in the middle of Jupiter plant guarded by 2000 Monolith and Blackwater Mercs. But seriously, there are 16 builds, overall 1.5 terabytes of data that were leaked. Because you can not password-protect a torrent, once the magnet link is out there, that is it. I just want to unpack the PAK files and have a look at the artwork and music.

Crash logs

Below is one of the crash logs. The username is “ovyhovskyi”. Interesting.

Below is one of the Stalker 2 crash logs. This might be interesting to you.

Download the leak with this link.

208
magnet:?xt=urn:btih:1aa59fe7f247f634f3f7824791985b795e5f9478&dn=stable%5Fvalidation%5Fb49ee388&tr=udp%3A%2F%2Ftracker.openbittorrent.com%3A80&tr=udp%3A%2F%2Ftracker.opentrackr.org%3A1337%2Fannounce

Here is yet another file, this is the configuration for the crash log reporting.

Stalker2/Saved/Config/CrashReportClient/UECC-Windows-66E0E3F8453A2F4A4847D0AB1FE57111/CrashReportClient.ini
1
2
3
4
5
6
7
8
9
10
11
[CrashReportClient]
bHideLogFilesOption=false
bIsAllowedToCloseWithoutSending=true
CrashConfigPurgeDays=2
CrashReportClientVersion=1.0
JiraUrl="https://jira.gsc.kiev.ua/rest/api/2/"
bAllowToBeContacted=true
bSendLogFile=true
CanSendWhenUIFailedToInitialize=true
UIInitRetryCount=10
UIInitRetryInterval=2.0

Whoever was testing this build was running an AMD Ryzen 7 7700X 8-Core Processor and an AMD Radeon RX 6700 XT 12 GiB. Not bad. The game will be using Nvidia DLSS, this might be very demanding, I wonder if my RTX 2060 would be enough to run this game? It might be very scalable if it is using the Unreal 5 engine.

Build installation

#UPDATE

RU

Обещанная расшифровка билда «S.T.A.L.K.E.R. 2».

Решили вопрос расшифровки энтузиасты с Discord-сервера «RedProjects».
Все желающие уже могут поиграть и просмотреть модели через Umodel/Fmodel.

Ключ дешифровки: tKQV3IAeBfvdBBTyD8kqhnsxus0xUlgH – 32, 0x744b515633494165426676644242547944386b71686e737875733078556c6748 – 64 в хексе. Ключи для ассетов (для вьюера – первый).

Билд можно запустить, скачав и переместив файл PalCoreAPI.dll в директорию \Windows\Stalker2\Binaries\Win64.
Ошибку, связанную с ucrtbased.dll можно решить, забросив одноимённый файл, прикрепленный к посту в \Windows\Stalker2\Binaries\Win64.

Предупреждение: загрузка может занять длительное время, не спешите выключать.

Ссылка на скачивание через магнет-ссылку: magnet:?xt=urn:btih:1aa59fe7f247f634f3f7824791985b795e5f9478&dn=stable_validation_b49ee388&tr=udp://tracker.openbittorrent.com:80&tr=udp://tracker.opentrackr.org:1337/announce

EN

The promised S.T.A.L.K.E.R. build breakdown. 2″.

Solved the issue of decryption enthusiasts from the Discord server “RedProjects”.
All interested can already play and view models through Umodel/Fmodel.

Decryption key: tKQV3IAeBfvdBBTyD8kqhnsxus0xUlgH – 32, 0x744b515633494165426676644242547944386b786e737875733078556c6748 – 64 in hex. Keys for the Assets (for the Viewer, the first one).

The build can be run by downloading and moving the PalCoreAPI.dll file to the \Windows\Stalker2\Binaries\Win64 directory.
The error related to ucrtbased.dll can be solved by throwing the file with the same name attached to the post to \Windows\Stalker2\Binaries\Win64.

Warning: it may take a long time to download, don’t rush to turn it off.

Magnet download link: magnet: magnet:?xt=urn:btih:1aa59fe7f247f634f3f7824791985b795e5f9478&dn=stable_validation_b49ee388&tr=udp://tracker.openbittorrent.com:80&tr=udp://tracker.opentrackr.org:1337/announce

Required files

Download the required files from the vk.com post.

https://vk.com/wall-165011456_51716.

If this is not accessible, the DLL files may be found here: https://www.securitronlinux.com/arma3/dlls.zip. Put both DLL files in the stable_validation_b49ee388/Windows/Stalker2/Binaries/Win64 folder replacing the existing files and then the game should run. You need at least 25 gigabytes of RAM and an RTX 4090 to get this to run at a playable frame rate. It is not very optimized at all. Hopefully, this will be worked on a lot, this needs a lot of work for sure.

Stalker 2 main menu. This looks very nice.

All guns in Stalker 2 so far

  • Vulcan
  • AKU
  • PM
  • Sawn-off
  • TOZ-34
  • AK-74
  • VSS Vintorez
  • AS Val
  • PKP
  • Tunder
  • Bison
  • TAR-21
  • SPAS-12
  • USP
  • IWI CARMEL
  • Gauss Rifle
  • Remington 870
  • Remington 700
  • MAC-10
  • Kriss Vector
  • RPD
  • SVD
  • SVU
  • DP-12
  • APB
  • GP-37
  • М416
  • TAURUS 444
  • RPG-7
  • M1A
  • OTs-2 Kiparis
  • Saiga
  • MR-5

9 thoughts on “The Stalker 2 dev build has leaked on the Internet.”

  1. I got to launch in english…but the launched in Russian…also option menu is not active in game…could you please help…thank you

    Reply
  2. I had some troubles starting this game, it was consuming all my VRAM, however, I found a very easy fix for this. In the directory: stable_validation_b49ee388\Windows\Stalker2\Saved\Config\Windows, I located Engine.ini and added this line of code:

    [/Script/Engine.RendererSettings]
    r.TextureStreaming=True
    r.Streaming.PoolSize=9000

    The purpose of this code is to limit the amount of VRAM the game consumes, I have the 10 GB version of the RTX 3080 so I limited it to 9 GB (I tried limiting it to 10 GB but it still caused a crash) so yeah, if you have the same problem just set your VRAM amount in the .ini file with the code I added. Obviously, you have to add a little bit less GB VRAM that your GPU has, in mb, so for example if you have an RTX 2060 which has 6 gb of VRAM that it’s recommended that you give it 5gb so 5000mb. The game is horribly optimized tho, it even ran pretty bad on my computer, but it’s a nice preview.

    Reply
  3. when i click stalker2.exe it says unable to start build, error code: 0x941. what should I do to start the game?

    Reply
    • Put the replacement dll files in the appropriate folder.

      The build can be run by downloading and moving the PalCoreAPI.dll file to the \Windows\Stalker2\Binaries\Win64 directory.
      The error related to ucrtbased.dll can be solved by throwing the file with the same name attached to the post to \Windows\Stalker2\Binaries\Win64.

      I uploaded the files here: https://www.securitronlinux.com/arma3/dlls.zip

      vk.com seems to be down.

      Reply

Leave a Comment

This site uses Akismet to reduce spam. Learn how your comment data is processed.