You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using version control, if you take a Worldspace override and merge it up into an .esm, during the merge itll regenerate Offset Data and Large Ref data for the worldspace in the Destination .esm file.
If possible could you add a toggle in the .ini file to either:
Disable specifically Large Reference data generation
or
Condition it such that it only generates Large Reference data if there is none in the destination .esm for a given worldspace
The CK generates this data horribly wrong and outright fixing that would be significantly more complicated. There is an xEdit script that can generate the data properly. My use case is I want to setup the Target .ESM file with correct Large Ref data, and have the CK not touch it, such that when i merge in a worldspace override it only generates the Offset Data.
If you want to look into actually fixing the large ref data generation i can walk you through the details, but it's pretty complex. Outright disabling it, with a toggle, would be far simpler.
Its got its own .cpp under i believe bgslargerefdata.cpp
Edit: Oh this is just for Skyrim. Fallout 4 supports Large Ref data, but the game by default doesn't utilize this feature.
The text was updated successfully, but these errors were encountered:
I added a plugin system, if you are familiar with it, you can try to implement it. I'm going to take a break for now, I want to play and I need to work too. In general, I'll rest for a week.
Not high priority but would be a nice to have.
When using version control, if you take a Worldspace override and merge it up into an .esm, during the merge itll regenerate Offset Data and Large Ref data for the worldspace in the Destination .esm file.
If possible could you add a toggle in the .ini file to either:
or
The CK generates this data horribly wrong and outright fixing that would be significantly more complicated. There is an xEdit script that can generate the data properly. My use case is I want to setup the Target .ESM file with correct Large Ref data, and have the CK not touch it, such that when i merge in a worldspace override it only generates the Offset Data.
If you want to look into actually fixing the large ref data generation i can walk you through the details, but it's pretty complex. Outright disabling it, with a toggle, would be far simpler.
Its got its own .cpp under i believe bgslargerefdata.cpp
Edit: Oh this is just for Skyrim. Fallout 4 supports Large Ref data, but the game by default doesn't utilize this feature.
The text was updated successfully, but these errors were encountered: