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

[VComrade]

Hello, every time I generate new occlusion data, and press X when the generation is complete I get the following warning messages:

Is this supposed to happen?

Also, is it necessary to regenerate object and trees LoD with DyndoLoD after regenerating terrain LoD with XLoDGen?

 

Thanks in advance

Edited January 4, 2021 by VComrade

[sheson]

Hello, every time I generate new occlusion data, and press X when the generation is complete I get the following warning messages:

 

Is this supposed to happen?

 

Also, is it necessary to regenerate object and trees LoD with DyndoLoD after regenerating terrain LoD with XLoDGen?

 

Thanks in advance

https://forum.step-project.com/topic/15375-xlodgen-rename-delete-error/

[VComrade]

https://forum.step-project.com/topic/15375-xlodgen-rename-delete-error/

Oh okay thanks, so it should not mess up anything? 

[VComrade]

https://forum.step-project.com/topic/15375-xlodgen-rename-delete-error/

Can you answer my second question?

 

"Also, is it necessary to regenerate object and trees LoD with DyndoLoD after regenerating terrain LoD with XLoDGen?"

[sheson]

Oh okay thanks, so it should not mess up anything? 

Discard everything that is not Occlusion.

 

Each LOD type works independent of each other. If there were a requirement to do anything it would be part of the instructions in the manual. Also see the chapter "Updating" in the DynDOLOD manual.

[VComrade]

Discard everything that is not Occlusion.

 

Each LOD type works independent of each other. If there were a requirement to do anything it would be part of the instructions in the manual. Also see the chapter "Updating" in the DynDOLOD manual.

How do I discard it? I can only press "ok".

Edited January 4, 2021 by VComrade

[sheson]

How do I discard it? I can only press "ok".

That means to delete any other files than Occlusion.esp

[VComrade]

That means to delete any other files than Occlusion.esp

Oh now I get it, theres bunch of files left over after all those lod generations. Thanks!

[Stefan]

If you find the time, do the same with the latest version again and have an eye at what part (check the message log) it starts waiting. Then check if there are LODGen or TexConv processes running in the background.

Doing it now, sorry for the delay. I am using the latest beta, 66, as a note, it still says beta 64 in the bar: https://prnt.sc/wixcxo

Will let you know how it goes.

[Stefan]

Dead, within 10 minutes. Runtime error, no generating process running, secondary or primary.

 

https://prnt.sc/wixsxb

 

Beta 64 works fine. I use the settings from Step SSE guide, here, if you forget: https://prnt.sc/wixu82

 

EDIT: Looking for that error, it seems it's trojan related? Probably it doesn't apply here. I run Nod32 Internet Security. Beta 64 works fine, and I have never got the Runtime error on anything else.

 

EDIT2: I am doing a  NOD32 scan and F-secure one as we speak, but it can't be a trojan. I restore Windows from a clean ghost kept on an external HDD I keep in a box, I don't visit random websites, I don't install random software, etc.

 

EDIT3: F-secure scanning done, it says my PC is clean. Eset will say the same probably.

Edited January 8, 2021 by Stefan

[sheson]

it still says beta 64 in the bar: https://prnt.sc/wixcxo

 

It says x64, always has.

[sheson]

Dead, within 10 minutes. Runtime error, no generating process running, secondary or primary.

 

https://prnt.sc/wixsxb

 

Beta 64 works fine. I use the settings from Step SSE guide, here, if you forget: https://prnt.sc/wixu82

 

EDIT: Looking for that error, it seems it's trojan related? Probably it doesn't apply here. I run Nod32 Internet Security. Beta 64 works fine, and I have never got the Runtime error on anything else.

 

EDIT2: I am doing a  NOD32 scan and F-secure one as we speak, but it can't be a trojan. I restore Windows from a clean ghost kept on an external HDD I keep in a box, I don't visit random websites, I don't install random software, etc.

 

EDIT3: F-secure scanning done, it says my PC is clean. Eset will say the same probably.

Post or pastebin the log

[Stefan]

It says x64, always has.

Lol, I missed an X, little moron that I am. 

 

Post or pastebin the log

I started it again, on beta 66, the second try worked flawlessly, here is the full log. Eset said the PC is clean too. WHich isn't necessarily true.

https://www.dropbox.com/s/06d49enrha4ng85/xlodgen%20v66.zip?dl=0

Edited January 8, 2021 by Stefan

[sheson]

Lol, I missed an X, little moron that I am. 

 

I started it again, on beta 66, the second try worked flawlessly, here is the full log. Eset said the PC is clean too. WHich isn't necessarily true.

https://www.dropbox.com/s/06d49enrha4ng85/xlodgen%20v66.zip?dl=0

The error was probably caused by a race condition I fixed in beta 67

Edited January 8, 2021 by sheson

[Stefan]

The error was probably caused by a race condition I fixed in beta 67

You are the man. Cheers.