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

[hanzabu]

17 minutes ago, sheson said:

Upload bugreport.txt and  answer the question if the error happens at the same part of the process, e.g. check the if the error message "Error saving textures" is for the same LOD level and coordinates / same filename.

If it is make sure the output folder is empty and that OS anti virus do not interfere with writing.

No i doesn't crash at the same part or at the same filename & my AV is disabled.
Also never had this problem with the older versions.

bugreport.txt LODGen_log.txt log.txt

[sheson]

30 minutes ago, hanzabu said:

No i doesn't crash at the same part or at the same filename & my AV is disabled.
Also never had this problem with the older versions.

bugreport.txt 62.01 kB · 0 downloads LODGen_log.txt 87.18 kB · 0 downloads log.txt 1.15 MB · 1 download

There is no need to upload the discreet log from the LODGen.exe meshes generation.

Do not install the game into special Windows folder like Program Files x86 to avoid problems with UAC and antivir.
Do not generate into mod manager folders. Especially while the mod manager is running.
Remove the dedicated output folder to make sure it is really empty and there are no hidden blocked files or folder accessed by other processes.

See what happens when using this test version. Upload bugreport and SSLODGen_log.txt

[hanzabu]

1 hour ago, sheson said:

There is no need to upload the discreet log from the LODGen.exe meshes generation.

Do not install the game into special Windows folder like Program Files x86 to avoid problems with UAC and antivir.
Do not generate into mod manager folders. Especially while the mod manager is running.
Remove the dedicated output folder to make sure it is really empty and there are no hidden blocked files or folder accessed by other processes.

See what happens when using this test version. Upload bugreport and SSLODGen_log.txt

 i really did all of the above but still have the same problem, can u please make available version 86, i made the mistake of deleting it.

[sheson]

12 minutes ago, hanzabu said:

 i really did all of the above but still have the same problem, can u please make available version 86, i made the mistake of deleting it.

The test version from the last post is beta 86. As expected it makes no difference. The terrain LOD generation code did not change between beta 86 and beta 87.

Upload the bugreport and SSELODGen log. Troubleshooting is about finding the cause of the problem and fix it. Not ignoring problems.

Then test with this test version and upload bugreport and SSELODGen log of that as well.

[hanzabu]

13 minutes ago, sheson said:

The test version from the last post is beta 86. As expected it makes no difference. The terrain LOD generation code did not change between beta 86 and beta 87.

Upload the bugreport and SSELODGen log. Troubleshooting is about finding the cause of the problem and fix it. Not ignoring problems.

Then test with this test version and upload bugreport and SSELODGen log of that as well.

sorry i thought u were posting the same test binary,
i confirm when using 86 it's working perfectly without ctd.

LODGen_log.txt

[sheson]

7 minutes ago, hanzabu said:

sorry i thought u were posting the same test binary,
i confirm when using 86 it's working perfectly without ctd.

LODGen_log.txt 352.95 kB · 0 downloads

Again, there is no point in uploading the log from LODGen generating terrain LOD meshes.

Upload the SSELODGen log.

Then run this test version and upload its SSELODGen log and bugreport - if it exists.

[hanzabu]

7 minutes ago, sheson said:

Again, there is no point in uploading the log from LODGen generating terrain LOD meshes.

Upload the SSELODGen log.

Then run this test version and upload its SSELODGen log and bugreport - if it exists.

sry i dont know which log file you r refering too, the only files generated r those i posted, do u want me to copy the output in xlodgen window ?

[sheson]

8 minutes ago, hanzabu said:

sry i dont know which log file you r refering too, the only files generated r those i posted, do u want me to copy the output in xlodgen window ?

The SSELODGen_log.txt is saved when xLODGen is closed.

[hanzabu]

7 minutes ago, sheson said:

The SSELODGen_log.txt is saved when xLODGen is closed.

sry i'm an idiot, i didn't close xlodgen for the file to get generated, here u go & thx for your patience (it would be wise to name those test binaries differently, so we can communicate more effectively)

SSELODGen_log.txt

[sheson]

11 minutes ago, hanzabu said:

sry i'm an idiot, i didn't close xlodgen for the file to get generated, here u go & thx for your patience (it would be wise to name those test binaries differently, so we can communicate more effectively)

SSELODGen_log.txt 2.59 MB · 0 downloads

Great! Good to know that test version #4 works as it is based on beta 87.

Now if you could also run test version #3. I expect it to fail. Upload SSELODGen and bugreport please to conclude the troubleshooting.

[hanzabu]

17 minutes ago, sheson said:

Great! Good to know that test version #4 works as it is based on beta 87.

Now if you could also run test version #3. I expect it to fail. Upload SSELODGen and bugreport please to conclude the troubleshooting.

here r results for test version #3
it did fail and rather quickly compared to the others

bugreport.txt SSELODGen_log.txt

[sheson]

11 minutes ago, hanzabu said:

here r results for test version #3
it did fail and rather quickly compared to the others

bugreport.txt 109.11 kB · 0 downloads SSELODGen_log.txt 703.49 kB · 0 downloads

Thanks for all the help. That's all I need.

Keep using the last version (#4) that worked.

[myztikrice]

Where can we see the changelog for xLODGen?

[sheson]

6 hours ago, myztikrice said:

Where can we see the changelog for xLODGen?

On the xEdit discord.

[Mephitic]

Beta 88 crash. Fortunately I have 86 still archived. No problems with that version - all else identical.

bugreport.txtLODGen_log.txt

No SSELODGen_log.txt was created. I assume that is because the window closed itself - I didn't get the chance.

Edited February 12, 2022 by Mephitic