xLODGen - Terrain LOD beta 132 for FNV, FO3, FO4, FO4VR, TES5, SSE, TES5VR, ENDERAL, ENDERALSE

[sheson]

It is the area right outside vault 101 after FO3 starting events, when you escape the vault.

https://imgur.com/XCGfmzg

 

Just tried with the beta 58 and seems to work (through MO2, on a dedicated folder).

https://imgur.com/BJv038W

 

In this new test, reduced the diffuse/normal to half the the previous values (became 512/256 for LOD4 and 256/128 for the others).

Shouldn't be a memory issue, game was doing fine with most textures from this guide https://ttwoee.com/#textures, altough for this test I'm using base TTW, no textures on top (btw I was using the LOD section from the guide).

Did follow base instructions for TTW LOD gen https://taleoftwowastelands.com/viewtopic.php?t=7132, I'm also using FNVLODGen Resources from here https://www.nexusmods.com/newvegas/mods/58562, dunno if I should leave the FNVLODGen.esp ticked after generating LOD, but I'm leaving it ON.

 

 

I'll do more test until I'm fine with the results, may report back if I find what was causing the issue... or run into new troubles 

Thanks immensely for the help 

You peeps that mod and release stuff and do all the support are awesome!!

If beta 58 works as expected, use all the settings and use all the resources as before.

 

Though there is really no need for high resolutions for the default diffuse/normals at the outer parts of the maps that can never be reached and just use the default terrain texture without any features.

[Himself]

Heya, me again ^^

 

Dunno if this issue is related to xLODGen or the lack of a proper asset.

 

Same area from before, there is this Water Tower:

https://i.imgur.com/XuRbfXV.jpg

 

After generating LOD, a broken energy tower, introduced by a mod, becomes visible, its circulated in green.

The Water Tower however, disappears, it is only visible once I get nearby.

https://i.imgur.com/WVzhQew.jpg

 

For reference, the Water Tower was visible before LODGen (in the right side), but the broken energy tower was not.

https://i.imgur.com/R6ch0B8.jpg

 

Sorry for the crude images, it is base TTW with no enhanced textures/visuals.

I tried a few times under different setups (some with extra textures and LOD mods).

 

Does the Water Tower disappears because there should be some specific asset (mesh, texture, dunno) for correct LOD generation?

Is there a way to fix that?

 

If a specific asset is required, I could ask for and see if someone feels like doing it at Nexus and TTW forums.

Thanks for any help with this =)

[sheson]

 

Heya, me again ^^

 

Dunno if this issue is related to xLODGen or the lack of a proper asset.

 

Same area from before, there is this Water Tower:

https://i.imgur.com/XuRbfXV.jpg

 

After generating LOD, a broken energy tower, introduced by a mod, becomes visible, its circulated in green.

The Water Tower however, disappears, it is only visible once I get nearby.

https://i.imgur.com/WVzhQew.jpg

 

For reference, the Water Tower was visible before LODGen (in the right side), but the broken energy tower was not.

https://i.imgur.com/R6ch0B8.jpg

 

Sorry for the crude images, it is base TTW with no enhanced textures/visuals.

I tried a few times under different setups (some with extra textures and LOD mods).

 

Does the Water Tower disappears because there should be some specific asset (mesh, texture, dunno) for correct LOD generation?

Is there a way to fix that?

 

If a specific asset is required, I could ask for and see if someone feels like doing it at Nexus and TTW forums.

 

Thanks for any help with this =)

 

Check the log for error or warning messages.

 

Especially look out for "too many vertices/triangles, some LOD will be missing in game!" which means there are too many LOD models with too many triangles in that area. The only solution is to have less triangles in that area by further optimizing the LOD models or having less LOD models.

 

If that is not it, then a mod removed the object or there is no LOD model present for it in the current load order.

Edited November 30, 2019 by sheson

[Zanderat]

Latest version is throwing up this error:

 

 

[Zanderat]

Can't seem to edit my post.  This was with beta 58.  The previous version (beta 57) works fine.

[sheson]

Latest version is throwing up this error:

There obviously is a problem with a requirement for TexConv. Run it by itself on a command prompt, it might just tell you what exactly. Probably needs a recent or specific Redistributable similar to LODGen.exe

 

Things need to work or be fixed in the latest version going forward.

Edited November 30, 2019 by sheson

[Himself]

 

Check the log for error or warning messages.

 

In TTW basic, the lines that stand out look like something minor.

https://imgur.com/IgziQ3X

If using NMC textures, the final stage shows many - textures not on atlas, some LOD will be missing in game!

 

 

... or there is no LOD model present for it in the current load order.

 

 

