Jump to content

Don't Let Steam Update Screw your F4SE


PLuv

Recommended Posts

Ok, I'm a little pissed at myself. But, I learned my lesson. From now on I will ALWAYS keep a copy of my current working Fallout4.exe ... so that when Steam automatically upgrades the *.exe and messes up the F4SE I can go back to the prior version while waiting for f4se.silverlock.org to update the F4SE. So, I guess that can take a day or two of going thru frigging withdrawals. Thank you Steam, for the lack of a F****ing heads up warning. You suck.

 

 

EDIT: I followed the instructions in the following video and it worked PERFECT!!!! Although for next time, to save myself all the nonsense, just make a BackUp Copy of your working Fallout4.exe. Now, when Silverclock upgrades their F4SE, I'll use the new Fallout4.exe from steam. This is a great video, btw.

 

Edited by PLuv
Link to comment
Share on other sites

Honestly, Bethesda hasn't had a worthwhile bug fix or performance optimization patch since 1.7.15. Everything after Nuka World release has been mostly for CC updates/content. They can't even be bothered to clean up their esms everytime they update. Without the tools and mods to mitigate their ineptitude, modding would be a serious chore.

Link to comment
Share on other sites

That's why I always start my game through F4se and tell steam to only update when the game is started. Steam doesn't even know I'm playing the game.

 

I don't need their CC-bloatware and - as has been said - they haven't had a serious update sind the last DLC.

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...