FO4LODGen

[bbypaarthurnax]

7 hours ago, sheson said:

That is indeed confusing. "No vertex colors" should be checked. The object LOD meshes should not have any vertex colors.

This was indeed the issue!  Thanks so much for the help sheson!

[Forze_x]

Dear Dyndolod developers, 

Following the Fallout 4 Step 4.10 instructions I've run into issues with TexGen64 version Alpha 159-161-167. I have followed every Step step meticulously multiple times and even had significant hardware upgrade (CPU/Motherboard/etc.), tried Windows 10 and 11 (including multiple formats and thorough cleanups up, including the registry).

I have found that up until the Alpha 145 build, everything worked fine in generating the Textures and creating LOD's, but starting from Alpha 159 to current Alpha 167 there are issues with blurry/unfinished textures and terrain issues with the Glowin Sea LOD's after generating the LOD's (either with or without using CAO).

Pictures of the issues: https://photos.app.goo.gl/sfcbw2wVps9oQvAy9

After testing I've found not using TexGen64 to generate Textures causes everything to work fine (except for the missing TexGen64 Textures of course, i.e. purple textures, see pictures here): https://photos.app.goo.gl/jKXJkZSgJKHAppP77

Disabling the generated xLODGen Object folder in MO2 also works fine.

I didn't get any errors in either TexGen64 or xLODGen:

FO4LODGen Log: https://drive.google.com/file/d/1gdPYCFF23keCHChHi8QuhPvZAYFqoEEK/view?usp=drive_link

LODGen log: https://drive.google.com/file/d/1lUpYY61T9XK35ZBCuk6u8HYxWY_KU-lq/view?usp=drive_link

TexGen debug log: https://drive.google.com/file/d/1oNIlIAQT3ztgBJ-_W3gm7RcJIRnsGj8z/view?usp=drive_link

TexGen FO4 log: https://drive.google.com/file/d/1iKljVx17MxSY-1shNT-fbWDJ9r-TXHiR/view?usp=drive_link

If I can help you in testing, please let me know.

Thank you for your time and help!

 

Full story from post(s) on the STEP FO4 board:

Since mid january I've run into problems on xLODGen Object generation using your guide. I'll explain the issues step by step.

-I've used the guide last november (Windows 11, Core I9-9900KF, 32GB Ram, RTX 3080, Samsung 980 1Tb) to create a regular buid, customizing it later => xLODGen worked fine, everything ran normal, even with a large number of world altering mods.

- Mid january I decided on a new build, more Vanilla, starting over from scratch with newer versions of all the tools => xLODGEN gave the following results https://photos.app.goo.gl/sfcbw2wVps9oQvAy9 I tried going back to older versions of xLODGen, xEdit and LodGen Resources, but nothing worked.

- The end of january, I upgraded my rig (Ryzen 7 7800X3D, 32GB Ram, RTX 3080, Samsung 990 Pro 1Tb), performing a full reinstall (with Windows 10). I started a completely new build following the STEP guide to the letter => same result.

- I decided to upgrade to Windows 11, performing another full reinstall of everything, including the full STEP guide => same result

- I removed everything, starting from scratch once more, but the issue remains.

My findings when troubleshooting:

- the issues remain when not using CAO.

- I've tried using different xLODGen settings, but the result remains the same. I receive no errors during or after generating Lods.

latest xLODGen logs: 

https://drive.google.com/file/d/1gdPYCFF23keCHChHi8QuhPvZAYFqoEEK/view?usp=drive_link

https://drive.google.com/file/d/1lUpYY61T9XK35ZBCuk6u8HYxWY_KU-lq/view?usp=drive_link 

- disabling the xLODGen Output mods restores regular LOD fine

- the terrain LOD generation works fine ( the usual Cloud z-fighting when moving fast during a TCL flyththrough). So the issues are specifically with Object generation. The terrain itself gets issues when the Object LOD is used.

- I've tried previous versions of xLODGen (back to the beginning of 2023) => same issue

- I've tried using Luxor8071 LOD's on top of the other => same issue

- I'm going to try and use different Texture overhaul mods to see if the issue remains, but I would like to let you guys know what I've found already.

Update:

