ForgottenGlory / Living-Skyrim-2

24 stars 10 forks source link

can't save #450

Closed CGDannim closed 3 years ago

CGDannim commented 3 years ago

**If you are reporting a crash to desktop, please attach your NET Script Framework crash log. This can be found in MO2's Overwrite folder.

If possible, please also attach a copy of your most recent save before the issue occurred.**

Save842_1DBF690B_0_416E75626973_LabyrinthianWorld04_082214_20200924194635_37_1.zip

Crash_2020_9_20_4-23-14.txt

Please check back on your bug request periodically. I will ask for more details sometimes and if they are not provided I will eventually close the bug report.

LS Version 2.3.0

Describe the bug I can no longer save. tmpsaves.zip

0 byte .tmp files are generated, but nothing else and Skyrim itself CTDs instantly on trying to save. No issue loading from any saves, but cannot then save from any.

I can Fast travel and move in and out of any cities/dungeons without issues.

To Reproduce Any save will CTD.

Expected behavior I expected to be able to save as I have 841 times before. ;)

Screenshots If applicable, add screenshots to help explain your problem. IF YOUR SCREENSHOT CONTAINS NUDITY DO NOT PUT IT ON GITHUB. Additionally, if your report applies to a specific object, make sure it is selected with the console open. Reports without this will be closed.

Additional context Add any other context about the problem here. image

I've noticed that my skse files are 0k up until entering Labyrinthian when they then jump to 2.4MB. My issue occurred after that. As mentioned above though reverting to an earlier save with a matching 0kb skse still results in a CTD when saving.

CGDannim commented 3 years ago

Was being too lazy I guess; looked at the log and tracked the issue to a Vitality mod item. Since I wasn't using that mod at all I disabled and have since been able to save.

The skse co-save files are still an 'issue' though. Sticking at ~2.4MB so far.

Any advice/recommendations?

ForgottenGlory commented 3 years ago

Fixed 2.4.1

CGDannim commented 3 years ago

Hi,

I understand that the bug is fixed with Vitality, but is there any recommendation for the co-save size (now 3MB)? It causes a significant delay (couple seconds/per) and likely won't get better without intervention. And I'd rather not try save cleaners and the like as they're not recommended and void support - unless told otherwise.