66 replies to this topic

[sheson]

hey ShesonI am having an issue generating Occlusion Generation xLODGEN it spewing out a load of errors:

 

I will add i have just built a new PC so there might be something I forgot to set up

Use the x64 version so it can use more memory.

 

If this happens with the x64 version, make sure Windows page file settings are default.

[DarkladyLexy]

I am using the x64 version and i haven't touch page filing

 

if it help i have i5 10600K runnind at stock and 32GB 3600MHz Ram

 

Edit: Scrap that I am not using the x64 verison i will try again.

[sheson]

I am using the x64 version and i haven't touch page filing

 

if it help i have i5 10600K runnind at stock and 32GB 3600MHz Ram

Track its memory usage. Try to close some (hidden) processes/programs.

 

If object LOD meshes are huge because of ultra tree LOD DynDOLOD settings, see if it works by temporarily disabling them so it uses vanilla LOD.

 

Open a couple of the mentioned *.BTO files in NifSkope to make sure they load and are not somehow corrupted.

Edited by sheson, 05 September 2020 - 04:17 AM.

[DarkladyLexy]

all sorted is cos I am idiot and not using the x64 version my bad.

[sheson]

all sorted is cos I am idiot and not using the x64 version my bad.

Ah good. No worries.

[HunterZ]

Sorry if this has already been asked, but if there is a future update, can this be fixed to respect the output directory command line parameter instead of writing occlusion.esp to the game directory? This seems to be the only tool in the xLODGen/DynDOLOD suite that doesn't support this mode of operation.

[sheson]

xLODGen is just a renamed xEdit. xEdit always saves plugins to the games data path and if required creates backups.

 

Why would Occlusion generation need to be the only tool mode that saves new or updated plugins to a different path, than any of the other xEdit modes/functions?