I've run into a bizarre situation with Fallout 4. In the included files, the cell containing the Hopesmarch Pentecostal Church has 2 references the UFO4P edited. Users have reported to us that this generates invisible ground and they can't jump down through the roof of the church.
After some wrangling I was able to fix the problem by completely removing the entire CELL record (and all its children) from the file. I then redid the 2 edits in the CK using the PC copy of the patch, saved, and tested it. Sure enough, everything worked fine.
Then I loaded up xEdit and the PS4 copy of the patch. I removed the entire CELL from it, saved, exited. Loaded xEdit back up afterward with both the PC and PS4 patches. I copied the data from the PC patch back into the PS4 patch. Saved and exited again.
When I tested the PS4 patch to be sure it worked, I found that it did not. Other members of the patch team have been able to confirm that this result is consistent. PC patch works, PS4 patch does not.
So I cut both files down to just the cell with the 2 edits in it for each file and tried that. Sure enough, one works, the other doesn't.
I have included 2 screenshots to illustrate the issue, because even the CK can see that the landscape collision has been re-enabled on the broken file. It's the yellow grid that shows up in the hole in the church's roof.
I have no idea what's going on here, but the only thing I can tell for sure is that copying the data from a working file into one that doesn't have it results in the second file being broken. So xEdit is missing something we're not able to see. Unless it has something to do with the Version Control data since the "Version Control Info 2" field has a 0F in the working file, and 00 in the one that doesn't. It's the only visible difference I can see when comparing, and xEdit even shows the data size for the CELL record is one bit different somewhere. Fallout4.esm has the 0F in the VC2 data as well.
It does not matter whether the file is flagged ESM or not, I tried it both ways to rule that out.
xEdit also does not seem to break it if the CELL record already exists and the new data is added to it. So we have a way to work around this until the bug is identified and fixed. I'm using xEdit 4.0.2 as downloaded from Nexus.
For background, what's happening here is that Bethesda disabled landscape rendering in the northwest quadrant of the cell and then placed a bunch of statics to simulate the church being partially buried. The broken file is causing the collision data to reappear but not the visible landscape that would be associated with it.
Landscape Collision Bug.zip
I've run into a bizarre situation with Fallout 4. In the included files, the cell containing the Hopesmarch Pentecostal Church has 2 references the UFO4P edited. Users have reported to us that this generates invisible ground and they can't jump down through the roof of the church.
After some wrangling I was able to fix the problem by completely removing the entire CELL record (and all its children) from the file. I then redid the 2 edits in the CK using the PC copy of the patch, saved, and tested it. Sure enough, everything worked fine.
Then I loaded up xEdit and the PS4 copy of the patch. I removed the entire CELL from it, saved, exited. Loaded xEdit back up afterward with both the PC and PS4 patches. I copied the data from the PC patch back into the PS4 patch. Saved and exited again.
When I tested the PS4 patch to be sure it worked, I found that it did not. Other members of the patch team have been able to confirm that this result is consistent. PC patch works, PS4 patch does not.
So I cut both files down to just the cell with the 2 edits in it for each file and tried that. Sure enough, one works, the other doesn't.
I have included 2 screenshots to illustrate the issue, because even the CK can see that the landscape collision has been re-enabled on the broken file. It's the yellow grid that shows up in the hole in the church's roof.
I have no idea what's going on here, but the only thing I can tell for sure is that copying the data from a working file into one that doesn't have it results in the second file being broken. So xEdit is missing something we're not able to see. Unless it has something to do with the Version Control data since the "Version Control Info 2" field has a 0F in the working file, and 00 in the one that doesn't. It's the only visible difference I can see when comparing, and xEdit even shows the data size for the CELL record is one bit different somewhere. Fallout4.esm has the 0F in the VC2 data as well.
It does not matter whether the file is flagged ESM or not, I tried it both ways to rule that out.
xEdit also does not seem to break it if the CELL record already exists and the new data is added to it. So we have a way to work around this until the bug is identified and fixed. I'm using xEdit 4.0.2 as downloaded from Nexus.
For background, what's happening here is that Bethesda disabled landscape rendering in the northwest quadrant of the cell and then placed a bunch of statics to simulate the church being partially buried. The broken file is causing the collision data to reappear but not the visible landscape that would be associated with it.
Landscape Collision Bug.zip