0 of 0
File information
Created by
Ehamloptiran Sheson and FNVEdit TeamUploaded by
zilavVirus scan
Safe to use
videogame_asset My games
Install hundreds of mods with the click of a button.
Notifications
-
Give Feedback
1671 comments
FNVLODGen is not compatible with texture packs by default. Texture packs must include updated LOD textures to work properly with FNVLODGen to generate visually matching LODs. If authors are not around to create them, anyone good with Photoshop/GIMP of other editors can do that.
Check in NifScope what textures are used in _lod.nif meshes and update them to match new textures if needed. Keep in mind that normal maps must always have the same file name as diffuse with _n.dds suffix for FNVLODGen.
Trees LOD Billboards Vanilla v1.1 Update
- better looking bushes
Removes a lot of vanilla LOD limitations. Warnings about vertex or atlas overlflow can be ignored if installed.
Typically LOD textures should be 128 or 256, and 512 for very large objects like cliffs.
< WARNING: LOD level 4 coord [-8, -12] textures not on atlas, some LOD will be missing in game! >
for the rest of worldspaces LODs generate fine.
As a result of this: when I stand at Trading Post 188 and look where Helios One should be, I can only see solar panels, but not the tower or the building. This gets even weirder since I can see Novac's Dinosaur...
Help please!
Reading in general helps a lot.
EDIT- For those still needing help. I fixed the issue mostly by triple-checking all my mods for any that changed textures and checked they were all installed correctly if they were suppose to work with lodgen. For me, the issue was that NMC was leaving bullshit in the files even after I uninstalled it in my mod manager, if you look in the NMC mod page it has an uninstaller in the files tab to clean it out. Also double check you have no weather mods on.
And, if you didn't, download the trees file in the files tab on this mod and install that if you ticked the trees option, IDK why op doesnt just include it in the main mod and instead mentions it in a passing sentence, but I guess he has his reasons
on second hand - I have already finished the entire game with all DLCs and all possible endings, and LODs looked well in the Mojave world, so in from practical point of view the mod works.
But those texture errors still bug me like hell)))
The engine mod linked in the sticky post forces the game to render all shapes so no more missing LODs due to some textures not being on atlas (atlas overflow), I mention that explicitely "Warnings about vertex or atlas overlflow can be ignored if installed."
And yet people say that it's not helpful, rude and useless.
FYI - not all mod users are as sophisticated in programming as you are, if not most...
(Much needed LOD NMC patch is installed)
Whoops! I had Wasted LOD - Cliffs of Mojave installed,
not compatible with NMC
thanks xoxo
Do we just install the patch, or install the patch and run LODgen again?
Edit : The patch didn't work for me either way, still seeing the black LOD
So as it turns out, the issue is caused by meshes .nif files in the FNV supplementation mod,
that have being generated in nifscope with the Vertex Colour option turned on.
For the new version of xLODgen, the Vertex Colour option needs to be disabled.
"FNV LODGen Resources"
keyword of EPIC can point here)
Issue was : "Fatal: Could not find ini" while running fnvlodgen, and before it was something about registry
missing (program suggests starting the launcher for STEAM version).
Problem was the program didn't know where the DATA folder was, and where the
"Fallout.ini" was. You fix this by editing the arguments section in
modmanager2
Used this : (likely unneeded, but it helped me find out what file i actually needed to link, and I think this corrected
the .exe location that was missing) :
Fallout New Vegas Registry Fix 32_64 Bit
Helpful links:
Used this : https://vivanewvegas.moddinglinked.com/lod.html
this : https://dyndolod.info/Help/xLODGen
this : https://tes5edit.github.io/docs/2-overview.html#CommandLineSwitches
And then manually i typed this in modmanager2 > executables > xLODGen > Arguments
it already had the argument of :
(my stuff was installed on I: partition instead so change your locations accordingly)
-FNV -O:"I:\lods\lods"
and then I added 1 extra argument (since the above "Fallout New Vegas Registry Fix 32_64 Bit" likely fixed the game "DATA" location, the only missing was "Fallout.ini") ,for the location of "Fallout.ini"
-I:"C:\Users\User\Documents\My Games\FalloutNV_Epic\Fallout.ini"
So the full arguments line looked like this (again edit locations yourself) :
-FNV -O:"I:\lods\lods" -I:"C:\Users\User\Documents\My Games\FalloutNV_Epic\Fallout.ini"
Wouldnt be surprised if the "Fallout New Vegas Registry Fix 32_64 Bit" step wasskippable and you could add this for the .exe location :
-D:"I:\Games\FalloutNewVegas\Fallout New Vegas English\Data"
for a full argument line of this :
-FNV -O:"I:\lods\lods" -I:"C:\Users\User\Documents\My Games\FalloutNV_Epic\Fallout.ini" -D:"I:\Games\FalloutNewVegas\Fallout New Vegas English\Data"
I'm sure someone can make a clearer shorter more concise version :)
Anyway it all works, thanks Zilav and Team, (but maybe there could be a line of text in the description or something that said how to troubleshoot if the program can't find the locations, would've helped my dumb brain atleast :D )