2. Yes, the required game version is mandatory. We often have to absorb official updates into our fixes so that everything continues to work properly. Because of this, we will NOT provide older versions of the patch for any reason. Update your game.
3. Removal of mods is not supported by Bethesda. DO NOT deactivate this patch even if you suspect it of causing some kind of problem. You WILL fubar your game and in doing so, you forfeit any support from us.
4. Do not unpack the BA2 assets. Doing so forfeits any support from us. Use the mod as distributed.
5. There is no such thing as a clean save. See #3. Do not follow advice from others claiming this to be true, because it is not, and never will be.
6. If you send me a PM asking about something that's been covered in the readme, sticky posts, or the description of the mod, I will summarily delete the message without a response. All of the information you need is readily available. Read it.
7. We do not support Fallout 4 VR on PC or console. Please do not ask. The data files for the game on VR are not identical to the standard PC version and thus we cannot guarantee compatibility and cannot provide support for anyone trying to use it on VR.
8. We also do not provide patch support for Creation Club DLC. This would require additional expense that few if any team members are willing to put out. Any bugs in this content should be reported directly to Bethesda so they can fix it at the source.
9. Do not post asking about why the DLC is required, simply accept that it is. No, we will NOT provide you a special non-DLC patch or combinations suited only to certain DLCs. We unified for a reason. Required mean REQUIRED. Any posts on this subject will be summarily deleted without a response, along with any replies from other users prior to us noticing them. This is not a democracy. You don't get a vote. Repeat offenders who don't take the hint will be blocked without notice.
Provided by BenRierimanu:
10. Object flicker is not usually the fault of the unofficial patch, please see if your precombine and or previs patch solution is in the correct spot for your load order. For PRP, there's a very big and obvious image on the mod description for what to do there and typically applies to any variant of it, if it doesn't fix the issue, bother me on the respective mod page.
Starting to get why other mod authors have a wall of stickies about stuff like this now, but:
This mod thread is not a general troubleshooting area. We are here to provide support for the use of UFO4P in your games, not to provide general support for every tangentially related thing in your games. We have been noticing lately that these types of posts coming here are leading people to the false conclusion that this patch is responsible for those problems and then they tell others elsewhere and all context is lost. This ends now.
From now on, any post not having something directly to do with the UFO4P itself is not permitted here. Go and use the general forums for your general troubleshooting. Nexus has plenty of people who frequent those areas, and so does Reddit. Please go and use those. There are also a number of mod support chat rooms on Discord you could use as well.
Posts violating this will be locked, removed, and the posters possibly blocked as well.
As was mentioned in other posts, the 2.1.1a update only adds Canary support to help with efforts to track down a potentially lethal engine bug (lethal to your saves that is).
You'll also need to install that in order for the support to be of any value. So please consider doing so. The more people who install this and play with it running, the sooner the cause can be found and presented to Bethesda for a proper fix.
Known issue for PS5 users, PS4 is fine: One of the DLC (Workshops / Wasteland Workshop) has a plugin master file that UFO4P and other plguins depend on that's not named correctly to the ones we expect on other platforms. BGS has to fix this one.
If you are getting messages in Vortex that the archives in UFO4P are not valid, please update to the new Vortex stable version. It has been updated to properly read the new archive headers.
You should be on 1.11.3 or greater for this error to go away.
I would like to point out again, for the umpteenmillionth time though, that this "error" is only an "error" to the mod manager. The game will not have any issues loading the archives. Ignore it if you don't want to update Vortex for whatever weird reason.
A verifiable test case for the stuttering issue has been created by Glitchfinder. As predicted, it wasn't due to anything WE did, but rather something Bethesda themselves needs to fix. I have the files myself and will link them somewhere in the morning for anyone who wants to verify this themselves.
The tl;dr of it though is this: ANY mod which makes an edit of ANY kind to an NPC WILL contribute to the issue. It makes absolutely no difference what kind of edit it is, but the issue was introduced with the NG Update. Not by anything we did to the patch.
EDIT: Here are the files to replicate the test: https://www.afkmods.com/StutterTest.7z
Use a save in Sanctuary Hills next to the workshop. Install the no overrides version first. Run from there to downtown Concord. You should encounter an FPS hit, but no major hitching or stuttering and by the time you get there all the NPC should have been spawned.
Exit the game and switch to the file with the overrides. Reload the Sanctuary Hills save. Run to downtown Concord again. You should notice the difference immediately once you've reached where the 2 bloodbugs usually spawn by the car, and it will become increasingly worse as you continue. Assuming your game doesn't crash, you should eventually be able to reach the spawning area and still see raiders dropping in from above. The stuttering should be VERY obvious.
the unofficial patch bugged the quest with ostwald at the palace of pleasure in nuka world, which does not activate, I only managed to do it by deactivating the mod
The items required are no longer Creation Club if you updated your installation of Fallout 4 to the Next-Gen update. Just like with Skyrim Special Edition, Bethesda now includes several of them as part of the game.
I'm trying to download the patch, but everytime I do Vortex says I'm missing masters. I know that has to do with the DLC, but I only have some, and have no intention of buying the others. Will the mod work if I don't have the masters for the DLC i dont have?
This is the biggest crime on Nexus, when someone finds a fix and doesn't share how it was done. Do you know how frustrating that is? Do you not have six sense? brotha what's that? come on now.
There is no "fix". You have to own and have installed all DLC and the Creation Kit content shipped for free with the recent update, or you can't use the unofficial patch.
I was disabling my mods one by one to find out what caused my stuttering. It bringed me here. Regarding that May 15th sticker, do we have to wait and hope if Bethesda makes a new patch to fix this new issue and until then nodody can use any NPC mod with UF4P? Or, is there any chance you Arthmoor will be able to fix this?
Just asking to know what will be my best approach for a new gameplay. Don't want to play without any of this, UF4P or NPC mods, but also don't believe Bethesda will release any new fix to address this...
We'll all need to wait on Bethesda to fix the issue because only they can. It has absolutely nothing to do with any particular mod, it's an engine issue they caused. Not us, not anyone else.
If you're on PC though, don't worry too much about it. Unless you install a mod that edits literally every NPC you'll probably never truly notice it.
Okay this might sound dumb but, the older file says its for use on gog versions, does that mean I cant use it on the steam version of the game or what?
How to make my companions shut the fck up when using this? Everywhere I go, companion will not stop spamming location dialogue...
Like Codsworth saying the place is messy. It ruins the entire patch, because I'm trying to do dialogues and the freaking robot is in the background going "WHAT A MESS" "WHAT A MESS" "WHAT A MESS"
Well whatever caused all of that isn't because of us and it's not a vanilla issue either. Yes, companions occasionally make comments. It's not "spamming" though since it doesn't happen non-stop. I think maybe you're overreacting to a minor thing :P
So why dont you let the old version of this be used for people who don't want to update? I didn't and was gonna download, but I have to update my game? Makes no sense you can't have old version of the mod.
9701 comments
1. This was created with the official CK.
2. Yes, the required game version is mandatory. We often have to absorb official updates into our fixes so that everything continues to work properly. Because of this, we will NOT provide older versions of the patch for any reason. Update your game.
3. Removal of mods is not supported by Bethesda. DO NOT deactivate this patch even if you suspect it of causing some kind of problem. You WILL fubar your game and in doing so, you forfeit any support from us.
4. Do not unpack the BA2 assets. Doing so forfeits any support from us. Use the mod as distributed.
5. There is no such thing as a clean save. See #3. Do not follow advice from others claiming this to be true, because it is not, and never will be.
6. If you send me a PM asking about something that's been covered in the readme, sticky posts, or the description of the mod, I will summarily delete the message without a response. All of the information you need is readily available. Read it.
7. We do not support Fallout 4 VR on PC or console. Please do not ask. The data files for the game on VR are not identical to the standard PC version and thus we cannot guarantee compatibility and cannot provide support for anyone trying to use it on VR.
8. We also do not provide patch support for Creation Club DLC. This would require additional expense that few if any team members are willing to put out. Any bugs in this content should be reported directly to Bethesda so they can fix it at the source.
9. Do not post asking about why the DLC is required, simply accept that it is. No, we will NOT provide you a special non-DLC patch or combinations suited only to certain DLCs. We unified for a reason. Required mean REQUIRED. Any posts on this subject will be summarily deleted without a response, along with any replies from other users prior to us noticing them. This is not a democracy. You don't get a vote. Repeat offenders who don't take the hint will be blocked without notice.
Provided by BenRierimanu:
10. Object flicker is not usually the fault of the unofficial patch, please see if your precombine and or previs patch solution is in the correct spot for your load order. For PRP, there's a very big and obvious image on the mod description for what to do there and typically applies to any variant of it, if it doesn't fix the issue, bother me on the respective mod page.
This mod thread is not a general troubleshooting area. We are here to provide support for the use of UFO4P in your games, not to provide general support for every tangentially related thing in your games. We have been noticing lately that these types of posts coming here are leading people to the false conclusion that this patch is responsible for those problems and then they tell others elsewhere and all context is lost. This ends now.
From now on, any post not having something directly to do with the UFO4P itself is not permitted here. Go and use the general forums for your general troubleshooting. Nexus has plenty of people who frequent those areas, and so does Reddit. Please go and use those. There are also a number of mod support chat rooms on Discord you could use as well.
Posts violating this will be locked, removed, and the posters possibly blocked as well.
For details on what exactly that means, see Kinggath's mod: https://www.nexusmods.com/fallout4/mods/44949
You'll also need to install that in order for the support to be of any value. So please consider doing so. The more people who install this and play with it running, the sooner the cause can be found and presented to Bethesda for a proper fix.
One of the DLC (Workshops / Wasteland Workshop) has a plugin master file that UFO4P and other plguins depend on that's not named correctly to the ones we expect on other platforms. BGS has to fix this one.
You should be on 1.11.3 or greater for this error to go away.
I would like to point out again, for the umpteenmillionth time though, that this "error" is only an "error" to the mod manager. The game will not have any issues loading the archives. Ignore it if you don't want to update Vortex for whatever weird reason.
The tl;dr of it though is this: ANY mod which makes an edit of ANY kind to an NPC WILL contribute to the issue. It makes absolutely no difference what kind of edit it is, but the issue was introduced with the NG Update. Not by anything we did to the patch.
EDIT: Here are the files to replicate the test: https://www.afkmods.com/StutterTest.7z
Use a save in Sanctuary Hills next to the workshop. Install the no overrides version first. Run from there to downtown Concord. You should encounter an FPS hit, but no major hitching or stuttering and by the time you get there all the NPC should have been spawned.
Exit the game and switch to the file with the overrides. Reload the Sanctuary Hills save. Run to downtown Concord again. You should notice the difference immediately once you've reached where the 2 bloodbugs usually spawn by the car, and it will become increasingly worse as you continue. Assuming your game doesn't crash, you should eventually be able to reach the spawning area and still see raiders dropping in from above. The stuttering should be VERY obvious.
https://www.nexusmods.com/fallout4/mods/38540 - this cause crash game.
Just asking to know what will be my best approach for a new gameplay. Don't want to play without any of this, UF4P or NPC mods, but also don't believe Bethesda will release any new fix to address this...
If you're on PC though, don't worry too much about it. Unless you install a mod that edits literally every NPC you'll probably never truly notice it.
New Tesla Cannon "content".
Like Codsworth saying the place is messy. It ruins the entire patch, because I'm trying to do dialogues and the freaking robot is in the background going "WHAT A MESS" "WHAT A MESS" "WHAT A MESS"