Ckit Errors

[chucksteel]

Ok guys I'm getting two errors when launching the Ckit, out of the thousands given by default two is not bad but I'm not sure if they are anything to be concerned about.

 

First error,

MASTERFILE: *** Cell FederalRationStockpileChurchExt (0000DF31) combined data is owned by file BTInteriors_Project.esp due to ref BTInt_DRGN_Garden_20 (031F9F75)

I know this is because of DLCNukaWorld.esm but, I only added one misc item. to the cell and didn't change anything that should disable the Pre-Combined Meshes.

 

when looking at the cell in xEdit my mod's PreVis, Pre-Combined Times, and everything else related to Pre-Combined Meshes matches DLCNukaWorld.esm. There are no other edits to the cell other then my one misc. item.

 

Second error,

MASTERFILE: *** Cell Wilderness (00000FEC) combined data is owned by file BTInteriors_Project.esp due to ref BTInt_DRGN_Garden_07 (031BAAA9)

Same as above but this one is related to DLCCoast.esm all other info matches and again I didn't touch anything other then adding one misc. item.

 

I'm really just not sure if I should even worry about this I haven't seen any problems in game. It's just anoying to get the pop-up error every time I load the mod in the Ckit.

 

Thoughts?

[VIitS]

At a guess, it is comparing the cell record for your mod and Fallout4.esm, and seeing that the PreVis and other related data is different, not realizing that those DLC are the ones that first made the change (gg, Bethesda).

 

As long as Previs and precombined meshes aren't actually disabled in-game, I think you can ignore it. I don't think you can do anything about the messages though*, because Bethesda.

 

 

*unless you change the Cell data to match vanilla instead of the DLC, which might get rid of the message if my assumption as to why it is there is correct. Of course that might cause actual issues in game, depending on how the PreVis changed. If it was just adding new occlusions where new objects were placed, or it's identical and just has new previs because Bethesda is sloppy, then you'll be fine, but if any large objects were moved it'd be better not to.

 

Edit:

-Looking at the DLC, it looks like the only relevant change at 0000DF31 is a single placed object that had been part of a combined mesh (in a different cell that was in the same previs block), and was deleted in DLCNukaWorld.esm. That object is one of the supports for the road signs, so it shouldn't have ever had occlusions associated with it.

-For 00000FEC (this is in the diamond city worldspace, right?), I'm not seeing any actual changes to any of the cell records with the same previs data. In fact, the only non-VISI, non-PCMB change I'm seeing in the entire Diamond City worldspace is that they added an activator for the radio channel. 00000FEC itself seems to also have new precombined data, despite having identical references and combined meshes.

 

I have no idea what happens if the game tries to use different previs data for the one cell versus those around it (since previs is built in 3x3 blocks), but if it doesn't cause problems then there should be no issue if you wanted to tweak the cell data so you didn't have to see the error messages.

[chucksteel]

I did some experiments, copied Fallout4.esm's xpri and xcri data over to my .esp. Still got the error, I then did the same with the proper DLC's info and still got the error. I was originally matching the DLC's info.

 

At this point I think I'm getting the error because (as you said) it was comparing to the FO4.esm then once I changed xpri and xcri in my mod. i was still getting the error because then it was comparing to the DLC. :wallbash:

 

I was just worried it was a sign of something bigger but, it seems it's just due to sloppy work by Beth. I haven't seen any issues in game and the message was just annoying and worrying me a bit.

 

i think your right and there is nothing I can do about it.

 

Thanks for taking the time to help put my mind at ease.