Jump to content

z929669

Administrator
 View Profile  See their activity

  • Posts

    13,028

  • Joined

  • Last visited

 Content Type 

Everything posted by z929669

  1. z929669
    Aside from the DynDOLOD Qs, by the screen you posted, it looks way too colorful for Step, so you must have installed some other things not in the guide. If you untick the DynDOLOD output and Occlusion mods, you should see things the way you did before running DynDOLOD. Always run LOOT when you tick/untick mods containing plugins. Always check that all intended plugins are ticked in the right pane of MO (presumably all of them) Always refresh the MO mod list (F5 works) just after moving textures from xLODGen/TexGen/DynDOLOD outputs into the respective MO mods.
  2. z929669
    I think the screens you have tell the tale. I vastly prefer this mod and think it is technically a 'fix' for the gaudy particle aura of the vanilla effect. Other opinions?
  3. z929669
    If you want to change MM between Main/LS/DS, then all you need to do is install each variant into its own mod followed by the MM DynDOLOD file. The DDL file should always remain active, and all you need to do is enable ONE MM variant and regen LOD. You can save the LOD ourputs into three variations as well to easily switch between them. This is just a resource change, so it is very simple to do. With MO, there is no need to 'backup' as you mention. If you installed MO as standalone/instanced, then you can create completely different mod lists. Under a single instance, you can have many different profiles base on that mod list. See the MO guide for more info.
  4. z929669
    I'm not positive on the vanilla behavior of equipping arrows + melee weapons, but I cannot recall ever having two main weapons equipped at the same time in Skyrim. Bows take both R/L slots like two-handed, so you obviously can only have one equipped at a time when that's the case. maybe some mods get around this, but that is vanilla IIRC. On compatibility, use xEdit launched from MO and Data in the the MO right pane to check sources of resources. Use More Informative Console to investigate sources in game. Read mod descriptions and compatibility notes and bug reports. We don't support specifics outside of the guide, because there are nearly infinite variations and preferences. LotD is a totally different guide for more advanced users that want to tweak and fine tune to great detail (and accept all of the additional maintenance overhead), so not sure why we would want to use it as a base for Step. Maybe you mean the overhaul 'mod'? Step itself doesn't support major deviations from vanilla but rather show people how to mod the game so that they can take up this sort of challenge independently. Step is the simplest guide to comprehensively improve the vanilla experience drastically, IMO. EDIT: Note that the Step website DOES support guide creators in creating, maintaining, and hosting advanced modding guides, so feel free to ask for support on how to do that if you get that far.
  5. z929669
    I understand the distinctions. My point is that the default OOtB settings for xLODGen, TexGen, and DynDOLOD are probably close to optimal for most systems that are not higher-end with 4k-8k resolutions. Terrain LOD4/8 textures at 256k are not obviously distinguishable on my 2k monitor from current recommendations in the Step guides (512k). Same goes for quality of 0/2/4/4 (Step) vs 5/5/10/5 (closer to default when running xLODGen for the first time, IIRC). I can see slight improvements with the higher settings, but only on direct compare of screens, and the improvements are marginal at best ... not significant IMO. Given the trade-off, the FPS/VRAM hit is probably not worth the very marginal quality gain unless the resource ceiling leaves a lot of room to spare.
  6. z929669
    I never quantified the 'cost' of terrain LOD, but we should probably stop recommending 512 resolution at LOD4 and LOD8 and use 256 instead. sheson mentioned that there is no perceptible difference unless you have a 4k-8k monitor. Doing this may help you get back some frames. LOD32 still benefits slightly from 512, depending on a number of factors. You can also raise the quality of LOD4 and LOD8. I believe the default is 5. And 10 for LOD16, IIRC.
  7. z929669
    Yeah, that is what we said it was up above Please mark Tech's answer as "best answer" for posterity.
  8. z929669
    I would use an app like ENB Manager to properly configure you ENB. This could be what is going wrong. You could have messed with some SKSE stuff, since these are both installed directly into Data outside of MO. Otherwise, you likely have a plugin missing or enabled that doesn't belong to current load order.
  9. z929669
    Somewhere previously, sheson mentioned that water LOD is not created by DynDOLOD. I think he mentioned that terrain gen only needs to know what is and is not water. The seams are a game-engine limitation that can be dealt with by other trickery, like ENB. I see them as well with/wo ENB, but only when flying around at 1000 meters.
  10. z929669
    Hmmm. Semantics. The instructions are accurate, so if you are getting a CTD, then there are other factors that I am not aware of. I added new steps #7 and #8 in previous post ... I thought it was obvious, but perhaps now it makes more sense? TexGen creates the assets needed by DynDOLOD. The assets are created from your load order. Saving said assets and your DynDOLOD output into mods that can be activated/deactivated means that you can reuse them later (with corresponding load order). Changing the mod lineup in any way means that you need to regenerate ... if it is a mod that alters textures or meshes in the open world. Possibly even terrain. Depends on what changed. Read the MO warnings, search for conflicts, enable/disable mods based on reasonable conclusions. You can always copy your MO profile into a new one and enable mods selectively from top to bottom. You do not need to start over, but rather approach your problem selectively and purposefully (i.e., using an algorithm), given all of the tools at your disposal. Modding is largely problem solving. Much like any hobby (computers, cars, cooking, etc.)
  11. z929669
    You need to delete it because it is invalid for the changed load order. you are generating the output again and placing it under that same mod in step 9. Be certain after step 9 that all mods get ticked as described and also be certain that the plugins are all activated in the MO right pane. Load into a clean save to check things. Be mindful that you want to load a game in an interior cell every time DynDOLOD data is changed. If in doubt, start a new game to get a clean save and COW to the area. COW tamriel 14 -24 should get you somewhere near Riften.
  12. z929669
    First, I would go back in and click various parts of the ground in that area to be sure it is only picking up the one NIF. If so, then find the NIF under meshes/landscape/? ... probably (you can use the MO filter search to find it). Then you will be able to see what mod it belongs to. This probably isn't the NIF you want, but ... If you open the NIF in Nifskope, you can see what texutes is is supposed to reference.
  13. z929669
    So the mod is the only difference in those screens? Seems like all of Blackreach looks better in the second set. Maybe the particle aura?
  14. z929669
    Your logic makes perfect sense, particularly with respect to file size. But it is still much more work to create hybrids, IMO., Especially since *most* trunks us relatively few triangles anyway. I suppose 16 triangles is better than 50 though ... Above load order doesn't have issues. It's just modded and running ENB. I wanted to test under a (my) fully modded setup. I do see value in testing with nothing but vanilla hybrid/full trees and no mods but the minimal 'fix' and unofficial patches. Obviously no post-processing in that case.
  15. z929669
    @sheson You may find this interesting. Not sure how much performance testing you have done in the past. The following is pure apples-apples compare on my system after painstakingly preparing LOD tree statics from Myrkvior. This mod has 150 trees, and many are custom in addition to full vanilla replacement. I think it makes for one of the best candidates for performance compares, particularly with respect to full vs hybrid trees. I find hybrids to be twice as tedious to create as full, and with DynDOLOD 2.xx, it was 3x more tedious, IMHO. This analysis compares full to hybrid Myrkvior with all else remaining equal. Tested on clean runs of LODGen (same terrain and occlusion, different DynDOLOD). The avg FPS is a bit low, since I am running ENB and also compared only statics (all trees for LOD4/8/16 used Level0/1/2, respectively). I also used the recommended TexGen/DDL "max size" = 256 for all textures. Each run involved me flying around 'slowly' across all regions of Tamriel using same route. Each run is 10-20 min long: FULL HYBRID My system specs are linked in my sig. Given that this is a fairly meticulous compare (all variables carefully throttled besides tree type and non-specific random factors), I am fairly confident that the same relative differences would be apparent on just about any modern PC, but there could be hardware factors that could deferentially impact performance of essentially # of NIF polygons rendered (my assumption about the brass-tax diff between full and hybrid models). This is good news, because I can create full hybrids much faster and with fewer opportunities for error. Your thoughts?
  16. z929669
    I tend to agree with Arthmoor. I have been modding TES since 2006, and never ever cleaned a vanilla master until about 2012. I also have run Skyrim with uncleaned masters in modded setups many times. Never a single issue that I could attribute to the masters. I really don't think it matters for the vanilla masters. It may well be crucial for many custom plugins though. The reason most guides do it is because it just seems prudent on its face (and Step has set this precedent since around 2012, so most other guide authors do it to avoid scrutiny). All opinions count, regardless of 'staff' status, BTW. Let's see what others think.
  17. z929669
    I would look for those files in those mods and see why they are not loaded. Seems like you either have a mod(s) disabled or do not have a required mod installed that is expected by another mod. Just as likely, the mod files referenced by the plugins are not in the mod(s) ... i.e., poor housekeeping by mod author. As long as DynDOLOD finishes successfully, it may not matter at all (if they are just junk refs in the plugin(s)). sheson may have other advice, but you can check the problem mods in the meantime and look at those mods bug reports on Nexus.
  18. z929669
    Why not load the patch in xEdit and make the adjustments Tech noted? I think you may need to open/save the plugin in the CK after making the edit and saving in xEdit.
  19. z929669
    Arthmoor's solution is to just not clean the vanilla masters. I have always suspected cleaning them was redundant, since they always worked fine without cleaning. Then we can just omit this piece of the guide. All in favor?
  20. z929669
    Since it's a switch, and the executables are independent, I think it can be used only on the autoclean one only.
  21. z929669
    The LW patch is same principles as the CR patch but includes different mods in the patch. Tech will fix the LoS lights next update. You can use xEdit to see what records the patches touch. You could CTD if you remove LoS and retain the patch, but maybe not. You can certainly not use the patch, but you would probably notice other lighting issues then. loot may also complain. I recommend leaving it be until we update unless you know how to remove the LoS dependency in xEdit/CK. If you want to add a substitute, it gets even more complex.
  22. z929669
    Mostly correct, but you DO need to run DynDOLOD again. I suggest: Untick the MM Darkside mod, TexGen Output, DynDOLOD Output, and Occlusion mods in MO in case you want to compare with Main later (you don't even need the MM xLODGen file, since it is 100% redundant with the MM DynDOLOD file, which you DO need ... it works for all MM versions) Rename TexGen/DynDOLOD Output mods with a "MM - Darkside" suffix Delete everything under "TexGen/DynDOLOD Output - MM - Darkside" (except for meta file) Re-run LOOT Install MM Main and tick the mod. Move it to just after the MM Darkside mod (and before the MM DynDOLOD mod) Refresh MO by hitting F5 (to be sure all assets are prioritized correctly before next steps) Run TexGen as normal Create NEW "TexGen Output - MM Main" mod Create NEW "DynDOLOD Output - MM Main" Add to new "TexGen Output - MM Main" mod, and place just after the Darkside one. Tick this mod. Run DynDOLOD as normal Add to NEW "DynDOLOD Output - MM Main" mod, and place just after the Darkside one. Tick this mod. Enable Occlusion mod Run LOOT Launch game & take screens Now you can simply untickall MM Main mods and tick all MM Darkside stuff (MM DynDOLOD is always enabled), run LOOT and launch to get screen compares.
  23. z929669
    Thanks for the analysis! Guess we should check the 'bugs' area to see if there's any issues. if not, then we will need to see about what it could possibly replace.
  24. z929669
    Then we either need to switch to the beta or add the switch mentioned previously.
  25. z929669
    So you had the bad ground texture, and your game loaded. Then you disabled the CL terrain mod and the game still shows the bad ground textures? Use More informative Console to find the texture names and sources, then look in Data of MO right pane to find the mod and hide the texture or disable the mod.
×
×
  • Create New...

Important Information

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

  I accept