Guess that is it, AFAIK - TTW LOD comes pre-generated and packed into .bsa

That was my fear, because there may be (many!) more of likewise cases, generating LOD for FO3 portion of TTW becomes a risky venture.

 

Not a xLODGen issue, but could you tell how does one find out these specific models? 

For example, how to find out which specific model is missing for xLODGen to include the Water Tower in the atlas?

(Hopefully, if given a practical example, I can follow up from there)

 

 

Btw, I'm assuming each atlas are those images generated inside the folder \blocks

looks like a comprised-miniature index for LOD visuals

NMC textures comes with this image and theres a Water Tower in there, but in-game the Water Tower looks wrong once it gets in the LOD, as does some other stuff too.

https://imgur.com/a/0OmBXbu

 

Again, many thanks if you can take the time!

Edited November 30, 2019 by Himself

[sheson]

 

 

 

In TTW basic, the lines that stand out look like something minor.

https://imgur.com/IgziQ3X

If using NMC textures, the final stage shows many - textures not on atlas, some LOD will be missing in game!

 

 

 

 

Guess that is it, AFAIK - TTW LOD comes pre-generated and packed into .bsa

That was my fear, because there may be (many!) more of likewise cases, generating LOD for FO3 portion of TTW becomes a risky venture.

 

Not a xLODGen issue, but could you tell how does one find out these specific models? 

For example, how to find out which specific model is missing for xLODGen to include the Water Tower in the atlas?

(Hopefully, if given a practical example, I can follow up from there)

 

 

Btw, I'm assuming each atlas are those images generated inside the folder \blocks

looks like a comprised-miniature index for LOD visuals

NMC textures comes with this image and theres a Water Tower in there, but in-game the Water Tower looks wrong once it gets in the LOD, as does some other stuff too.

https://imgur.com/a/0OmBXbu

 

Again, many thanks if you can take the time!

 

Instead of making screenshots of text, copy and paste the text to pastebin or upload the logile to a file service.

 

In FO3/FNV it is a simply file matching process. The LOD model for house.nif is house_lod.nif in the same folder.

 

Based on the wrong position error, it is possible that the LOD model is not read properly and missing because of that. This version of LODGen.exe should print a better message that also print the model filenames for easier troubleshooting. I might remember this wrong, but FO3/FNV object LOD typically has no vertex colors, but nevertheless LODGen should be able to read the nif.

 

The object LOD texture atlas is stitched together from the texture that are referenced in the LOD nif file - the single source texture.

LOD only has binary transparency and the default threshold is at 128. If transparency is messed up, then either something is off with the source texture or something happened to the LOD atlas texture. Best to use DXT1 with 1 bit transparency or DXT5 with alpha channel for source and atlas texture. 

Edited November 30, 2019 by sheson

[ahrneely]

This may be an inappropriate place to post this question and it may have already been answered somewhere else, but I'm struggling with xLODGen and haven't been able to find an answer anywhere else.

 

I'm following the most recent iteration of the TucoGuide over on Nexus (TucoGuide 3.4.3.0) and have pretty much followed everything in the guide to the letter. I have reached the portion where they guide us through the use of xLODGen and have run into an issue.

 

When I run SSELODGen, 90% of the functions return an error message. Those error messages look like this:

 

[04:46] <Warning: Error reading texture Textures\Landscape\ReachDirt01_N.dds>

[04:46] Error: Executing TexConv failure: "D:\Steam\steamapps\common\xLODGen\Edit Scripts\Texconvx64.exe" -nologo -y -f R32G32B32A32_FLOAT -o "C:\Users\[NAME]\AppData\Local\Temp\SSEEdit" "C:\Users\[NAME]\AppData\Local\Temp\SSEEdit\242B0E3ADB5D41F3B693026F6928C882.dds"

 

After two hours of runtime, SSELODGen finished and left me with about 10% of processes that didn't return these error messages. Does anyone have any idea of what could be causing the error messages or what I could do about them?

 

For what it's worth, <C:\> is my system drive and <D:\> is the drive where I keep SSE and MO2 and all mods.

 

Thanks in advance! :-D

[sheson]

This may be an inappropriate place to post this question and it may have already been answered somewhere else, but I'm struggling with xLODGen and haven't been able to find an answer anywhere else.

 

I'm following the most recent iteration of the TucoGuide over on Nexus (TucoGuide 3.4.3.0) and have pretty much followed everything in the guide to the letter. I have reached the portion where they guide us through the use of xLODGen and have run into an issue.

 

When I run SSELODGen, 90% of the functions return an error message. Those error messages look like this:

 

[04:46]