- Same issue when using other Texture Packs: SavrenX - Vivid 

- Same issue when not using:

--High Resolution Texture Pack

--Jesters Better Destroyed Vehicles

--Langleys HD Textures Workshop

--FlaconOils Complete Retexture Project

-Same issue when using FO4LODgen - Guide settings https://www.nexusmods.com/fallout4/mods/49362

 

Update 2:

I found the problem:

The new Dyndolod/TexGen is the perpetrator:

Lodgen after not using TexGen:

https://photos.app.goo.gl/geNgNF1Y2CPEUuqo7

Of ourse it's missing textures now, causing the purple coloring.

I'm going to look for an older Dyndolod/TexGen for testing.

Tested the available version: Alpha 159 and 161, both have the issue

The old 145 is locked unfortunately.

 

 

 

 

[z929669]

2 hours ago, Forze_x said:

Dear Dyndolod developers, 

Following the Fallout 4 Step 4.10 instructions I've run into issues with TexGen64 version Alpha 159-161-167. I have followed every Step step meticulously multiple times and even had significant hardware upgrade (CPU/Motherboard/etc.), tried Windows 10 and 11 (including multiple formats and thorough cleanups up, including the registry).

I have found that up until the Alpha 145 build, everything worked fine in generating the Textures and creating LOD's, but starting from Alpha 159 to current Alpha 167 there are issues with blurry/unfinished textures and terrain issues with the Glowin Sea LOD's after generating the LOD's (either with or without using CAO).

Pictures of the issues: https://photos.app.goo.gl/sfcbw2wVps9oQvAy9

After testing I've found not using TexGen64 to generate Textures causes everything to work fine (except for the missing TexGen64 Textures of course, i.e. purple textures, see pictures here): https://photos.app.goo.gl/jKXJkZSgJKHAppP77

Disabling the generated xLODGen Object folder in MO2 also works fine.

I didn't get any errors in either TexGen64 or xLODGen:

FO4LODGen Log: https://drive.google.com/file/d/1gdPYCFF23keCHChHi8QuhPvZAYFqoEEK/view?usp=drive_link

LODGen log: https://drive.google.com/file/d/1lUpYY61T9XK35ZBCuk6u8HYxWY_KU-lq/view?usp=drive_link

TexGen debug log: https://drive.google.com/file/d/1oNIlIAQT3ztgBJ-_W3gm7RcJIRnsGj8z/view?usp=drive_link

TexGen FO4 log: https://drive.google.com/file/d/1iKljVx17MxSY-1shNT-fbWDJ9r-TXHiR/view?usp=drive_link

If I can help you in testing, please let me know.

Thank you for your time and help!

 

Full story from post(s) on the STEP FO4 board:

Since mid january I've run into problems on xLODGen Object generation using your guide. I'll explain the issues step by step.

-I've used the guide last november (Windows 11, Core I9-9900KF, 32GB Ram, RTX 3080, Samsung 980 1Tb) to create a regular buid, customizing it later => xLODGen worked fine, everything ran normal, even with a large number of world altering mods.

- Mid january I decided on a new build, more Vanilla, starting over from scratch with newer versions of all the tools => xLODGEN gave the following results https://photos.app.goo.gl/sfcbw2wVps9oQvAy9 I tried going back to older versions of xLODGen, xEdit and LodGen Resources, but nothing worked.

- The end of january, I upgraded my rig (Ryzen 7 7800X3D, 32GB Ram, RTX 3080, Samsung 990 Pro 1Tb), performing a full reinstall (with Windows 10). I started a completely new build following the STEP guide to the letter => same result.

- I decided to upgrade to Windows 11, performing another full reinstall of everything, including the full STEP guide => same result

- I removed everything, starting from scratch once more, but the issue remains.

My findings when troubleshooting:

- the issues remain when not using CAO.

- I've tried using different xLODGen settings, but the result remains the same. I receive no errors during or after generating Lods.

latest xLODGen logs: 

https://drive.google.com/file/d/1gdPYCFF23keCHChHi8QuhPvZAYFqoEEK/view?usp=drive_link

https://drive.google.com/file/d/1lUpYY61T9XK35ZBCuk6u8HYxWY_KU-lq/view?usp=drive_link 

