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

[z929669]

1 hour ago, sheson said:

Always post the log please. 

The SSE-Tamriel--tamriel.esm should not affect this,  unless there is a plugin in the load order also adds the same missing cells maybe.

Try the version from 

it should create a bugreport.txt.

Will do ... thanks

[z929669]

On 4/30/2021 at 12:39 PM, sheson said:

Always post the log please. 

The SSE-Tamriel--tamriel.esm should not affect this,  unless there is a plugin in the load order also adds the same missing cells maybe.

Try the version from 

it should create a bugreport.txt.

So it happened again first during DLC2SolstheimWorld ... event:

Faulting application name: xLODGenx64.exe, version: 4.1.3.1, time stamp: 0x6075af33
Faulting module name: xLODGenx64.exe, version: 4.1.3.1, time stamp: 0x6075af33
Exception code: 0xc0000005
Fault offset: 0x00000000013e6ef9
Faulting process id: 0x43e4
Faulting application start time: 0x01d742d3018be86e
Faulting application path: C:\Modding\Tools\xLODGen\xLODGenx64.exe
Faulting module path: C:\Modding\Tools\xLODGen\xLODGenx64.exe
Report Id: f4007d5d-7708-4b79-a39e-22136aa898e1
Faulting package full name:
Faulting package-relative application ID: 

... so I deleted log and tried again. Then it quit during DLC2ApocryphaWorld. LODGen_log.txt 

...and here is the event for that:

Faulting application name: xLODGenx64.exe, version: 4.1.3.1, time stamp: 0x6075af33
Faulting module name: KERNELBASE.dll, version: 10.0.19041.906, time stamp: 0x2f2f77bf
Exception code: 0x0eedfade
Fault offset: 0x0000000000034b59
Faulting process id: 0x4c3c
Faulting application start time: 0x01d742d62b3eee1d
Faulting application path: C:\Modding\Tools\xLODGen\xLODGenx64.exe
Faulting module path: C:\Windows\System32\KERNELBASE.dll
Report Id: 898e25e3-3dfe-4676-8526-54fc327ae45f
Faulting package full name:
Faulting package-relative application ID: 

I'm not seeing a bugreport.txt

[sheson]

5 hours ago, z929669 said:

So it happened again first during DLC2SolstheimWorld ... event:

... so I deleted log and tried again. Then it quit during DLC2ApocryphaWorld. LODGen_log.txt 

...and here is the event for that:

I'm not seeing a bugreport.txt

Can you replicate this with the latest xLODGen terrain LOD beta?

The exception happens in xLODGen (while generation terrain LOD textures IIRC), so the LODGen log generating LOD meshes does not show anything.

[z929669]

6 hours ago, sheson said:

Can you replicate this with the latest xLODGen terrain LOD beta?

The exception happens in xLODGen (while generation terrain LOD textures IIRC), so the LODGen log generating LOD meshes does not show anything.

Damn. I missed that update. I will test again with that. I was using what you last linked me to a few days ago.

[ikonomov]

It seems I'm getting a crash consistently with v80 regardless of the options I choose.  Previously (v77 and v76) it only happened when choosing specific chunk for LOD4.  Sadly I deleted the old version AND the output files I had, if still available it would be greatly appreciated if somebody can post the older v77 download link.

Thanks

[z929669]

1 hour ago, ikonomov said:

It seems I'm getting a crash consistently with v80 regardless of the options I choose.  Previously (v77 and v76) it only happened when choosing specific chunk for LOD4.  Sadly I deleted the old version AND the output files I had, if still available it would be greatly appreciated if somebody can post the older v77 download link.

Thanks

I ran v80 without issue recently but had the same issue with previous versions. I just saved the output, noted the worldspace where it failed in the log, and regenerated only the remaining worldspaces (they seem to execute in order of those listed in xLODGen). I copied the latest output over to former with overwrite. It seemed to work fine.

[sheson]

1 hour ago, ikonomov said:

It seems I'm getting a crash consistently with v80 regardless of the options I choose.  Previously (v77 and v76) it only happened when choosing specific chunk for LOD4.  Sadly I deleted the old version AND the output files I had, if still available it would be greatly appreciated if somebody can post the older v77 download link.

Thanks

There were no updates to the terrain LOD generation code after 75. This is still a beta test. Bugreport generation was added so we can troubleshoot better and fix the current version.

Not sure why you posted the bugreport in a PM. Anyhow, based on that, test with this version: https://mega.nz/file/xUhyjYzS#NJsm-U7ejFK2eqU8LHqwtPwI1scID_yBYh-AF-tKs-4

 

[ikonomov]

3 hours ago, sheson said:

There were no updates to the terrain LOD generation code after 75. This is still a beta test. Bugreport generation was added so we can troubleshoot better and fix the current version.

Not sure why you posted the bugreport in a PM. Anyhow, based on that, test with this version: https://mega.nz/file/xUhyjYzS#NJsm-U7ejFK2eqU8LHqwtPwI1scID_yBYh-AF-tKs-4

 

For the first time now I've been able to generate LOD4, LOD8 and LOD16 separately choosing the specific chunks using the .exe file you just provided.  I was also able to generate all terrain mesh files and textures for all LOD levels without choosing specific chunks without any problems.  I'm not sure what else to test, whatever you changed it seems to have worked.  If you need to isolate the problem further you can post more versions of xlodgen and I'll be happy let it run and test.

Anyways, this is awesome!  Thank you

[ikonomov]

I ran it again separately for LOD4, 8 and 16 a second time now just to make sure and still got LOD generation complete all three times.

[sheson]

6 hours ago, ikonomov said:

For the first time now I've been able to generate LOD4, LOD8 and LOD16 separately choosing the specific chunks using the .exe file you just provided.  I was also able to generate all terrain mesh files and textures for all LOD levels without choosing specific chunks without any problems.  I'm not sure what else to test, whatever you changed it seems to have worked.  If you need to isolate the problem further you can post more versions of xlodgen and I'll be happy let it run and test.

Anyways, this is awesome!  Thank you

Great! Uploaded as terrain LOD beta 81.

[ikonomov]

20 hours ago, sheson said:

Great! Uploaded as terrain LOD beta 81.

If not too much to go into, what was the problem?  After all this time trying to find the needle in the haystack it has made me curious. lol

[sheson]

4 hours ago, ikonomov said:

If not too much to go into, what was the problem?  After all this time trying to find the needle in the haystack it has made me curious. lol

Multithreaded access to the terrain texture cache that wasn't made fully thread save.

[ikonomov]

19 hours ago, sheson said:

Multithreaded access to the terrain texture cache that wasn't made fully thread save.

Ah.  I remember you mentioned something about multithread before.  Well it's great that this crash ends here.  The Beta in the title of this thread together with our crash reports might have turned away some people from using one of the best tools they could possibly get their hands on for their game.  I know we keep repeating ourselves, but thank you sheson.

[z929669]

@sheson Finally got a bugreport.txt with this latest version of xLODGen:

bugreport.txt

EDIT: Reran and got another. Including logs as well this time:

bugreport.txtLODGen_log.txt

[sheson]

2 hours ago, z929669 said:

@sheson Finally got a bugreport.txt with this latest version of xLODGen:

bugreport.txt 110.34 kB · 0 downloads

EDIT: Reran and got another. Including logs as well this time:

bugreport.txt 125.57 kB · 0 downloads LODGen_log.txt 98.3 kB · 0 downloads

Instead of the the LODGen log post the xLODGen logs.