[04:46] Error: Executing TexConv failure: "D:\Steam\steamapps\common\xLODGen\Edit Scripts\Texconvx64.exe" -nologo -y -f R32G32B32A32_FLOAT -o "C:\Users\[NAME]\AppData\Local\Temp\SSEEdit" "C:\Users\[NAME]\AppData\Local\Temp\SSEEdit\242B0E3ADB5D41F3B693026F6928C882.dds"

 

After two hours of runtime, SSELODGen finished and left me with about 10% of processes that didn't return these error messages. Does anyone have any idea of what could be causing the error messages or what I could do about them?

 

For what it's worth, is my system drive and is the drive where I keep SSE and MO2 and all mods.

 

Thanks in advance! :-D

Yes it came up before, but then there are other users who post screenshots of log messages instead of the text so searching for something becomes a bit more tedious...

 

Look at the answer I gave yesterday 3 posts up: https://forum.step-project.com/topic/13451-xlodgen-terrain-lod-beta-for-fnv-fo3-fo4-fo4vr-tes5-sse-tes5vr-enderal/page-48?p=238090&do=findComment&comment=238090

 

Do not install tools into Steam, game, mod manger or special OS folders like Program Files x86. Install tools into their own dedicated folders. Use the -o command line to output files into dedicated folders outside of Steam, game or mod manger folders.

Edited December 1, 2019 by sheson

[ahrneely]

Yes it came up before, but then there are other users who post screenshots of log messages instead of the text so searching for something becomes a bit more tedious...

 

Look at the answer I gave yesterday 3 posts up: https://forum.step-project.com/topic/13451-xlodgen-terrain-lod-beta-for-fnv-fo3-fo4-fo4vr-tes5-sse-tes5vr-enderal/page-48?p=238090&do=findComment&comment=238090

 

Do not install tools into Steam, game, mod manger or special OS folders like Program Files x86. Install tools into their own dedicated folders. Use the -o command line to output files into dedicated folders outside of Steam, game or mod manger folders.

Interesting effects to note:

 

1.) I ran SSELODGen through a command prompt as suggested. This time, the error messages each had to do with a VCRUNTUIME dll file and the percentage of errors dropped to 2%.

 

2.) I also ran the x86 version of SSELODGen through MO2. This returned zero errors.

 

3.) Neither of the above methods attempted to call .dds files that are being called when running the x64 version of SSELODGen through MO2.

 

This leads me to believe I have something installed in MO2 that is telling xLODGen to look for .dds files that don't actually exist.

 

More investigation is necessary. I'll report back if I make any discoveries.

Edited December 1, 2019 by ahrneely

[sheson]

Interesting effects to note:

 

1.) I ran SSELODGen through a command prompt as suggested. This time, the error messages each had to do with a VCRUNTUIME dll file and the percentage of errors dropped to 2%.

 

2.) I also ran the x86 version of SSELODGen through MO2. This returned zero errors.

 

3.) Neither of the above methods attempted to call .dds files that are being called when running the x64 version of SSELODGen through MO2.

 

This leads me to believe I have something installed in MO2 that is telling xLODGen to look for .dds files that don't actually exist.

 

More investigation is necessary. I'll report back if I make any discoveries.

The suggestion is to run TexConv on the command prompt to see if there are messages about missing requirements.

 

If the x86 version works, it probably means the x86 version of the required Rredistributable is installed, but the x64 version is not.

 

Not sure how you would know what textures TexConv needs to convert if there is no error, since there is no message if it just works.

Edited December 1, 2019 by sheson

[ahrneely]

 

Not sure how you would know what textures TexConv needs to convert if there is no error, since there is no message if it just works.

I'm not quite sure I understand. Does this mean that if no error message appears the log wouldn't display the .dds file of the texture it's trying to convert? Therefore, my assumption that the x86 version "not calling a .dds" that the x64 version errors out on is invalid? (Which, by the way, is cool. As long as something is working, I guess I don't care how it works.)

[sheson]

I'm not quite sure I understand. Does this mean that if no error message appears the log wouldn't display the .dds file of the texture it's trying to convert? Therefore, my assumption that the x86 version "not calling a .dds" that the x64 version errors out on is invalid? (Which, by the way, is cool. As long as something is working, I guess I don't care how it works.)

When generating LOD, TexConv may convert 10000s of textures. When everything works as planed you won't see a single log line about TexConv doings its thing in the background.

 

If the error message would be about missing texture it would be obvious from the message and I would have suggested a troubleshooting step into that direction.

 

Run TexConv.exe/TexConvx64.exe from the command prompt to see if it tells you what might be wrong.

Edited December 1, 2019 by sheson

[Saqer]

12.7 GB just for terrain LOD (1k defuse and 512 normals BC7 both)... It's like installing another game!