FNVLODGen

Post by **Adonis VII** » Thu May 14, 2015 7:25 am

Yes, it appears in atlas map but the mesh still refers to the original texture instead of the map. My language is default US English.

Post by **zilav** » Thu May 14, 2015 8:22 am

There is another chance why mesh could be separate in LOD - very large tiled UV data (numbers in UVSets are very low or very high, like several dozens or hundreds when viewed in NifScope). Vanilla lod meshes don't have those, but maybe you have some mods that do that.

Download the latest FNVEdit, press Ctrl+F3, enter _lod.nif in filter to view all lod meshes, check the right column that lists where do they come from. All of them should be from vanilla and DLCs BSA archives by default. If anyone of nv_rocks lod meshes have Data mentioned there, then there is some mod that overrides them.

Post by **Adonis VII** » Thu May 14, 2015 12:21 pm

All the meshes are from the main fallout source. I tried with only the single texture installed and got:

Running FNVLODGen manually from game directory with ONLY New Vegas and textures\landscape\nv_rocks\nv_rockcanyonlod_d.dds installed produces correct LOD with 1 node

Running FNVLODGen through MO with ONLY New Vegas and textures\landscape\nv_rocks\nv_rockcanyonlod_d.dds (actual directory) installed produces incorrect LOD with 2 nodes.

Running FNVLODGen through MO with ONLY New Vegas and textures\landscape\nv_rocks\nv_rockcanyonlod_d.dds (through MO directory) installed produces incorrect LOD with 2 nodes.

The normal has no effect on the problem. So the issue is only with MO and this texture. It is 2048x1024 so its huge for a LOD file. Might that be the cause?

Post by **Adonis VII** » Thu May 14, 2015 12:49 pm

It's the size. I reduced the texture to 1024x512 and LOD now generates fine. As to why 2048 textures don't work with FNVLODGen and MO is beyond my knowledge, but really LOD's shouldn't be that large anyway.

Post by **zilav** » Thu May 14, 2015 2:35 pm

Ah now I see, I set the default max resolution of lod textures to 1024 in lodgen, everything higher will remain separate in generated lod. This works in Skyrim where several shapes are supported, but for fallouts ideally I should just show error and abort lod generation. Or just leave it as is, we know what is the source of problem (NMC) and can create a correct lod textures pack for it.

Normals maps are always scaled up to diffuse texture resolution, so their size doesn't matter. And seriously, 2048 lod texture size... what NMC's author was smoking?

Post by **RoyBatty** » Thu May 14, 2015 6:42 pm

He just made a mistake, it's feasible when he made thousands of textures all by himself. He made a few other mistakes and he fixes them when he's informed about them.

Like the red rocks having a normal for the diffuse texture... just made wrong filename and overwrote the correct texture. We are not perfect ;)

Post by **Adonis VII** » Thu May 14, 2015 11:29 pm

Either way atleast we figured out the issue so we know MO can work fine (without other user error). Now I can delete those 120ish LOD folders I've made...

Post by **zilav** » Fri May 15, 2015 7:53 am

Are there any other issues with NMC besides rock textures? There will be new rock lod models using separate new textures provided with FNVLODGen so those won't be a problem.

Post by **RoyBatty** » Fri May 15, 2015 8:14 am

Quite a few things aren't using NMC's textures, rocks in DC (his lod does), bridge, a few other things. I didn't check if his LOD works in NV. It may be that he edited the texatlas manually? I dunno.

Post by **zilav** » Fri May 15, 2015 5:11 pm

If worldspace atlas texture(s) is included in NMC pack, then yes, he edited it.