After having Niko take a nap at the upper level of the refuge, the game would momentarily soft lock.

This is, at the time of this bug report, my first playthrough with the mod.

MSI Z390M Gaming Edge AC
i7-9700K @ 5.0Ghz (Overclocked)
Asus STRIX GTX 1070
24Gb DDR4 RAM
OS on a M.2 512Gb SSD.
Game installed on a WD 4Tb HDD.


At first, the game would have to be forcibly shut down, as Niko going to sleep does not properly close the game. Instead, it leaves a hanging window that returns a "Not Responding" state by Windows.

Starting the game, after forcibly closing it, would bring a reappearing hanging window that is now white instead of anything else. After about a minute, an error message along the lines of "OpenAL" error is returned (This might've said "GL" instead, but my memory does not serve me well.


I'm unsure how many points are relevant to bring, but these may seem related to the issue.

Spoiler!!!
This game was started after a NG+ completion on the base game, without requesting the Entity to reset the game for you.

The splash screen for the base game had been presented at first startup. Though, it's clear the mod is working in some manner, with the modified options and Discord's updated status on completion.

The solstice track for the room plays for the office room with the computer, on the first playthrough. The second time this area was visited, an unknown song had played. Perhaps this song is for Fading memory?

The timer ticks down for a seemingly arbitrary date (Screenshot taken on Aug 26). Could this be the date the Solstice DLC was released?
https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=2585765062

The clock of Windows has been modified to force a 0:00:00 timer state. Nothing of significance had occurred and the timer had been automatically set back to its original time.

Wallpaper engine (known to interfere with gameplay) has a rule set to stop running when OneShot: Fading Memory is started up.

This issue is automatically resolved, and gameplay has resumed normally after. Simply restart the game, as needed, and be patient to see how the attempt plays through.


It appears the clock is a separate bug and might be unrelated. After resuming the game normally, the clock had found its original state of being deactivated.

Original State
https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=2585783190

After going up to the "Roundabout" sightseeing spot and returning, the clock had once again operated with a timer going down.