z929669

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.

You need to enable the DynDOLOD resources as described in the guide. In fact, you need to enable all mods that you install. Please revisit the mod instructions for DynDOLOD under 03-Resources.

Yes yes not necessary, but fine yes should work fine if you follow the instructions probably ... but there is a lot of detail and gotchas in between the steps you've listed. If you know how to run the tools and install mods, then you should be fine. Otherwise, I suggest that you follow along with our setup guide just to be sure you have the infrastructure set up correctly. Else you will be stuck on things that have nothing to do with DynDOLOD. You might also consider running with the beta version, since this is a thread for DynDOLOD 3.00 alpha (for testing and helping out with development). My advice is to forget about installing multiple tree mods that don't necessarily work together without some custom patching. Myrkvior alone is a big tree overhaul. If you want to learn how DynDOLOD works and how to use it, you don't need any mods at all. If you have a working mod list and just need to get the proper LOD, then you can try your steps above, but it sounds like you could potentially have a lot of questions and issues that are not likely related to this topic. If a stable LO is what you want and developing a general understanding of how to build one, maybe try following the Step guide as a first measure and post questions on our guide forums for help ... or just follow along with the LOD section in that guide using DynDOLOD 2.xx. As sheson will undoubtedly say: See first post about logs to include when posting. Also, see the links above.

The settings under the spoiler here work well for Cathedral Landscapes grass. You can test with ENB and lower all by, say, 0.1 if they are still too bright.

Sounds good. Will adopt those changes in my setup

Awesome. We need a FO-knowlegeable (and interested) party to do this, so it looks like a good thing from all sides if you are into upgradeing an FO guide. There is no PHP that you will see. It's all handled by Semantic Mediawiki functions, forms, and templates. Just have a look at the Step Portal as mentioned, click through to the FalloutNV home page, and go to it's portal page for all you need to create the mod pages and the guide. We will step in to help as needed. I will grant you the necessary edit perms to get started. You can edit most pages as a member, but using the guide infrastructure requires more.

Are you using an FPS monitor? DynDOLOD and NGIO both can cost enough in performance to cause stuttering. In my testing, terrain LOD costs me 5 FPS, and DynDOLOD can cost me a minimum of 10 FPS on the very lowest settings (and I have a pretty beefy box). Add ENB, and you are losing at least another 5-40 FPS. If you have lower than 40 FPS, you can start seeing some stutter or 'lagginess'. Look at the second post and try some of the recommendations under the 'performance' section. If that doesn't help with the stutter, check that DynDOLOD works as intended by generating LOD without NGIO active in your mod list. If that doesn't have stutter, then try disabling the DynDOLOD mod (created from your output) and run NGIO using the recommended settings. These WIP instructions for DynDOLOD w/wo grass LOD should help (sheson has not yet fully vetted, so take his advice over ours if conflicting)