Installation of Modification:
- Part 1
German SoC-Version with Patch 1.006 is highly recommended for installation of the mod.
Steam-, GoG-, Silver- or Gold-Versions can work. But must not.
Old good SoC-DVD with 1.001, patched to 1.003, 1.004, 1.005 and 1.006 is best for.
The mod need min. 4 Gb RAM and 64-bit operating system to work!
R1-Render is completly removed from game engine. Only R2-Render work!
The mod need unpacked ca. 12 Gb space on hard drive.
- Part 2
Create a backup of bin-Folder from SoC-Installation!
Create a backup!
Do it!
- Part 3
Complete remove/delete any other mods.
Remove/delete/rename the bin-Folder from SoC-Installation.
Please note: Wlads "Soljanka" 2015 Extended Edition is no update to the old "Soljanka" Final
or previous versions of the 2013 Edition!
- Part 4
Extract the content of the 7zip files into your main Stalker-folder. Let the files overwrite the existing files.
Eventually it is needed to change the parameters of "fsgame.ltx" into "$game_data$ = true|true|"
- Part 5
Start Stalker. Change settings. Play new game.
Caution! Stalker needs to be restarted if you change old or new graphic-settings, even if the game does not tell you to do so! It is recommended to restart the Stalker game after you have changed major graphical settings. Only in that way it can be ensured to have it saved right by the game.
- KNOWN ISSUES:
You may encounter a wrong update of your actor due to the high script-loading of the mod.
If you start a new game and you do not see the time within the HUD and Backpack-Volume-Notification, the actor was not fully updated. Mostly it can be fixed by reloading the save game. If you are still encountering the problem - close the game and start it again.
It is alyways advisable to have the game-intro running for a few moments before skipping it.
The same applies to savegames! If the savegame gets loaded without a crash but you do not see the time within the HUD and Backpack-Volume-Notification, the actor was not fully created.
Just reload the savegame until you see those notifications.
I regret to have not found the reason for this rare bug yet.
