Are the issues with loading saves after quitting to the main menu only present in Fallout New Vegas, or other Bethesda games with the same engine too? I don't usually do that anyway, but I will make sure I don't in future.
Wait! Seriously, THIS causes issues to the game? Honestly at this point I ought to know better but here we are again.
Just for clarification sake! Is this due to the script extender not being facilitated properly by the game, or does the base game already screw its own native scripts to hell this way regardless of third party add-ons?
It's an issue with the game itself. One of the most visible ways to see it is if you die and immediately reload a save in that same area, you'll see your character's blood spatter still floating in the air from where they got shot.
Yeah! Hell I've been playing this thing since it came out decades ago, and it still surprises me in the ways that it can f-ck up.
But the most recent issues related to this exact phenomena that is still fresh in my mind was in Fallout 4 where I mistakenly discharged a weapon in Goodneighbor, and of course in typical Bethesda fashion the entire town came after my character. So what to do except reload the last autosave, only for them to attack again for no apparent reason what so ever.
Yes I am absolutely positive that conflict was not initiated on that save.
And yes as soon as I exited the game and relaunched it, nothing happened.
I can't confirm this, but I think this mod causes Quick Select's HUD to disappear after some time. I only say that because it happened after I installed this mod. Figured I should bring this up in case anyone else runs into the same problem.
I see, can you share the technical root cause around that? This is surprising, old folklore among bethesda games was to go back to main menu to clear the scripts, as if you reload while in game you'll definitely run into scripts and other data carrying over. And I've been doing that on my new save, oof.
The whispers from the grapevines told many a warnings about the old engine running the core of Beth Esda, Wizards are the only ones figuring out this forbidden knowledge
32 comments
IF YOU WANT TO SUPPORT MY WORK CONSIDER DONATING
Edit: Fixed
Honestly at this point I ought to know better but here we are again.
Just for clarification sake! Is this due to the script extender not being facilitated properly by the game, or does the base game already screw its own native scripts to hell this way regardless of third party add-ons?
I'll believe both!
But the most recent issues related to this exact phenomena that is still fresh in my mind was in Fallout 4 where I mistakenly discharged a weapon in Goodneighbor, and of course in typical Bethesda fashion the entire town came after my character. So what to do except reload the last autosave, only for them to attack again for no apparent reason what so ever.
Yes I am absolutely positive that conflict was not initiated on that save.
And yes as soon as I exited the game and relaunched it, nothing happened.
IT JUST WORKS!
https://www.meme-arsenal.com/memes/321b3cdd8d21162edff6e3529c988d66.jpg
Is it that?
Thanks!
This is surprising, old folklore among bethesda games was to go back to main menu to clear the scripts, as if you reload while in game you'll definitely run into scripts and other data carrying over. And I've been doing that on my new save, oof.