- disabling the xLODGen Output mods restores regular LOD fine

- the terrain LOD generation works fine ( the usual Cloud z-fighting when moving fast during a TCL flyththrough). So the issues are specifically with Object generation. The terrain itself gets issues when the Object LOD is used.

- I've tried previous versions of xLODGen (back to the beginning of 2023) => same issue

- I've tried using Luxor8071 LOD's on top of the other => same issue

- I'm going to try and use different Texture overhaul mods to see if the issue remains, but I would like to let you guys know what I've found already.

Update:

- Same issue when using other Texture Packs: SavrenX - Vivid 

- Same issue when not using:

--High Resolution Texture Pack

--Jesters Better Destroyed Vehicles

--Langleys HD Textures Workshop

--FlaconOils Complete Retexture Project

-Same issue when using FO4LODgen - Guide settings https://www.nexusmods.com/fallout4/mods/49362

 

Update 2:

I found the problem:

The new Dyndolod/TexGen is the perpetrator:

Lodgen after not using TexGen:

https://photos.app.goo.gl/geNgNF1Y2CPEUuqo7

Of ourse it's missing textures now, causing the purple coloring.

I'm going to look for an older Dyndolod/TexGen for testing.

Tested the available version: Alpha 159 and 161, both have the issue

The old 145 is locked unfortunately.

This may not be relevant to TexGen and better suited for the xLODGen topic. See DoubleYou's response.

[sheson]

10 hours ago, Forze_x said:

Dear Dyndolod developers, 

Following the Fallout 4 Step 4.10 instructions I've run into issues with TexGen64 version Alpha 159-161-167. I have followed every Step step meticulously multiple times and even had significant hardware upgrade (CPU/Motherboard/etc.), tried Windows 10 and 11 (including multiple formats and thorough cleanups up, including the registry).

I have found that up until the Alpha 145 build, everything worked fine in generating the Textures and creating LOD's, but starting from Alpha 159 to current Alpha 167 there are issues with blurry/unfinished textures and terrain issues with the Glowin Sea LOD's after generating the LOD's (either with or without using CAO).

Pictures of the issues: https://photos.app.goo.gl/sfcbw2wVps9oQvAy9

After testing I've found not using TexGen64 to generate Textures causes everything to work fine (except for the missing TexGen64 Textures of course, i.e. purple textures, see pictures here): https://photos.app.goo.gl/jKXJkZSgJKHAppP77

Disabling the generated xLODGen Object folder in MO2 also works fine.

I didn't get any errors in either TexGen64 or xLODGen:

FO4LODGen Log: https://drive.google.com/file/d/1gdPYCFF23keCHChHi8QuhPvZAYFqoEEK/view?usp=drive_link

LODGen log: https://drive.google.com/file/d/1lUpYY61T9XK35ZBCuk6u8HYxWY_KU-lq/view?usp=drive_link

TexGen debug log: https://drive.google.com/file/d/1oNIlIAQT3ztgBJ-_W3gm7RcJIRnsGj8z/view?usp=drive_link

TexGen FO4 log: https://drive.google.com/file/d/1iKljVx17MxSY-1shNT-fbWDJ9r-TXHiR/view?usp=drive_link

If I can help you in testing, please let me know.

Thank you for your time and help!

 

Full story from post(s) on the STEP FO4 board:

Since mid january I've run into problems on xLODGen Object generation using your guide. I'll explain the issues step by step.

-I've used the guide last november (Windows 11, Core I9-9900KF, 32GB Ram, RTX 3080, Samsung 980 1Tb) to create a regular buid, customizing it later => xLODGen worked fine, everything ran normal, even with a large number of world altering mods.

- Mid january I decided on a new build, more Vanilla, starting over from scratch with newer versions of all the tools => xLODGEN gave the following results https://photos.app.goo.gl/sfcbw2wVps9oQvAy9 I tried going back to older versions of xLODGen, xEdit and LodGen Resources, but nothing worked.

- The end of january, I upgraded my rig (Ryzen 7 7800X3D, 32GB Ram, RTX 3080, Samsung 990 Pro 1Tb), performing a full reinstall (with Windows 10). I started a completely new build following the STEP guide to the letter => same result.

