For anyone asking for NV version. Porting the mod is most likely as easy as opening it in NVSE-launched GECK and recompiling the scripts (resaving all the Scripts and Quests). I don't have New Vegas so I can not test the result myself. You can try that on your own or PM me for a link (under condition you'll extensively test it and report back)
It's FOSE requirement. Fallout executable version is irrelevant for virtually all mods, but if any of those require FOSE which in turn requires specific fallout3.exe versions to work, you won't be able to use such mods (and there are many). You can probably still replace or patch the exe.
Built-in save system is very rudimentary and can be prone to severe bugs. This adds many convenience features seamlessly and alleviates the risk of the latter. The primary point is always having multiple well-organized checkpoints to revert to, automatically and without any save folder bloat.
Thank you, thank you, thank you!!! This mod really "saved" my ass! LOL. Had the hankering to replay Fo3 with some new mods I noticed about a month ago, and reinstalled everything, started playing, but got CTD's on saving about 20 hours in. Uninstalled/reinstalled (2 more times!) but kept getting the .tmp file extension on saved games and CTD's. Could not figure out WTF to do. Then I stumbled across this mod. Gave it a try, and helps me get around the problem!
It doesn't solve it entirely, I still OCCASIONALLY get the .tmp file extension on saved games, but I just delete those (for example I might get: AutoSave 2.fos AutoSave 2.fos.bak AutoSave 2 fos.tmp
I'll just delete all three of those files, load game from last autosave, which I guess uses AutoSave 1, 3 or 4. I have to blow myself up first, then I can continue as normal.
Yes, I used the "blow-yourself-up" trick before I started using this mod, but that was only a temporary fix. It got so bad, it didn't matter if I had done that or not, the next save caused a CTD.
So I've been able to continue way farther into this game than I would have without this mod. Again, thanks very much. At least my head doesn't hurt so much nowadays (since I quit beating it against the desk on every CTD. LOL)
Seem to be running into a problem while the mod is activated, which is that the mod blocks me from quick save/load. Did anyone else encounter this problem perhaps?
This mod works well as long as I stick to the default keys for quicksave and quickload. But when I attempt to change them, things go awry. In particular, I'd like to use F6 for quicksave and F9 for quickload (a habit formed by years of playing FPS games). I use the console command to set the values:
set rmSvKeySave to 64 set rmSvKeyLoad to 67
Afterward, F6 works properly for quicksave but pressing F9 has no effect. Furthermore, I can't bring up the settings menu via Ctrl+F9 (or Ctrl+F8 either). Setting quickload back to its default of F8 restores the functionality.
I checked the relevant INI file and F9 is not currently mapped to anything else as far as I can tell. Are there restrictions on which function keys can be used for these operations? Is something special needed to use F9 for quickload?
You should unbind F9 from its default (Quickload) or anything else in the game settings menu probably. And don't forget to save after changing the variables — these values are stored in save files themselves, loading older one will revert your changes back
Thanks for the reply. I did check both the INI file and the FO3 in-game key bindings to make sure F9 wasn't in use.
And I eventually figured out I need to save after changing or they'll revert next time. But changing the quickload binding in the current session doesn't work for the current session, so saving won't affect that, right?
Using this over CASM, as I had the awful invincible enemies problem.
The only real addition I would have liked is disabling notifications in the top-left, unless you already can and I missed it. Otherwise, it seems to be ideal.
63 comments
This adds many convenience features seamlessly and alleviates the risk of the latter.
The primary point is always having multiple well-organized checkpoints to revert to, automatically and without any save folder bloat.
It doesn't solve it entirely, I still OCCASIONALLY get the .tmp file extension on saved games, but I just delete those (for example I might get:
AutoSave 2.fos
AutoSave 2.fos.bak
AutoSave 2 fos.tmp
I'll just delete all three of those files, load game from last autosave, which I guess uses AutoSave 1, 3 or 4. I have to blow myself up first, then I can continue as normal.
Yes, I used the "blow-yourself-up" trick before I started using this mod, but that was only a temporary fix. It got so bad, it didn't matter if I had done that or not, the next save caused a CTD.
So I've been able to continue way farther into this game than I would have without this mod. Again, thanks very much. At least my head doesn't hurt so much nowadays (since I quit beating it against the desk on every CTD. LOL)
set rmSvKeySave to 64
set rmSvKeyLoad to 67
Afterward, F6 works properly for quicksave but pressing F9 has no effect. Furthermore, I can't bring up the settings menu via Ctrl+F9 (or Ctrl+F8 either). Setting quickload back to its default of F8 restores the functionality.
I checked the relevant INI file and F9 is not currently mapped to anything else as far as I can tell. Are there restrictions on which function keys can be used for these operations? Is something special needed to use F9 for quickload?
And I eventually figured out I need to save after changing or they'll revert next time. But changing the quickload binding in the current session doesn't work for the current session, so saving won't affect that, right?
The only real addition I would have liked is disabling notifications in the top-left, unless you already can and I missed it. Otherwise, it seems to be ideal.
Anyway, nice mod, this one is a must install for me
set rmSvKeySave to 62
Number 62 here is a scancode for F4