CritLoren
Saves stop loading after save #600
Describe the bug In two separate playthroughs, I've made it all the way to save # 600 before the game inexplicably refuses to load anything after that. I made 7 more saves which all reload fine while I'm still playing the game, but when I exited to desktop and reloaded they all led to nearly insta-CTD on loading, the only save that has worked beyond save #600 is a save I made a few steps and a few seconds after the #600 save. Loading either save and progressing in different ways leads to the same inevitable result, insta-CTD, and by "insta" I mean about a half-second of loading screen before it just gives up entirely.
To Reproduce Steps to reproduce the behavior:
- Save 600 times
- Keep playing and saving after save #600
- After save 600, exit to desktop and try to reload any of the saves after #600
- See error
Expected behavior Expectations are saves work as normal
Save 600.zip 601.zip 602.zip 603.zip 604.zip 605.zip 606.zip 607.zip 608.zip 609.zip 610.zip 611.zip 612.zip 613.zip 614.zip
Crash log crash-2023-01-07-21-46-55.log crash-2023-01-07-21-45-02.log crash-2023-01-07-21-43-55.log crash-2023-01-07-21-42-40.log crash-2023-01-07-20-54-13.log crash-2023-01-07-20-51-52.log crash-2023-01-07-20-49-36.log crash-2023-01-07-20-48-13.log crash-2023-01-07-20-46-52.log crash-2023-01-07-20-44-40.log
Desktop (please complete the following information):
- Yggdrasil VR version: Latest
- Storage type Yggdrasil VR is installed on: SSD
- OS version: Windows 10
- RAM: 16gb
- CPU: AMD Ryzen 7 5800X 8-Core Processor 3.80 GHz
- GPU: Nvidia RTX 3070
- Antivirus Windows Defender
Additional context Only the restate this is the second time it happened, the only obvious parallels I remember was I was wearing enchanted Draugr Lord Armor at the time both saves started crashing.
Sure are these them?
usvfs-2023-01-07_12-59-17.log usvfs-2023-01-08_17-28-09.log usvfs-2023-01-08_18-31-00.log usvfs-2023-01-06_16-47-36.log usvfs-2023-01-06_22-30-16.log
No they should be in the same folder as the crash logger ones On 11 Jan 2023, 01:00 +0000, CourageousTern @.***>, wrote:
Sure are these them? usvfs-2023-01-07_12-59-17.log usvfs-2023-01-08_17-28-09.log usvfs-2023-01-08_18-31-00.log usvfs-2023-01-06_16-47-36.log usvfs-2023-01-06_22-30-16.log — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you commented.Message ID: @.***>
I'm hoping those were the right files? Any luck figuring out what the problem might be?
Hey sorry but it might be good to update engine fixes, it fixed the save size issue.