Jump to content

Recommended Posts

Posted (edited)
  On 3/3/2020 at 4:29 PM, MrSnakestone said:

I don't know if this is the right place to ask for help, but it's the only one relevant to my issue:

 

This is a weird issue that started up yesterday. I wanted to generate some LODs for a town mod I was testing. Now everything generated fine and I could get ingame, but I forgot to disable a mod that if lods are generated for will cause a floating glacier above whiterun fields near 0,0. So I had to redo my LODs again, no big deal I've done it many times before, but this time I got a invalid lodsetting file error. First time I ever got this, but I didn't pay it much mind and used the LODs that were generated. This caused me to CTD. So I deleted the LODs via MO2, and no I checked my overwrite folder and there's no LOD files in it, and generated the LODs again. After a few attempts and a post on SSELodGens page I got LODs to generate without the error, but I crashed again. The crash happens when the loading screen is about to transition into me actually being in the game. I tried everything, disabled mods, enabled mods, generated LODs and tried many new saves and coc qasmoke, but I still CTD'd. I thought my issue was Animated Armory, but even with that gone I still CTD with SSELodGen LODs enabled in my mod list. If I try to play the game without generated LODs I have floating half aspen trees all over the place. I'm at a loss on what to do and try, anyone got any advice or help.

Are you using an older MO2 version and/or forgot to set a dedicated output folder with -o as recommended on the first post? The lodsetting or single object LOD source textures being corrupted happened quite a bit earlier last year. But with the regular MO updates all reports died down.

 

In any case, create or install a valid lodsettings files again. Update to latest MO2 and latest xLODGen. Remove all generated LOD files from meshes/terrain and textures/terrain.

 

Generate LOD with -o into a dedicated folder. If it complains about not being able to read textures, install those again as well until there are no errors.

Then install the output as a mod in MO.

 

If there are still problems in the game then first temporary remove tree LOD in meshes\terrain\[worldspace name]\trees, then meshes\terrain\[worldspace name]\objects, then the terrain LOD *.BTR  in meshes\terrain\[worldspace name].

 

Once yo know which LOD type causes the problem, do the usual temporary remove half testing until you are down to only one or a handful files causing the problem.

 

Check them in NifSkope for errors or upload them for me to test.

Edited by sheson
Posted
  On 3/3/2020 at 4:51 PM, sheson said:

Are you using an older MO2 version and/or forgot to set a dedicated output folder with -o as recommended on the first post? The lodsetting or single object LOD source textures being corrupted happened quite a bit earlier last year. But with the regular MO updates all reports died down.

 

In any case, create or install a valid lodsettings files again. Update to latest MO2 and latest xLODGen. Remove all generated LOD files from meshes/terrain and textures/terrain.

 

Generate LOD with -o into a dedicated folder. If it complains about not being able to read textures, install those again as well until there are no errors.

Then install the output as a mod in MO.

 

If there are still problems in the game then first temporary remove tree LOD in meshes\terrain\[worldspace name]\trees, then meshes\terrain\[worldspace name]\objects, then the terrain LOD *.BTR  in meshes\terrain\[worldspace name].

 

Once yo know which LOD type causes the problem, do the usual temporary remove half testing until you are down to only one or a handful files causing the problem.

 

Check them in NifSkope for errors or upload them for me to test.

I was running an old version of MO2. I updated that and updated xLODGen to the newest version. I did my LODs and didn't get any errors, but now I CTD even faster.

Posted (edited)
  On 3/3/2020 at 5:11 PM, MrSnakestone said:

I was running an old version of MO2. I updated that and updated xLODGen to the newest version. I did my LODs and didn't get any errors, but now I CTD even faster.

There are probably still corrupt meshes or textures in the load order.

 

In addition to what I already suggested how to find the problematic LOD mesh, maybe install .Net Script Framework first. Its crash log might actually mention the corrupt file directly.

Edited by sheson
Posted (edited)
  On 3/3/2020 at 5:19 PM, sheson said:

There are probably still corrupt meshes or textures in the load order.

 

In addition to what I already suggested how to find the problematic LOD mesh, maybe install .Net Script Framework first. Its crash log might actually mention the corrupt file directly.

So I removed the files from tamriel's folder and was able to get into the game. Everything was messed up, as expected, but no crash. So I tested it with another worldspace and I crashed. So is it tamriel's meshes that are corrupted? Do you mind taking a look at them?

 

https://mega.nz/#!VyISFITJ!Dn446s6JGxeTUX_4Vr0aUtcTzZv4e2AGPjy7QtXb16Y

 

Also I tried .net script but it didn't give me a crash log.

 

Edit: I went back in and coc'd to Raven Rock and CTD'd, so Solstheim's LODs must be corrupt too.

Edited by MrSnakestone
Posted (edited)
  On 3/3/2020 at 6:09 PM, MrSnakestone said:

So I removed the files from tamriel's folder and was able to get into the game. Everything was messed up, as expected, but no crash. So I tested it with another worldspace and I crashed. So is it tamriel's meshes that are corrupted? Do you mind taking a look at them?

 

https://mega.nz/#!VyISFITJ!Dn446s6JGxeTUX_4Vr0aUtcTzZv4e2AGPjy7QtXb16Y

 

Also I tried .net script but it didn't give me a crash log.

 

Edit: I went back in and coc'd to Raven Rock and CTD'd, so Solstheim's LODs must be corrupt too.

