While playing on the new Sakhal terrain (DayZ 1.30), the game client consistently freezes/hangs in one specific location: the main road bend leading towards the Airport (coordinates around pos=<6348.1, 7403.8, 5.4>).
The crash is highly specific and direction-dependent:
It only happens when moving towards the Airport (when the engine attempts to stream in and render airport structures).
It does not happen when moving away from the Airport or looking down at the ground.
When the freeze occurs, the client stops responding to the network loop, causing the local server to drop the connection with the error: Player kicked from server: Lost connection with host (No packets from client).
Root Cause & Visual Settings Analysis:
Through systematic testing, I isolated the exact graphic settings triggering this loop. The crash is caused by an asset/texture streaming conflict within the Enfusion render pipeline when set to higher profiles:
Trigger Settings: Setting Postprocess Antialiasing to High/Extreme OR Object Detail to High/Extreme causes an immediate client lock-up at the threshold of loading the airport.
Workaround Status: Lowering Postprocess Antialiasing to Medium and Object Detail to Medium completely eliminates the freeze, allowing smooth passage through the zone.
Extracted Log Proof:
The exact moment of the rendering failure is captured in the client crash log (error.log) right before the entity rendering loop breaks down:
13:34:50.911 RENDER (E): Error: invalid texture, assuming 1D and have 2D
Immediately following this line, the engine falls into an infinite warning loop trying to parse frozen lakes/ponds assets around the airfield:
13:34:52.661 ENTITY (W): Unknown object class 'pond' (dz\water_sakhal\ice_lake\sakhal_50x50_ice_lake.p3d)
13:34:52.721 ENTITY (W): Unknown object class 'pond' (dz\water_sakhal\ice_lake\sakhal_50x50_ice_lake_clear.p3d)
Additional Core Behavior (Corrupted Storage Loop):
Every single time this rendering crash occurred, my player profile/server state became corrupted. I was unable to reconnect to the server at all, getting stuck in a disconnection loop. The only way to successfully log back into the server was to manually delete the server's storage folder to reset the world/character state.
Because of this corrupted state loop, I intentionally kept only two essential mods loaded: @CF and @VPPAdminTools. These were used strictly as diagnostic tools so I could use the admin panel to quickly teleport back to the exact location and resume testing after deleting the storage directory. We can confidently rule out these tools as the cause, as the root error originates directly from the native Enfusion render pipeline (RENDER (E): Error: invalid texture).
Hardware Specs:
CPU: Intel Core i5-1360KF
GPU: NVIDIA GeForce RTX 3080 Ti
RAM: 32 GB DDR4/DDR5
Storage: High-Speed SSD (Dysk D)