- I decided to upgrade to Windows 11, performing another full reinstall of everything, including the full STEP guide => same result

- I removed everything, starting from scratch once more, but the issue remains.

My findings when troubleshooting:

- the issues remain when not using CAO.

- I've tried using different xLODGen settings, but the result remains the same. I receive no errors during or after generating Lods.

latest xLODGen logs: 

https://drive.google.com/file/d/1gdPYCFF23keCHChHi8QuhPvZAYFqoEEK/view?usp=drive_link

https://drive.google.com/file/d/1lUpYY61T9XK35ZBCuk6u8HYxWY_KU-lq/view?usp=drive_link 

- disabling the xLODGen Output mods restores regular LOD fine

- the terrain LOD generation works fine ( the usual Cloud z-fighting when moving fast during a TCL flyththrough). So the issues are specifically with Object generation. The terrain itself gets issues when the Object LOD is used.

- I've tried previous versions of xLODGen (back to the beginning of 2023) => same issue

- I've tried using Luxor8071 LOD's on top of the other => same issue

- I'm going to try and use different Texture overhaul mods to see if the issue remains, but I would like to let you guys know what I've found already.

Update:

- Same issue when using other Texture Packs: SavrenX - Vivid 

- Same issue when not using:

--High Resolution Texture Pack

--Jesters Better Destroyed Vehicles

--Langleys HD Textures Workshop

--FlaconOils Complete Retexture Project

-Same issue when using FO4LODgen - Guide settings https://www.nexusmods.com/fallout4/mods/49362

 

Update 2:

I found the problem:

The new Dyndolod/TexGen is the perpetrator:

Lodgen after not using TexGen:

https://photos.app.goo.gl/geNgNF1Y2CPEUuqo7

Of ourse it's missing textures now, causing the purple coloring.

I'm going to look for an older Dyndolod/TexGen for testing.

Tested the available version: Alpha 159 and 161, both have the issue

The old 145 is locked unfortunately.

If you have issues with a guide, you need to ask question about it on the appropriate forum/section for the guide.

The google drive links ask for a login.

From the screenshot I am deducting you seem to have a problem with the LOD for power pylons.

Configurations for TexGen included in DynDOLOD 3 Alpha does not affect the LOD textures for the electrical towers. They are rendered LOD texture.
Textures\LOD\ElectricalTowerLOD_d.DDS
Textures\LOD\ElectricalTowerSmallLOD_d.DDS
TexGen does not affect terrain LOD meshes or textures.

The issue with low res textures shown in game might have to do with the used textures not being in a BA2. The game used to have issues with proper mipmap usage in that, though I am out of the loop if that is still the case.

[Forze_x]

6 hours ago, sheson said:

If you have issues with a guide, you need to ask question about it on the appropriate forum/section for the guide.

The google drive links ask for a login.

From the screenshot I am deducting you seem to have a problem with the LOD for power pylons.

Configurations for TexGen included in DynDOLOD 3 Alpha does not affect the LOD textures for the electrical towers. They are rendered LOD texture.
Textures\LOD\ElectricalTowerLOD_d.DDS
Textures\LOD\ElectricalTowerSmallLOD_d.DDS
TexGen does not affect terrain LOD meshes or textures.

The issue with low res textures shown in game might have to do with the used textures not being in a BA2. The game used to have issues with proper mipmap usage in that, though I am out of the loop if that is still the case.

Dear Sheshon,

I had posted it in the STEP board, but was a little to fast to repost it here, my apologies.

Thanks to Double You I found the issue: TexGen automatically used 2160p, which caused my Atlas size (8192x8192) to fill up. Since I'm a dumb idiot I didn't change the settings to 1440p to check if these worked.

I changed the links to the Google Drive so they're accessible.

https://drive.google.com/file/d/1gdPYCFF23keCHChHi8QuhPvZAYFqoEEK/view?usp=sharing

https://drive.google.com/file/d/1iKljVx17MxSY-1shNT-fbWDJ9r-TXHiR/view?usp=sharing

https://drive.google.com/file/d/1lUpYY61T9XK35ZBCuk6u8HYxWY_KU-lq/view?usp=sharing

