Forze_x

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.

On behalf of Sheshon I've tested it with a larger atlas size of 16384x16384. This works fine apparantly: https://photos.app.goo.gl/NNFACYEpECPVK2Tr9 Thanks for the help!

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!

Dear Double You (is a sexy MF), Thanks for looking into this! These links should work now for the logs. 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 I used the automatic settings of TexGen, indeed for 2160p resolution. https://photos.app.goo.gl/KG5XPQYpsMZPFKgw9 I lowered the settings to 1440p, now it works correct now. My apologies for not checking this out. " 2. Use the setting corresponding to rendered game resolution: 1080p = HD, 1440p = QHD, 2160p = 4k. It should be automatically detected." Just a recommendation: maybe it's interesting to recommend not going over the 1440p resolution for the TexGen textures. 4K is getting more common today and idiots like me think everything just works out of the box Once again, thank you very much for the help!

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.

Dyndolod Alpha 159 has the same issue. This is the oldest version available. I'll repeat my posts on the Dyndolod boards. @ Z929669: I can confirm it's a Dyndolod/TexGen issue. When I don't use TexGen everything works fine (except for the missing textures of course). I previously used Dyndolod Alpha 145 and it didn't have the problems. Unfortunately the DRM is blocking me from using it (downloaded it via the WaybackMachine).

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.

Dear STEP Team, First of all let me congratulate you on creating the single best Fallout 4 (and other games) Mod Guide available. I've been using your guides for years now and love how easy and simple you made the insanity of modding Bethesda games. Now, enough ass-kissing, onto the issues. 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. Thank you for taking these issues into consideration!