I've made a retexture for the vanilla Whiterun windmill.
Used a new entry, as these are separate placements. I didnt wanted to interfere with the original model.
First try, using texture sets for the new colors:
Second try, copied the mesh and put these textures inside the mesh, using Nifscope:
Both times, I used the full model for the LOD, as seem below:
If I used the standard LOD, I would not get the new textures, as it would load the LOD from the standard vanilla texture.
In both times, I ran TexGen and Dyndolod. I've got the same result:
Why this is happening? I ran TexGen, ran Dyndolod, ran xLodGen for the terrain (although the terrain dont have anything to do with these objects), but I'm still getting the vanilla LOD, for a object with a entire separate entry, using a different mesh, and assigned the full model for the LOD mesh in the CK.
This is also happening with other vanilla objects, copied from the nordic ruins and retextured, and which passed through the same processes, also using full models for the LOD mesh in the CK. They all show the vanilla LOD when distant.
This is not happening with custom meshes from other authors, though. These are running fine with retextures, even using the same meshes with texture sets. Only vanilla meshes are being affected.
Is there a special rule I should put in Dyndolod for it? I tried this one below, but still got the same result:
Question
Wolfstorm321
I've made a retexture for the vanilla Whiterun windmill.
Used a new entry, as these are separate placements. I didnt wanted to interfere with the original model.
First try, using texture sets for the new colors:
Second try, copied the mesh and put these textures inside the mesh, using Nifscope:
Both times, I used the full model for the LOD, as seem below:
If I used the standard LOD, I would not get the new textures, as it would load the LOD from the standard vanilla texture.
In both times, I ran TexGen and Dyndolod. I've got the same result:
Why this is happening? I ran TexGen, ran Dyndolod, ran xLodGen for the terrain (although the terrain dont have anything to do with these objects), but I'm still getting the vanilla LOD, for a object with a entire separate entry, using a different mesh, and assigned the full model for the LOD mesh in the CK.
This is also happening with other vanilla objects, copied from the nordic ruins and retextured, and which passed through the same processes, also using full models for the LOD mesh in the CK. They all show the vanilla LOD when distant.
This is not happening with custom meshes from other authors, though. These are running fine with retextures, even using the same meshes with texture sets. Only vanilla meshes are being affected.
Is there a special rule I should put in Dyndolod for it? I tried this one below, but still got the same result:
2 answers to this question
Recommended Posts
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 accountSign in
Already have an account? Sign in here.
Sign In Now