https://drive.google.com/file/d/1oNIlIAQT3ztgBJ-_W3gm7RcJIRnsGj8z/view?usp=sharing

 

Once again, my apologies for being a hasty idiot and thank you for delivering a great set of tools!

[sheson]

23 minutes ago, Forze_x said:

Dear Sheshon,

I had posted it in the STEP board, but was a little to fast to repost it here, my apologies.

Thanks to Double You I found the issue: TexGen automatically used 2160p, which caused my Atlas size (8192x8192) to fill up. Since I'm a dumb idiot I didn't change the settings to 1440p to check if these worked.

I changed the links to the Google Drive so they're accessible.

https://drive.google.com/file/d/1gdPYCFF23keCHChHi8QuhPvZAYFqoEEK/view?usp=sharing

https://drive.google.com/file/d/1iKljVx17MxSY-1shNT-fbWDJ9r-TXHiR/view?usp=sharing

https://drive.google.com/file/d/1lUpYY61T9XK35ZBCuk6u8HYxWY_KU-lq/view?usp=sharing

https://drive.google.com/file/d/1oNIlIAQT3ztgBJ-_W3gm7RcJIRnsGj8z/view?usp=sharing

 

Once again, my apologies for being a hasty idiot and thank you for delivering a great set of tools!

In that case I would suggest to also test to increase the atlas size to 16384 so xLODGen doesn't need to create a second atlas texture.

[Forze_x]

6 hours ago, sheson said:

In that case I would suggest to also test to increase the atlas size to 16384 so xLODGen doesn't need to create a second atlas texture.

I've tried it and can confirm this solution works perfectly: https://photos.app.goo.gl/NNFACYEpECPVK2Tr9

Many thanks for the help! 

I informed DoubleYou as well, it might be interesting to add this information to the Step guide.

[Throwinkicks]

I’m noticing a bug where there is no lod for the houses in sanctuary hills. I toggled clipping and ran around the entire map and as far as I can tell all the lod is pretty much perfect except sanctuary specifically. If I don’t install the lodgen output the vanilla houses are there (despite obviously missing the generated lod) but with it installed the houses disappear. I can’t figure out what is causing this. 

[DoubleYou]

3 minutes ago, Throwinkicks said:

I’m noticing a bug where there is no lod for the houses in sanctuary hills. I toggled clipping and ran around the entire map and as far as I can tell all the lod is pretty much perfect except sanctuary specifically. If I don’t install the lodgen output the vanilla houses are there (despite obviously missing the generated lod) but with it installed the houses disappear. I can’t figure out what is causing this. 

I take it you use Rebuild Sanctuary?

[Throwinkicks]

Yes I believe so. I’m using a storywealth mod collection and I added lodgen on top of it. I’d there a way to fix this? 

I have (a storywealth rebuild patch) (Rebuild AIO part 01) (rebuild me home sanctuary roads) (rebuild shared resources)

[DoubleYou]

8 minutes ago, Throwinkicks said:

Yes I believe so. I’m using a storywealth mod collection and I added lodgen on top of it. I’d there a way to fix this? 

I have (a storywealth rebuild patch) (Rebuild AIO part 01) (rebuild me home sanctuary roads) (rebuild shared resources)

Check the Res01Modern01RR and related records to ensure the HasDistantLOD flag is there and the Distant LOD meshes are assigned and patch as necessary.

[Throwinkicks]

Okay thanks 🙏🏻 

[Throwinkicks]

On 3/7/2024 at 3:30 PM, DoubleYou said:

Check the Res01Modern01RR and related records to ensure the HasDistantLOD flag is there and the Distant LOD meshes are assigned and patch as necessary.

how do i do this exactly? i understand its using xedit. but im unfamiliar

[sheson]

3 hours ago, Throwinkicks said:

how do i do this exactly? i understand its using xedit. but im unfamiliar

If you have questions how to use xEdit check is manual, watch videos about it and ask on its forum or discord.

You load the plugin in xEdit, bring up the desired base record via the left tree view or by entering its form ID in the top left field and hit enter. You can edit entries in plugins other than Fallout4.esm by double or right clicking them and selecting edit. You can drag and drop entries from one plugin to another. 

Base records and their LOD model assignments can also be edited in Creation Kit.