Unstable operation of the game client

At the moment, the whole problem with periodic pouring in most people is associated with a voluminous update.Since the client uses the UE3 engine, the data processing goes into one stream, which in turn gives itself a lot of felt and therefore the configuration of the computer itself, in this case, it does not matter.

If, after the update, you still have a problem with periodic pouring and departures, but there were no previously, then delete the files: …\S1Game\CookedWindows\LocalShaderCache-PC-D3D-SM3.gpk And …\S1Game\Config\S1*.ini.
It is these files that may contain data that were initially incorrectly configured if you downloaded them together with our new client earlier.

itIsImportantThatDuringTheFirstLaunchOfTheClient,AfterDeletingFilesHigher,InS1EngineIniTheyAreDisconnected:

“UseVsync=false

[Engine.GameEngine]

bSmoothFrameRate=False”,

andAlsoVerticalSynchronizationAndRestrictionOfTheFpsAndInTheSettingsOfTheGraphicDriverWereDisabled.

weDrawYourAttentionToTheFactThat first theLaunchCanBeVeryLong,AfterRemovingTheseFiles, up to the freezing of the processtera.exe In the dispatch of tasks (The status “does not answer”) – In fact, the client caches, adds and checks all the necessary graphic files.This process takes a lot of time due to work in one stream, which we have already indicated earlier.
If nothing happens for a long time, then leave the client for 10-15 minutes, he will load.

After the first launch, the prolaxes will still be for some time, since the remaining files continue to caching directly in the game.But as soon as you run the location once, the next time the lags either disappear altogether or will be minimal.

Demonstration of gameplay without and with customer caching: https://youtu.be/Zp9yTHu20To?si=rsIVQBAHIqjiEjZ4