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

[sheson]

Does beta 65 automatically closes itself, or it crashed? This is the end of my log:

Finished LOD level RigmorRoscrea.4.52.60.btr [64/32]
Finished LOD level RigmorRoscrea.4.56.60.btr [64/32]
Finished LOD level RigmorRoscrea.4.60.60.btr [64/32]
Finished LOD level RigmorRoscrea.4.4.56.btr [8012/32]
Finished LOD level RigmorRoscrea.4.8.52.btr [16946/32]
Log ended at 3:46:07 AM (0:39)
Code: 0

Thank you.

Nothing changed. You pasted the last few lines from the LODGen.exe log. LODgen.exe always ends like this since years.

Also, how do I do a clean install? I have downloaded the 65 beta, removed everything inside the 64 folder, than unziped 65 in the same folder, but when I launch xLodgen through MO2, the 64 custom templates are still in the Terrain LOD4 LOD8, etc. 

 

Thank you.

What are "custom templates" supposed to be? There is such thing in xLODGen terrain LOD beta.

[Stefan]

Nothing changed. You pasted the last few lines from the LODGen.exe log. LODgen.exe always ends like this since years.

So it didn't crash. For some reason in my first 5 or 6 terrain generation, xLodgen never closed by itself so I had to close it manually. So that's why when this time it did, I thought it crashed.

 

 

 

What are "custom templates" supposed to be? There is such thing in xLODGen terrain LOD beta.

The custom templates from the Step tutorial here https://wiki.step-project.com/SkyrimSE:0.3.0b#xLODGen, those 4 images from "Terrain LOD generation". When I first installed beta 64, the data was different, and I had to change it to the Step guide. When I installed beta 65, all 4 were present.

Cheers

Edited January 3, 2021 by Stefan

[Stefan]

And this was the full log:

https://www.dropbox.com/s/w0b6hwdjvklknby/lodgen_log.txt?dl=0

https://www.dropbox.com/s/6epqvpmtxb0u2pu/sselodgen_log.txt?dl=0

[07:35] Error creating textures for level 4 quad [12,-40] Operation aborted
[07:35] Error creating textures for level 16 quad [0,-48] One or more errors occurred

I repeat, the reason why I ask is because the first 5 or 6 times when I generated terrain last week with SSELODgen, when it was done I had to close it manually. But the last 2 times, for some reason after RigmorRoscrea world both times it closed automatically, when I came to the PC only MO2 was running. 

So I thought it crashed or something.

 

The second log shows an error at the end?

 

Thank you.

 

PS: Could it be because I have ticked Grass Cache, the grass generated with No grass in objects? That's the only difference between these 2 runs, and the other 5-6 runs.

https://prnt.sc/wf7qfl

Edited January 3, 2021 by Stefan

[sheson]

So it didn't crash. For some reason in my first 5 or 6 terrain generation, xLodgen never closed by itself so I had to close it manually. So that's why when this time it did, I thought it crashed.

xLODgen.exe terrain LOD beta never closes itself. It ends with a "LOD generation complete" message. Always has. However the spawned and hidden LODGen.exe processes from which you posted the last few log lines does.

 

 

The custom templates from the Step tutorial here https://wiki.step-project.com/SkyrimSE:0.3.0b#xLODGen, those 4 images from "Terrain LOD generation"[/size]

 

When I first installed beta 64, the data was different, and I had to change it to the Step guide. When I installed beta 65, all 4 were present.

Cheers

These are called options or settings. xLODGen/xEdit stores settings between sessions in the same folder as plugins.txt for the selected game mode.

 

 

And this was the full log:

https://www.dropbox.com/s/w0b6hwdjvklknby/lodgen_log.txt?dl=0

https://www.dropbox.com/s/6epqvpmtxb0u2pu/sselodgen_log.txt?dl=0

[07:35] Error creating textures for level 4 quad [12,-40] Operation aborted
[07:35] Error creating textures for level 16 quad [0,-48] One or more errors occurred

I repeat, the reason why I ask is because the first 5 or 6 times when I generated terrain last week with SSELODgen, when it was done I had to close it manually. But the last 2 times, for some reason after RigmorRoscrea world both times it closed automatically, when I came to the PC only MO2 was running. 

So I thought it crashed or something.

 

The second log shows an error at the end?

 

Thank you.

 

PS: Could it be because I have ticked Grass Cache, the grass generated with No grass in objects? That's the only difference between these 2 runs, and the other 5-6 runs.

https://prnt.sc/wf7qfl

 

