FEEDBACK v1.0 - Feedback & Bug Reports

[z929669]

7 minutes ago, Forze_x said:

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.

 

 

It sounds like his is an issue with FO4 LODGen using sheson's tools. Please post on the xLODGen topic for support, and let us know if the FO4 guide instructions conflict with any resolution you find.

[Forze_x]

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).

[DoubleYou]

2 hours ago, Forze_x said:

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).

I do not believe TexGen to be at fault. Your logs are protected on your drive. This is likely a variation of the bug depicted here:

What display resolution are you using? Perhaps you upgraded to a 4k monitor and TexGen is selecting a higher resolution LOD texture to generate, which is potentially inflating the size of the object lod atlas too full, so it is splitting and degrading the texture at runtime.

[Forze_x]

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!

[emiral]

What's the current view on editing the INI files? It looks like BethINI Pie makes changes to fallout.ini. But shouldn't we leave that file as it is, and do any overrides to it in falloutcuston.ini? Or is it that any modifications to entries in fallout.ini or falloutprefs.ini should be made in those files, and if an entry doesn't exist in those files, it goes in falloutcustom.ini?

[DoubleYou]

6 hours ago, Forze_x said:

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!

I hadn't tested going to that high of resolution, not for a long time at least. There are limitations in Fallout 4 as regards size of lod textures used that can cause issues if you get too many to fill the lod atlas, as you have found.

1 hour ago, emiral said:

What's the current view on editing the INI files? It looks like BethINI Pie makes changes to fallout.ini. But shouldn't we leave that file as it is, and do any overrides to it in falloutcuston.ini? Or is it that any modifications to entries in fallout.ini or falloutprefs.ini should be made in those files, and if an entry doesn't exist in those files, it goes in falloutcustom.ini?

I don't typically recommend using Fallout4Custom.ini vs main Fallout4.ini. Fallout4Custom.ini is not useful for anything in Fallout4Prefs.ini, as Fallout4Prefs.ini takes precedence. Using it only adds confusion with no benefit. 

[emiral]

Thanks, that's the direction I was looking for.

[Forze_x]

1 hour ago, DoubleYou said:

I hadn't tested going to that high of resolution, not for a long time at least. There are limitations in Fallout 4 as regards size of lod textures used that can cause issues if you get too many to fill the lod atlas, as you have found.

I don't typically recommend using Fallout4Custom.ini vs main Fallout4.ini. Fallout4Custom.ini is not useful for anything in Fallout4Prefs.ini, as Fallout4Prefs.ini takes precedence. Using it only adds confusion with no benefit. 

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!

[Tudemonster]

On 8/30/2023 at 1:37 PM, DoubleYou said:

In the game console, type the following and report the value:

getini "iFPSClamp:General"

I'm having the same issue. 

after checking console my output says 

iFPSClamp:General >> 0

[Tudemonster]

Is there any fix for the "too fast" problem?  I've followed the install correctly and even just after setting up the modding tools, before adding any mods, the game is going at double speed and I can't figure it out.

Tried both with and without the "fps clamp" with no change

4 minutes ago, Tudemonster said:

Is there any fix for the "too fast" problem?  I've followed the install correctly and even just after setting up the modding tools, before adding any mods, the game is going at double speed and I can't figure it out.

Tried both with and without the "fps clamp" with no change

thinking it has something to do with my 120hz refresh rate

 

[DoubleYou]

2 hours ago, Tudemonster said:

Is there any fix for the "too fast" problem?  I've followed the install correctly and even just after setting up the modding tools, before adding any mods, the game is going at double speed and I can't figure it out.

Tried both with and without the "fps clamp" with no change

thinking it has something to do with my 120hz refresh rate

 

The smoke test before installing mods is simply to check to ensure there isn't a CTD at this point. The issue you describe should be fixed later after installing the High FPS Physics Fix mod.

[deathtome1998]

so I am having an issue when I try to run the FOLIP patcher through synthesis. it says it can't find a part of the path, root:\steamlibrary\steamapps\common\fallout 4\data\meshes\lod. I know that the lod folder isn't there. however I don't know why it isn't there as I've tried to verify my game files, and launch the game from steam afterwards. neither of those gave me a fix. not sure what's going on there. if someone could lend some knowledge I'd appreciate it.

[DoubleYou]

21 hours ago, deathtome1998 said:

so I am having an issue when I try to run the FOLIP patcher through synthesis. it says it can't find a part of the path, root:\steamlibrary\steamapps\common\fallout 4\data\meshes\lod. I know that the lod folder isn't there. however I don't know why it isn't there as I've tried to verify my game files, and launch the game from steam afterwards. neither of those gave me a fix. not sure what's going on there. if someone could lend some knowledge I'd appreciate it.

Do you have FOLIP installed? Is Synthesis being run through Mod Organizer?

[deathtome1998]

2 hours ago, DoubleYou said:

Do you have FOLIP installed? Is Synthesis being run through Mod Organizer?

yes, and yes. but for some reason after reinstalling FOLIP which was the one thing I had yet to think of trying it worked now. so thanks for getting back to me with the questions you asked that made me reinstall it. although I'm also having an issue with texgen. it keeps giving me this error,

Textures\DLC03\lod\Landscape\Trees\RedPineHalf01_s.dds. 

and I'm not quite sure why. my landscape mod's BA2s LODs are extracted into a separate mod in MO2 so that they're loose files and will be read properly, but this seems to be an issue from something else. I have all the LOD fixes that I need such as weston water LOD fix for example. and like my last post said I have already verified my game files, so I don't think it's that either. do you or anyone else have an idea?

Edited March 29 by deathtome1998

[DoubleYou]

12 hours ago, deathtome1998 said:

yes, and yes. but for some reason after reinstalling FOLIP which was the one thing I had yet to think of trying it worked now. so thanks for getting back to me with the questions you asked that made me reinstall it. although I'm also having an issue with texgen. it keeps giving me this error,

Textures\DLC03\lod\Landscape\Trees\RedPineHalf01_s.dds. 

and I'm not quite sure why. my landscape mod's BA2s LODs are extracted into a separate mod in MO2 so that they're loose files and will be read properly, but this seems to be an issue from something else. I have all the LOD fixes that I need such as weston water LOD fix for example. and like my last post said I have already verified my game files, so I don't think it's that either. do you or anyone else have an idea?

Since reinstalling FOLIP fixed your first issue, my guess is your installation of Far Harbor 3d Tree LODs is similarly wrong, which would explain an error involving it.