some_random_guy

Hey guys, could anyone please help me figure out a similar issue ? MO was working absolutely fine for me for a very long while and then suddenly stopped working, when i start the game through MO it starts the launcher and the screen goes black for a second as if it's trying to start the game, but then it kicks me out to the desktop. At first i thought it was a problem with my mods, but even after reinstalling Mod Organizer without any mods and clearing my appdata/local/mod organizer data folder the game still won't launch. Here are the logs of my crash

High settings - Everything works, takes 10 minutes to generate, minimal performance loss. Thank you Sheson, you are a Legend.

Could be, sure.

It looks like you didn't click generate static objects when you were generating DynDoLod, that's the only explanation for you missing all the lod objects, and only having the tree lods. Go through DynDoLod process again, but load up advanced options and in advanced options unclick generate Dynamic objects and generate tree lods and only check for Generate static lods and create atlas. https://imgur.com/iJXBbyY Select low med or high for whichever preset you want. After LodGen is done just copy the files over to your mod organizer, dyndolod folder.

Well, you can see DynDoLod is working because windmill sails are seen from the distance (unless you have Skyfalls and Skymills instead of course), but you seem to be missing static lods, which should be located inside your dynDolod generated folder (which should be inside your mods folder if you are installing DynDoLod with mod organizer), look for a folder called meshes\terrain\tamriel. You should see alot of .bto files inside that folder and the total size of Tamriel folder should be around 900mb depending on the options you chose.

In the above video, it's the real trees that are too bright, not the LODS. But in your pictures it seems like you have a few lods that are too bright and a few that are too dark and then you have shadows applied to some tree models and not the others. Obviously a tree model that has a shadow applied to it, will look much different from the exact same tree model that doesn't have any shadows applied, so getting the right distance for the shadows and the switch to lods is the first thing you should look at, ideally you want your shadows to extend all the way to where the switch to lods is happening, only then you will know for sure whether your lods are too dark or too bright for a properly shadowed tree.

P.S Performance wise you can of course achieve the same effect by adding a mesh rule \mountains\ Lod4=Lod8 Lod8=Lod16 Lod16=Lod16 when running DynDoLod, but LOD8's used as LOD4 in this fashion will look pretty poor, as they use tiny LOD textures.

You are a hero Sheson, made an .esp to remove the is HD Lod flag from every mountain, removed the IsHDMeshMask=_lod_ from the export files, re_generated the .bto files and they all had IsSnow instead of isSnowHD and the snow shader is now being applied correctly to all my lod_1 meshes which are posing as lod_0 meshes! From preliminary testing, from switching nearly all mountain lod_1's to lod_0's I gained about 5% GPU usage and as far as I can see, the visual difference is unnoticeable when using HD textures on lod_1's vs lod_0's. As soon as I finish testing this and create the non snow mountain versions, i'll make comparison screenshots, do some performance testing and i'll upload the .esps and meshes and textures and possibly a set of vanilla .bto files with my updated mountain meshes and texture lods for everyone to use. Huge Thanks man, DynDoLod FTW!

Will do, thanks!

Grr, sorry man, got the posts mixed up, this forums format is hard to read :p

Thank you ! I guess creating an .esp to toggle HD LOD lod flag off the mountains should do the trick, i'll get right to it!

I had the same problem and SMIM was responsible. You'll need to install SMIM compatibility sails and generate DynDoLod with SMIM and compatibility sails activated if I remember this correctly.

Would be quite a stretch to call this thing a mod, but i'll happily supply the assets for people who don't mind using my mountain textures after i'm finished with them. Thanks for the idea, What I have also tried to do now, is replace lod_0 meshes with what used to be lod_1 meshes and apply the original fullsize mountainslab01 and mountainslab02 textures to them to quickly make a performance set of lods that still looked decent. And while the generated .bto files can be viewed in NifSkope and seem to be perfect, the game renderer just fully covers them with snow and from what I understand, this is the snow object shader at work, seems like the snow shader that's being applied to lod_0 objects is following the UV-map of the original mesh, so the UV_map of lod_0 must be set exactly as it is on the original mesh, but the UV-map of lod_1 file's that i've set as lod_0's is quite different and doesn't share the pattern. So it looks like removing the snow material from the base records will set everything right, but i'm wondering if there's also a way to make them work with the snow shader ? As far as i can tell there really isn't a way to copy over the UV-map from the lod_o to lod_1, so what options does that leave me with ? I know we are moving slightly away from the DynDoLod topic, but if you have any insight i'd appreciate it.