Again. xLODGen.exe never closes itself. Never has. In case of a problem there should be an error message in the log or a message window popping up.

 

"Operation aborted" typically means you closed the program before it was finished.

 

xLODGen does not care about grass data files.

Edited January 3, 2021 by sheson

[Stefan]

Edited because you edited your post so my answers sync to your edited post.

 

Thank you. I will try to troubleshoot the issue.

 

PS: The plugins.txt is in the MO2 profiles folder, but there is no xLodgen settings in there https://prnt.sc/wfal1r EDIT: SOrry, you mean that it stores them between sessions, so probably because I am running it now, there are no settings there.

 

"Operation aborted" typically means you closed the program before it was finished.
 

PC was untouched through the night, so I definitely didn't close it unless I was sleep walking. 

 

PS2: Good to know, so the issues are not with the grass. WIll try to isolate.

 

Thank you 

Edited January 3, 2021 by Stefan

[sheson]

Edited because you edited your post so my answers sync to your edited post.

 

Thank you. I will try to troubleshoot the issue.

 

PS: The plugins.txt is in the MO2 profiles folder, but there is no xLodgen settings in there https://prnt.sc/wfal1r EDIT: SOrry, you mean that it stores them between sessions, so probably because I am running it now, there are no settings there.

 

PC was untouched through the night, so I definitely didn't close it unless I was sleep walking. 

 

PS2: Good to know, so the issues are not with the grass. WIll try to isolate.

 

Thank you 

 

The games plugins.txt is in c:\Users\[username]\AppData\Local\[skyrim|Skyrim Special Edition]\Plugins.txt. Mod manager might have local copies that replace plugins.txt at this location at run time, but that does not change where the game or xEdit reads/writes standard game files.

 

xEdit/xLODGen settings are in Plugins.sseviewsettings

[Stefan]

Also, as a note, xEdit seems to be stalling for some reasons a lot of time https://prnt.sc/wfbksq .

 

The games plugins.txt is in c:\Users\[username]\AppData\Local\[skyrim|Skyrim Special Edition]\Plugins.txt. Mod manager might have local copies that replace plugins.txt at this location at run time, but that does not change where the game or xEdit reads/writes standard game files.

 

xEdit/xLODGen settings are in Plugins.sseviewsettings

Posting while you were also posting.

 

Thank you, I have found them. If this lod run doesn't work again, I will delete those settings too, and do a clean install of SSELODgen and try again.

Edited January 3, 2021 by Stefan

[sheson]

Also, as a note, xEdit seems to be stalling for some reasons a lot of time https://prnt.sc/wfbksq .

Without any context - like doing what - xEdit is probably waiting for user input or an external process to complete.

[Stefan]

Without any context - like doing what - xEdit is probably waiting for user input or an external process to complete.

What can I do to add context?

 

The only things that run together with xEdit are the AV, the system apps, Total Commander, which is something like Windows Explorer, Steam and Google Chrome with discord.

 

Also, xEdit was generating LOD for terrain when that PS was taken, following the SSE Step guide, the xLodgen part, to the letter, I triple quadruple checked. All cells selected, LOD8 to LOD32 using the guide settings.

 

There are no popup windows in xEdit.

 

Anyway, I just deleted the settings from AppData, reinstalled fresh in an empty folder, and trying it again following the steps and settings in the Step xLodgen guide for SSE.

 

Please let me know what you need for more context if xEdit stalls again.

 

Thank you very very much, and sorry.

 

EDIT: The AV is NoD32, Internet Security variant. 

 

EDIT2: After restarting fresh, following the SSE Step guide xLodgen, xEdit started using around 65% of the CPU, then after a minute or so is using only about 15% constantly with rare spikes that can go up to 100%. I have an I7 and I am using the 64 version of xLODGEN. 

 

EDIT3: I have even disabled screens going off, if there is the slightest chance that it interferes with it. I don't ever use system sleep, hibernation is disabled, the computer is never shut down, only restarted if it's required.

Edited January 3, 2021 by Stefan

[sheson]

What can I do to add context?

 

The only things that run together with xEdit are the AV, the system apps, Total Commander, which is something like Windows Explorer, Steam and Google Chrome with discord.

 

Also, xEdit was generating LOD for terrain when that PS was taken, following the SSE Step guide, the xLodgen part, to the letter, I triple quadruple checked. All cells selected, LOD8 to LOD32 using the guide settings.

 

There are no popup windows in xEdit.

 

Anyway, I just deleted the settings from AppData, reinstalled fresh in an empty folder, and trying it again following the steps and settings in the Step xLodgen guide for SSE.

 

