z929669

The 1.0.0 guide has both Ethereal Clouds and CWS to install without any modification (which is what I am running). There are no conflicts between these mods or between these and OMF. OMF just uses a plugin to modify whatever is providing the fogs texture, which may be Ethereal in these shots. I don't think there is an diff in brightness between those shots. They both use the same ... ?textures?, and OMF just increases the density. I just don't see any 'glare' with or without. Just a little fog vs more fog. EDIT: OP updated. Looks like Ethereal only makes the sky more blue and enhances the clouds. I see no diff with the fog, so it must be vanilla fog. I prefer OMF with Ethereal both with and wo ENB (middle shots). Looks like the OMF plugin is really only changing "XSCL - Scale" and maybe adding some "XCLR - Region"s. Not sure but it doesn't look like it is using any model/texture. If so, then it's just an effect? EDIT2: Just saw that you had instructions not to install Ethereal Clouds if CWS and LW Patch are installed ... needless to say, I didn't follow those instructions and had both running this whole time.

Posted compares. I think this one is a no-brainer if you like obscuring the mountains a bit more to give the illusion of bigger mountains and larger expanse (I do). There is no color diff ... it just adds a bit more fog.

Discussion topic: ENB Helper SE by aers Wiki Link

Discussion topic: ENB Light by 4109 Wiki Link EmbersXD seems to have built in compatibility for its meshes so ENB Light should not overwrite them (will need to hide or not install this meshes) Battle Ready Candlelight Fixes is completely overwritten by this mod (so hide these as well)

There are some explicit instructions and commentary on Skyfalls and Skymills in the DynbDOLOD doc. I suggest you look at the doc and search for that commentary. The short version is that you don't need this mod to get the effects of 'working' windmills.

ditto^

I don't think it's a problem if all changes are forwarded. I would save the ESP and try the ESM to see.

We created the System Setup Guide specifically to instruct how to reacquire game files and a wealth of other essential info. Sounds like you would benefit from reading it.

Thanks for confirming! EDIT: Yep, that fixed the issue.

Indeed, sorry: textures.7z

Ha! See, I never knew that. I will probably continue my own way, since it's built in ... unless I remember to try that. Maybe it will stick.

What I did previously for 3D LOD (not hybrid) is copy past these nodes to the empty_passthru_lod.nif root node: All trees are this simple, but the trunks are much too bright in the LOD. I had converted these from NiTriShape + NiTriShapeData into BSTriShape, so I have access to both model types (attached all). This LOD model gives very bright trunks though, unlike the full models BSTriShape (converted): treeaspen02.nif NiTriShape + NiTriShapeData (original): treeaspen02.nif LOD model created from BSTriShape model and empty_passthru_lod.nif: treeaspen02_72358853passthru_lod.nif

Nice. Thanks for confirming. marked your own answer as solution.

That's why I like MO so much. Many ways to accomplish the same tasks. ... and I often discover new ways of doing things from posts like yours. Lotsa options

Just to clarify ... you had used a different mountain mod than MM, but now you want to switch to MM per the guide and convert all related mods likewise in the process? If so, it all makes sense to me now. I hadn't considered that and was a bit confused until now (I think).

Interesting (and good) tip. I just install new mods as usual and slow-double click on the priority to change it to the correct #. I also use section headings that match our 20 modGroups, color coding each differently (all Gameplay* ones with same color though). This makes it simple to move the scroll bar in the left pane to the area of interest.

@sheson I'm working on an aspen tree mod and want to create 3D statics of full models to determine if I can get the trunks to look better. The hybrid trunks turn out well, but when I create the 'full' statics, the LOD trunks are very bright ... almost white, while the trunks of the full-size meshes used to create the statics look fine. For flat trunks, I obviously use the empty_trunk.nif provided, but for 'full' statics, I use the empty_passthru.nif provided. Do you have any recommendations for 'white' trunk full LOD? I can remove or change the vertex colors or add/remove shader properties on the trunks, but not positive what will yield the correct result. The trunk shader properties are all compatible with LOD I think. I can share the NIF with you if that would be helpful. I have read through the doc, so please point me to that again if something specific to this 'issue' is addressed there. EDIT: I found this post, but not necessarily the same issue it seems. I should also note that this mod is replacing vanilla assets only, so no plugin.

Note that I created the LOD for the 1.03 main file, which seems to be closest to vanilla of the two downloads. I'm not sure if the 2.32 "Autumnal (single color)" version is identical to 1.03 or not, but I can create LOD for these three as well, I suppose.

Sorry for the late reply. I suggest updating to the SE 1.0.0 guide as a first measure ... see this post for details

Just update all mods that MO says are outdated (and are truly not up to date ... many mod authors do not handle Nexus versioning correctly or consistently, so MO can think an update exists when it does not.

It looks like a good fix, but pointing to a google Drive indefinitely isn't going to work, I suspect. This should really be hosted on the Nexus for posterity, even if it must be uploaded as a new mod.

OK, then that seems like a question for the NGIO mod author(s) or nexus posts area. If you learn anything new there, please post back your findings. I personally have not experience this issue, but I also haven't been testing for this.

Overwriting should not be an issue, especially if you installed the Resources where indicated by the guide. Revisit that to be sure it is in the correct priority in MO. Otherwise, this can happen if you have DynDOLOD 3 alpha versus 2.xx (as used in the SE 1.0.0 guide) with the wrong resources downloaded and installed. It can also happen if you did not set up DynDOLOD with the correct game switch as instructed in the Tools section of the System Setup Guide. Alternatively, the file name itself can be changed to the game type, but that's not how we instruct to do it in the guide.

Not really so much patching as getting things to look right with Cathedral Landscapes and your mountain mod. It would help if you provided more about what you are trying to accomplish. If you only changed the mountain mod used, then it's just a matter of installing MM and looking at the conflicts, etc.

I fixed the wording in that section and rewrote some of it for clarity.