Closing the character inventory screen in-game causes the game to freeze for an entire second. Occurs every time on starting the game. Started to occur seemingly "randomly" five days ago and was, for whatever reason, only resolved by changing servers. When joining the previous server again, the issue was gone.
Description
Details
- Severity
- Minor
- Resolution
- Open
- Reproducibility
- Always
- Operating System
- Windows 10 x64
- Operating System Version
- 22H2 Build 19045.4291
- Category
- Game Freezes
- Close the game
- Launch the game
- Join a server (can be done from launcher)
- Open character's inventory screen once in-game
- Close character's inventory screen: The game freezes for a whole second. Every time an inventory is closed.
Occurs every time upon starting the game. It is my experience that this started to happen randomly, out of the blue, on January 19th and it has not stopped for days. It was only resolved by changing server, joinin a new server, leaving the new server and re-joining the old server. The issue was then completely gone.
But before cycling servers: No amount of reboots, verifying Steam game files or deleting all the configuration files on Windows 10 in the "Documents" folder has resolved this. This issue simply did not go away. No modification has been done to the game. It's the normal main/stable branch of DayZ from Steam.
This occurs on DayZ main/stable:
Launcher version: 1.6.158923
Game version: 1.26.159040
Branch: main / beta branch not specified
Annoying workaround: Each time the game launches you have to:
- Go into the Options menu
- Disable the "Show HUD" option
- Click Apply. Game freezes for 5 seconds.
- Re-enable the "Show HUD" option
- Click Apply. Game freezes for 5 seconds.
- The issue is now resolved; only until the next time the game is started.
Permanent workaround (unknown why this worked): Join a different server. Open the inventory; no freeze. Exit the game. Join the old server again. Open inventory; no freeze. The freezing issue had somehow been resolved by swapping server back and forth.
After resolving the issue with the workaround... the issue is no longer reproducible. So the main cause is "random". But while affected, it was 100% reproducible by simply playing the game normally.