So, to truly earn my stripes I’m diving into this epic new DLC update, and you’re coming with me!
Is it because my elaborate storage system got blown up by a particularly enthusiastic creeper? Or could it be because Illumination’s Minions mashup is getting an exciting update, and that update lands today! Now, I’d love to call myself an “agent of chaos” but I don’t think I’ve truly earned that title yet (especially when all my builds tend to feature the same copper kitchens). They will just learn when some other company will sue them because some of their work is blocked from saving states.My Overworld certainly feels more chaotic today than it did yesterday. I already told their support that this "feature" has more of a bug, but well, companys. "Safe files" is blocking every writing access to windows standard user folders. That made me think and I checked Bitdefenders logs. Then, I came to safe a file from an email to one of windows standard folders (music, videos, downloads, documents.). Well, maybe a bug ffrom the latest Bethesda update, I thought. But after some searching I found there simply were no safes I made. At first I imagined a failure in loading the latest safe game. But imagine my surprise as I found nothing of my recent built buldings. A day afterwards I tried to load the safe game. I played about 3 to 4 hours, saving some times because I was building a settlement. Shortly after I installed Bitdefender I played Fallout 4. On the next screen deactivate the "safe files" (sichere Dateien) option. It is approximately in the middle of the window on its right side. On the window that opens, choose "show functions" (Funktionen anzeigen). Right click and choose "show" (Anzeigen). I do not have the english version of bitdefender, so I have to guess how the "feature" is called there, but I will try. Because of this thread and my own experiences with Bitdefender I was able to track the bug down. This also can be a problem when saving for some programs or games. It is definitely one of Bitdefenders new "features".
0 kommentar(er)
