Search the Community
Showing results for tags 'bethesda'.
Arthmoor posted a topic in Unofficial Fallout 4 PatchSo it appears we've been hit with an impenetrable roadblock in the workshop system. Bethesda, for reasons unknown, has made some rather... bad changes to how things work. If you don't want to read through the details, the summary of the situation is this: Settlers recruited via the radio beacon (basically all of them really) or settlers placed via console commands (shame on you people!) will begin to exhibit gear, appearance, gender, and even race changes after a certain amount of time. My own testing shows this is tied to how long the respawn timer is for the game. Cut it to one hour, you can get the problem almost immediately. Raise it, and you can probably delay it, but it will cost severely in performance elsewhere. In the end, it's an engine issue we cannot solve. Eventually, just standing around in the cell WHILE THE SETTLERS ARE WITH YOU will result in them changing if you turn your back on them, even for just a few seconds. Thread on Bethesda.net: https://community.bethesda.net/thread/53871 Let them know this needs to get fixed! Anyway, here's the details, as explained by Sclerocephalus: IMO, this may sound a death bell for the project. Settlement issues are a large portion of what's wrong with the game and it has taken him/us 4 iterations of work to get to the point we're at now, and now it's all for nothing. Considering Bethesda themselves screwed this up for reasons unknown, I don't know if we can trust them not to completely screw something ELSE up later on that gets in the way of fixing a broken quest, bad flags on NPCs, or even stuff as simple as fixing typos. We are already operating under restricted conditions with being unable to do any sort of mesh fixes and being severely limited in the ability to do placed reference corrections. Adding all of this makes it even less useful as a project now. Only Bethesda can ultimately fix this, so IMO, people should start directing bug reports to them. Make them realize that as long as they're screwing up fundamental systems for resource management reasons, we can't do anything. There was absolutely no reason to have done this either since NPCs placed via script calls don't need to be persistent outside of their settlements and they had no reason to believe that performance would improve by cycling them repeatedly while you're in the settlement. In fact, logic dictates it does exactly the opposite. A few additional comments from Sclerocephalus:
Hi. I have been experiencing a bug in fallout 4: In the blind betrayal mission, Danse becomes enemies with the brotherhood of steel if you keep him alive, i kept him alive and decided to join the Railroad, meaning I destroyed the Prydwyn and ended the game with that faction. I went back to Listening Post Bravo and wanted him to be my companion, however, when i interacted with him, there was no response! My character would spout: "Excuse me, paladin danse?" and Danse wouldnt reply, I couldnt access the trade menu or engage in a conversation. It would be amazing if you fixed this, as Danse is my favourite companion and it is a damn shame that Bethesda blocked me from engaging with a former companion who is enemies with the Brotherhood because I am enemies with the Brotherhood!! There is no logic! It would really enhance my and others' experience with the game. Thanks