Just found it amusing, and I have no idea why it happens but, outside Starlight Drive-In towards the train tracks is a wrecked van. Whenever you hit the save key, the back door flings open.
Is anyone else having issues with this recently? I have confirmed that a full save via this mod are not as stable as menu full saves. on my machine anyways.with my MOD list. blank,wrong or missing save pic. ctd on load. this mod was last updated October 2017. F4SE and MCM have both been updated a number of times since then. I consider this an essential mod and don't want to stop using it.
It's good more people are developing mods for MCM, but may I ask why create a mod that is already existent with other MCM mods like Survival Options and Unlimited Survival Mode? Is it to showcase different methods of implementing a same function?
I wasn't aware of any other mods with this function. Either way it was a mod I made for Skryim and started to play Fallout 4 so I decided to make a similar one. Also, some people might want just the save function without all the other options in those mods
Exactly. It's a good idea to make only full saves instead of quick saves. So why sould I install another mod that has this feature when I only need this one?
Not everyone plays the game in survival mode. Using quicksaves and autosaves usually gets your saves corrupted in the long run, with more chances of random CTD. So having a mod that does a full save at the press of a key without all of the bloat from the other mods (survival options) is useful.
That’s my problem I use HotKeys. MCM all the game assignable favourites and lots of Mods that requires assigned keys and don’t have anything spare or might be needed soon. If only the Quicksave could be un-assigned as I never use quicksave ever.
Hard to believe you don't have one free key out of 110 besides F5. Conflict control is done by MCM, not my mod, so I don't really have control over how that works
Here's something weird: the mod saves via hotkey just fine, but sometimes the screenshots in the load menu from are from a 1 or 2 or a few saves previous to the save it actually represents. (Hope that made sense.) One of the screenshots in my load menu is actually blank, ie just kind of a grey outline of the vault tec logo without text.
The text to the left of the screenshot describing the area where the save took place is accurate, and the correct save loads but, yeah, the screenshot sometimes shows the screen from a few saves ago. So, if you save a lot like me, it can be a bit difficult to go back a save or 2 with any degree of accuracy especially if you have multiple saves in the same area.
Maybe it's just me, but that's never happened before after a couple thousand hours making hard saves. Dunno what it could be - the only thing that comes to mind is that I'm still running 1.10.20 so have the previous-to-current F4SE (so I installed the MCM geared for 1.10.20). Could that be it? I know, I know... very strange.
Yeah, I would recommend running the latest versions of both F4SE and Fallout 4 as that is what I developed this on. Though it shouldn't make a huge difference as its fairly small. As for the bug, I'm pretty sure it is nothing on the end of my mod, its probably more to due with the same function in papyrus. I'd imagine the 'save' button on the main menu is done directly through the executable.
Give Feedback
38 comments
just wondering cos i was considering reinstalling FO4 because of this mod
I have confirmed that a full save via this mod are not as stable as menu full saves.
on my machine anyways.with my MOD list.
blank,wrong or missing save pic.
ctd on load.
this mod was last updated October 2017.
F4SE and MCM have both been updated a number of times since then.
I consider this an essential mod and don't want to stop using it.
The text to the left of the screenshot describing the area where the save took place is accurate, and the correct save loads but, yeah, the screenshot sometimes shows the screen from a few saves ago. So, if you save a lot like me, it can be a bit difficult to go back a save or 2 with any degree of accuracy especially if you have multiple saves in the same area.
Maybe it's just me, but that's never happened before after a couple thousand hours making hard saves. Dunno what it could be - the only thing that comes to mind is that I'm still running 1.10.20 so have the previous-to-current F4SE (so I installed the MCM geared for 1.10.20). Could that be it? I know, I know... very strange.