The only thing i need to do now, is find a mod that removes the snow effect from mountains to enjoy these lods in all their glory !

Spent a few hours today going through every mountain mesh and textures, adding new ones, resizing them in gimp to make exact copies of them for lod_1 (512x512) and lod_2 (256x256) and applying these textures to every lod mesh for these mountains, finally even the most distant mountain lods match my actual mesh textures. Saying that i'm happy with the result is quite an understatement ! https://imgur.com/XB00WjX Thank you very much for your hard work Sheson and i appreciate all the support that you provide to your users on here !

Well that explains it! Here I thought I was fixing the UV map, meanwhile making it unusable for the atlas and wasting my time. So the sizes and renames for .dds files aren't a problem as long the UV map is set right, that's good to know !

Thanks, i can rest easy now! And another one from me for today since Zilav isn't responding Could you tell me how LodGen and DynDoLod select the textures that get added to the atlas ? I've created some custom lod textures for the mountains and applied them to the lod.nif files, yet they wont get added to the texture atlas and as a result, when the .bto files are generated, the objects that I applied my custom textures to, get separated into a separate node, which obviously increases the size of the .bto file and makes them less efficient. Is there like a fixed set of textures that get added to the atlas and nothing else is allowed ? I've looked at the manuals and can't see anything about this. Actually, i've also edited the UV map in NifSkope for these objects as well to make them look a bit more upscaled, maybe that could have something to do with it as well, since the atlas gets split up by UV maps.

Sheson, could i ask you an unrelated question please ? Since you seem to know alot about scripting and papyrus vm and you knew enough about heap memory to produce a fix that solved crashes for 90% of Skyrim players, could you tell me for certain what effect increasing stack memory size has on the scripting overlay ? Since we have no tool that could track the stack memory usage, how do we know what an ideal memory size for our stack would be ? I can swear that increasing my papyrus stack size via ImaxAllocatedMemoryBytes has a positive effect on my game, and through testing I am now up to 1gb with no buffer overflow messages in papyrus log even on extremely long play sessions, and yet people are telling me that it's dangerous to have a value that high, but i've been playing with this setting for weeks and have seen no adverse effects, could you please settle this for me ?

Nope, i just thought to myself - "wtf!" loaded the save game again, ran to the same location and it wasn't there anymore:(:)

I had the same problem today, i had a part of the road and a cliff LODs stay loaded even when I got close to them, I'am loading DynDoLod into an existing save though.

It doesn't matter whether I use nifskope 2.0.4 or 2.0.1 or run the model inside the game, the results are absolutely identical, I prefer using 2.0.1 because it's compatible with Zilav's billboard creator tool. The only difference I notice is when I open any .bto mesh generated via a DynDoLod tool in Nifskope 2.0.4 , I receive this message: I have completely reinstalled DynDoLod yesterday, tried generating new LODS with no TexGen textures and no mods active in M.O. and ended up with the same result, not sure how this can be happening. I use the latest nvidia drivers on a 970 gtx gpu, i will try reinstalling them today and i will try default .ini files instead of my modded ones.

This is very interesting indeed. The meshes I use are what comes with DynDoLod itself, there is nothing overwriting the meshes that are flickering and I have no _lod meshes except for vanilla ones that are stored in .bsa archives. The only thing that I have modified are the textures that I generated with DynDoLOD TexGen script for my mods, is it possible that textures cause flickering ? I didn't think they could. I have generated about 6 passes in total and they all had the same result, but I'm going to generate a few more now that I know it's a problem somewhere in my setup.

That's exactly what i'm trying to figure out, how to get this awesome tool to work right.. i'm on my third day now. I'm looking at the separate mesh of the pond LOD (tundrapond01_lod) as supplied with DynDoLod and they don't flicker, but when combined inside a .bto, they start to flicker. However, the separate lod mesh consists of 3 parts, but when combined inside a .bto, the same mesh becomes a 1 part object which starts to flicker.. How can this be fixed on my end ? Here is a video to illustrate what i mean https://youtu.be/ebslzFPykwI

Doesn't matter whether it's Nifskope or Skyrim, flickering is exactly the same. I'm not a huge fan of flickering and had to get rid of quite a few distance overhaul mods as they were causing them, thought that DynDoLod would be better than this..

Not sure why, but my DynDoLod generated meshes seem to suffer from terrible flicker-osis.. https://www.youtube.com/watch?v=nimkcsAD8o4&feature=youtu.be