Not sure why you can't do the basic troubleshooting by eliminating half of the meshes each step yourself?

 

I can load into Tamriel just fine with the meshes and textures you sent me.

 

That is most likely because not all the textures used by the LOD meshes aere part of the archive you uploaded.

 

It seems that object LOD atlas generation was not checked, so the object LOD meshes use a lot of texture directly.

 

One or more of those textures might be corrupt, may have an unsupported compression format or may have a resolution that is not of 32, 64, 128, 256, 512 etc.

 

Generate xLODGen to generate an object LOD texture atlas. Make sure there are no error messages in the log.

Edited by sheson
Posted

Hi sheson, I have got a question concerning the terrain generation. Whenever I generate LOD with xLODGen the terrain looks much darker than the foreground. If I use the noise textures and brighten it or generate the lod with a higher brightness setting, so that the ground looks bright enough, other parts of the landscape that I don't want to change also get brighter. I noticed that the grass mod that I am using is somehow covering all of the nearby landscape. Would it be somehow possible to use the grass texture to generate certain parts of the terrain so that there is a smooth transition between the nearby grass and distant terrain? It is very noticeable when riding through the countryside and is not very immersive. Here are some pictures:

 

Nug5DmUl_t.png bJwZEOKT_t.png

 

Thank you in advance and thanks for the great tool!

Posted (edited)
  On 3/8/2020 at 6:45 PM, BlackOncilla said:

Hi sheson, I have got a question concerning the terrain generation. Whenever I generate LOD with xLODGen the terrain looks much darker than the foreground. If I use the noise textures and brighten it or generate the lod with a higher brightness setting, so that the ground looks bright enough, other parts of the landscape that I don't want to change also get brighter. I noticed that the grass mod that I am using is somehow covering all of the nearby landscape. Would it be somehow possible to use the grass texture to generate certain parts of the terrain so that there is a smooth transition between the nearby grass and distant terrain? It is very noticeable when riding through the countryside and is not very immersive. Here are some pictures:

 

Nug5DmUl_t.png bJwZEOKT_t.png

 

Thank you in advance and thanks for the great tool!

 

As explained and discussed in this thread several times already, the combined terrain LOD textures look exactly as the full textures in the loaded cells - as long as the "improved" snow shader is disabled.

 

Grass is not textures but 3D models. For now you have to manually change landscape texture to simulate grass as Terrain LOD Redone and Cathedral Landscapes do. Some kind of grass baking is tested, but I did not have much time for it so far.

Edited by sheson
Posted

I've been having infinite load screens when entering the overworld or fast traveling, which went away when I disabled occlusion.esp. Regenerating the esp didn't help, and I haven't seen any error messages when generating - how should I go about diagnosing what is causing this? I'm sure it's occlusion exposing a problem in some other mod, but I'm not sure how to identify the cause.

Posted
  On 3/16/2020 at 4:06 PM, DarthVitrial said:

I've been having infinite load screens when entering the overworld or fast traveling, which went away when I disabled occlusion.esp. Regenerating the esp didn't help, and I haven't seen any error messages when generating - how should I go about diagnosing what is causing this? I'm sure it's occlusion exposing a problem in some other mod, but I'm not sure how to identify the cause.

You obviously have looked at Occlusion.esp in xEdit already? All it does it overwrite existing CELL records and update/add TVDT (and MHDT if is missing).

 

If Bashed Patch was part of the load order and had CELL records then that would be the first thing to look at.

 

The obvious method to troubleshoot this is to remove half the overwrites and test if problem still occurs.

If not, restore backup and remove the other half.

repeat until only one record remains.

Posted (edited)

So I tried generating occlusion.esp from scratch with bashed patch disabled, and I'm still getting the ILS only with occlusion.esp enabled. Are there any other troubleshooting steps you'd recommend?

Edited by DarthVitrial
Posted
  On 3/21/2020 at 6:20 PM, DarthVitrial said:

So I tried generating occlusion.esp from scratch with bashed patch disabled, and I'm still getting the ILS only with occlusion.esp enabled. Are there any other troubleshooting steps you'd recommend?

As already mentioned, remove half the records in a binary search until the problematic one remains.

  • +1 1
Posted (edited)

Hi,

 

New xLodGen user here, i have an issue when generating i have only the texture folder in my output not the mesh one.

And in the log file i find this:

 

[00:09] <Error: Could not execute "E:\Téléchargements\Programs\xLODGen\Edit Scripts\LODGenx64.exe" "E:\Téléchargements\Programs\xLODGen\Edit Scripts\LODGen_Terrain_Tamriel.txt">
[00:09] [Tamriel] Terrain LOD meshes generation error: System Error.  Code: 109.
 
Someone know this issue??
 
Thanks in advance.
Edited by wavejumper
Posted
  On 3/25/2020 at 3:42 PM, wavejumper said:

 

Hi,

 

New xLodGen user here, i have an issue when generating i have only the texture folder in my output not the mesh one.

And in the log file i find this:

 

[00:09]
[00:09] [Tamriel] Terrain LOD meshes generation error: System Error.  Code: 109.
 
Someone know this issue??
 
Thanks in advance.

 

The OS or some 3rd party tool is probably preventing xLODGen from running. Check if LODGen_log.txt contains any useful information.

 

Do not install anything into special Windows folders like Program Files x86.

Make sure to set a dedicated output folder with -o

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.