Please let me know what you need for more context if xEdit stalls again.

 

Thank you very very much, and sorry.

 

EDIT: The AV is NoD32, Internet Security variant. 

 

EDIT2: After restarting fresh, following the SSE Step guide xLodgen, xEdit started using around 65% of the CPU, then after a minute or so is using only about 15% constantly with rare spikes that can go up to 100%. I have an I7 and I am using the 64 version of xLODGEN. 

 

EDIT3: I have even disabled screens going off, if there is the slightest chance that it interferes with it. I don't ever use system sleep, hibernation is disabled, the computer is never shut down, only restarted if it's required.

As I already said: like doing what? What exactly was the programs doing at the time of the screenshot.

 

Generating terrain LOD is two major different things: generating terrain LOD meshes and terrain LOD textures.

 

xEdit/xLODGen uses external process like LODGen to generate terrain LOD meshes and TexConv to convert terrain LOD textures. At times xEdit/xLODGen has to wait for these external process to complete their tasks.

 

I have no idea what you going on about, because it is not clear if there is a problem and if there is a problem what it is exactly.

 

It is perfectly normal for xLODgen.exe to have anything between 0% and 100% CPU. It totally depends on what it is doing at the time.

Edited January 3, 2021 by sheson

[Stefan]

Ok, thanks for the support.

 

I have reverted to beta 64, cleared the AppData xLODgen folder, installed it in a fresh folder, and for now it seems to work, it has already generated 3gb of files, so it's past the breaking point that lead to the previous 2 sessions crashes.

 

Something happened when I updated to 65, probably I should have cleared the AppData folder too, not only the program files. 

 

Also, I wasn't complaining, you said you need context, so I was giving context. About CPU usage, about OS, AV, what I was doing. 

 

Happy new year.

 

PS: When I showed you the first screenshot where xEdit was idle, it was idle for at least 1-2 hours, while it was supposed to generate meshes or textures. I left it running on one of the screens together with the task manager. So it was not a case of going from 0 to 100. But it doesn't matter now, since reverting to 64 seems to have done the trick.

 

Also, I work in IT, I am 40 years old, and I work on PCs since the first year of university 22 years ago. So while I am not accustomed with xLODGEN, I do know how to handle a PC, and know how a CPU behaves. Just as a note.

Edited January 3, 2021 by Stefan

[sheson]

Ok, thanks for the support.

 

I have reverted to beta 64, cleared the AppData xLODgen folder, installed it in a fresh folder, and for now it seems to work, it has already generated 3gb of files, so it's past the breaking point that lead to the previous 2 sessions crashes.

 

Something happened when I updated to 65, probably I should have cleared the AppData folder too, not only the program files. 

 

Also, I wasn't complaining, you said you need context, so I was giving context. About CPU usage, about OS, AV, what I was doing. 

 

Happy new year.

 

PS: When I showed you the first screenshot where xEdit was idle, it was idle for at least 1-2 hours, while it was supposed to generate meshes or textures. I left it running on one of the screens together with the task manager. So it was not a case of going from 0 to 100. But it doesn't matter now, since reverting to 64 seems to have done the trick.

 

Also, I work in IT, I am 40 years old, and I work on PCs since the first year of university 22 years ago. So while I am not accustomed with xLODGEN, I do know how to handle a PC, and know how a CPU behaves. Just as a note.

There is no need or requirement to clear the AppDarta folder. It would be part of the instructions if it were.

 

I still have no idea if it was doing meshes or textures, if it waited for LODGen or TexConv background processes to complete.

[Stefan]

I can confirm that it worked after downgrading to 64 and clearing the AppData, just downgrading by using a new folder the beta 64 didn't work. I don't know what happened.

 

I have just finished the terrain generation and the full 9GB are there, no crash, the CPU was never idle, and I got to see the end message. 

 

PS: I want to apologize if I appeared disrespectful or looking for a quarrel. I appreciate the work you are doing, for free, so thank you very much again for the apps and support. 

[sheson]

I can confirm that it worked after downgrading to 64 and clearing the AppData, just downgrading by using a new folder the beta 64 didn't work. I don't know what happened.

 

I have just finished the terrain generation and the full 9GB are there, no crash, the CPU was never idle, and I got to see the end message. 

 

PS: I want to apologize if I appeared disrespectful or looking for a quarrel. I appreciate the work you are doing, for free, so thank you very much again for the apps and support. 

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.

[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.

I will try to do it this evening. Now it's morning, 9 am.

Edited January 4, 2021 by Stefan