Jump to content

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


sheson

Recommended Posts

52 minutes ago, Coldtrain3469 said:

I did I was following viva newvegas guide and it says the version here however, when I go here https://www.nexusmods.com/newvegas/mods/58562 it says FNVLODGen 3.2.1. So I am assuming to use this site's version and let it overwrite xEdit 4.0.4 scripts?

From the first post:
xLODGen beta 95 - based on 4.1.4b
Unzip into a dedicated folder outside of any Steam, game or mod manager folders or special Windows folders like Program Files.

You will notice it says nothing about unzipping or overwriting into any existing xEdit folders. When you open the archive, you will notice that the archive starts with its own xLODGen folder already.
There is no reason to invent steps or complicate anything. Simply unpack into its own folder and start it with -fnv -o:"c:\OutputPath\" command line arguments.

Link to comment
Share on other sites

Hi! I'm trying to use xLODGen for my first time. I'm using it on FNV. Every time I try to use it, I get to these lines:

[00:46] c:\program files (x86)\steam\steamapps\common\fallout new vegas\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-4.y0.dds
[00:46] c:\program files (x86)\steam\steamapps\common\fallout new vegas\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-16.y16.dds
[00:46] c:\program files (x86)\steam\steamapps\common\fallout new vegas\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-4.y0.dds
[00:46] c:\program files (x86)\steam\steamapps\common\fallout new vegas\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-20.y0.dds
[00:46] c:\program files (x86)\steam\steamapps\common\fallout new vegas\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-20.y0.dds
Operation aborted

I haven't touched my mouse or keyboard during the process, so I'm not manually aborting afaik. It just stops; no errors, nothing. Any help would be appreciated!!!

Link to comment
Share on other sites

1 hour ago, RandomProduct said:

Hi! I'm trying to use xLODGen for my first time. I'm using it on FNV. Every time I try to use it, I get to these lines:

[00:46] c:\program files (x86)\steam\steamapps\common\fallout new vegas\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-4.y0.dds
[00:46] c:\program files (x86)\steam\steamapps\common\fallout new vegas\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-16.y16.dds
[00:46] c:\program files (x86)\steam\steamapps\common\fallout new vegas\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-4.y0.dds
[00:46] c:\program files (x86)\steam\steamapps\common\fallout new vegas\textures\landscape\lod\wastelandnv\diffuse\wastelandnv.n.level4.x-20.y0.dds
[00:46] c:\program files (x86)\steam\steamapps\common\fallout new vegas\textures\landscape\lod\wastelandnv\normals\wastelandnv.n.level4.x-20.y0.dds
Operation aborted

I haven't touched my mouse or keyboard during the process, so I'm not manually aborting afaik. It just stops; no errors, nothing. Any help would be appreciated!!!

Upload the entire log to pastebin or a file service when making posts.

Do not install the game into special Windows folders like Program File x86 to avoid issues with Windows UAC, antivir, file permissions.

As explained on the first post:
Use -o:"c:\OutputPath\" command line parameter to change where files are generated to, default is the game folder. Then install output as a mod.
Do not generate into any game, any mod manager folders or special Windows folder like Program Files x86.

Link to comment
Share on other sites

Quick question - the last few times I've run xLodGen to generate Terrain LOD (just terrain, no object or tree), it's run out of space due to generating nearly 300gb of files in about 10 minutes. If this is just my setup (too many high poly meshes, too many mods with custom worldspaces, etc), that's fine then, I'll just free up more space, but I wanted to post my logs here just in case it's not actually supposed to be generating that much stuff (I could swear in the past it's never been even 100gb and I haven't changed my LO that much) and something is going wrong with the actual generation process (since there are errors in the Bugreport.txt that don't look like space related errors?).

I'm going to try with all the quality settings at lowest for now, see if that uses less space, but I figured I'd post my logs and bugreport here on the off chance that it's a bug and not just my setup having too many things in it.

 

SSELodGen log: https://mega.nz/file/Y1lSVDJZ#9OliNEWrDjbwBjnYzbVlOmCqgA42QJMkcTxvbkt_Vis

LodGen Log: https://mega.nz/file/Eg8ikJ6J#FcAwJft9nUBqJ8DyofAm4sSpDrBzp3kIwafhUx_0yI0

bugreport.txt

Edited by DarthVitrial
Link to comment
Share on other sites

1 hour ago, DarthVitrial said:

OK, followup - this time it just got to "Operation aborted" and it had 250GB free, so space doesn't seem to be the issue. Maybe another race condition?

Bugreport.txt attached.

 

Logs: https://mega.nz/file/glcgBRrK#8pKFL3gRI-cL--RVbHtTqvJi54ia3eazPCslvaT3wB0

bugreport.txt 433.21 kB · 1 download

Delete old logs and bugreport.txt. Use this test version https://mega.nz/file/9ZhUTZJb#ThODCL_AcOqwERvpHEDuv2_oE1N2NZslq7vZHQfSoho

If it happens again, double check plugins for errors. If plugins seem fine, upload new logs if it happens again.

  • Like 1
Link to comment
Share on other sites

59 minutes ago, DarthVitrial said:

No crash so far! Still running, been about an hour.

though it is a little surprising that the file size is already over 100GB on low quality settings.

Once its done check that the textures have the selected compression format.

Link to comment
Share on other sites

1 hour ago, DarthVitrial said:

It crashed again after about an hour. :/

Bug report attached.

Logs: https://mega.nz/file/k0lg1ZjT#3652CmIiichoTEKhdP00fVkqD9xihEATJchMyFn0tNk
 

For when it does work, how do I check texture compression format?

bugreport.txt 79.92 kB · 0 downloads

See what happens when you add the -speed command line argument.

https://github.com/Microsoft/DirectXTex/wiki/Texdiag

  • Like 1
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.