Hello and thank you for reading ... this might be rather verbose ..<!>
I have about 6 different game 'profiles' created in MO2 ('Mod Organizer 2') utilizing many mods from a list of about 500 mods. I keep the same 'world spaces' for all of them (even 'Falskaar' because it is convenient). HOWEVER, each profile has a mixture different mods in them.
I noticed that the 'DynDOLOD ESP' is not 'good' for all the profiles since it records the mod contents of each profile therefore the .esp is not 'portable' between these profiles.
As a result, I have taken to running ALL DynDOLOD 'build processes' for each profile ...
1 run 'XLodGen' for terrain only and create mod in MO2 from output
2 run 'TexGen' and created mod in MO2 from output
3 run 'DynDOLOD' and create mod in MO2 from output
4 run 'XLodGen' for 'occlusion' only, and this magically appears in the MO2 mod list.
Each of the output mods above (4) are made specific for each profile and are uniquely named and installed in MO2. The pertinent output mods (all four) STAY ACTIVATED in the mod list of the profile while the others are 'disabled'
Q. Given the fact that I have the same 'World spaces' for ALL profiles, is it necessary to perform the entire 'DynDOLOD' creation process for each profile OR can I only run the primary 'DynDOLOD' for each process (keeping the 'xLodGen' and 'TexGen' files the same)?
After a perusal of the output files, I would think that I would only have to run 'DynDOLOD' for each profile ... using the first three output files ... but there may be some fine detail that I am missing that would prohibit this.
Thanks for Reading!
Edited by bchick1, 29 March 2020 - 02:48 PM.