Jump to content

z929669

Administrator
 View Profile  See their activity

  • Posts

    13,028

  • Joined

  • Last visited

 Content Type 

Everything posted by z929669

  1. z929669
    Savegame could be an issue with such big changes. Try starting a new game to see if it loads. You likely still have something in the mod list that is not jiving. In that case, begin disabling blocks of mods and sort with LOOT paying attention to any LO errors in LOOD and MO. You just need to get the game loaded with all of your environment/landscape mods active to precache grass.
  2. z929669
    Looks like you need to install the version of SSE Engine Fixes for 1.5.97
  3. z929669
    This has nothing to do with DynDOLOD, so please post to these topics for related discussion. Once you have a 1.5.97 grass cache, you can generate grass LOD in SAE without NGIO (since we are waiting for .NET FW or similar for AE) using:
  4. z929669
    Discussion topic: Grass Cache Fixes by DoubleYouC Wiki Link Use a SSE 1.5.97-created grass cache in SSE 1.6.xxx without NGIO dependency to allow grass LOD in SAE. Related Topic s Get 1.5.97 without a backup Run 1.5.97 and 1.6.xxx on same PC via MO Kezyma's Root Builder for Mod Organizer Now that NGIO has been updated, downgrading the game is no longer necessary for generating the grass cache. Dropped as of 2.3 in favor of Grass Cache Helper
  5. z929669
    I will fix that now. I also just fixed some of what I had in my flurry to correct. I downloaded the latest ENBSeries for both SLE and SSE, so they have changed.
  6. z929669
    The file structures have change a bit, so I updated the instructions: Extract the contents of the "WrapperVersion" into the game folder (e.g., ..\Steam\steamapps\common\GameFolder). Note that only *.ini, *.dll files and the \enbseries\ folder are required. 0.467 is available for SLE, so that's just a tad different. The updated instructions apply to both I believe. I fixed a few more of the instructions in that section, which were a bit redundant or nonsensical. The ENB 'preset' is provided by a mod author, and should detail all requirements and instructions for installation. We only need to instruct about installing ENBSeries itself. We need eyes on these edits and the larger context of this article as it all needs an update I think.
  7. z929669
    This is the key I was missing! Just opening NifSkope.exe defaults to BS header 0, and only Ni* are available on Block > Insert spell. Once I change that value to 100, I now have additional Bethesda (and Havok) categories for selecting BS* nodes (blocks). In all of my scouring over NIF doc, I never found this. Thanks. I do prefer copy/pasting blocks via keyboard over removing them from the base model, since then I avoid all of the cleanup steps (e.g., extra strings). It's also difficult for me to strip stuff from models with skinning, since parent/child blocks are more complex, and I am often left with an inconsistent hierarchy and block names. It must all get sorted by LODGen in the hybrids.bat/DynDOLOD automation anyway? I do see that the method you lay out (CRC script on base models via xEdit > strip blocks > clean up > save as trunk/crown) is very straight forward. It trades-off the hassle of my copy/paste of CRC and treeName strings (using 7-zip CRC shell integration and Explorer) for the hassle of stripping/spells in NifSkope and launching xEdit. I will write up this approach once I run through it. So I can package my mods this way then? I didn't consider that DynDOLOD would scan recursively beyond \DynDOLOD\lod\trees, but that seems obvious now. Fantastic.
  8. z929669
    I do it mostly to look for changes in the installation (FOMOD, file names, or otherwise) in order to keep our instructions up to date.
  9. z929669
    How can I tell the NIF game format of any random NIF file directly (without surmising from the node names)? emptypassthru_lod.nif contains nothing I know of that indicates it's for LE and not SE. When I first was figuring out how to create hybrids, I was very confused about the empty NIF and where to get it (game format, base node name, other parameters). This is why I used emptypassthru_lod.nif as a basis. You should know that I have no issue with copy/paste of BSTriShape into emptypassthru_lod.nif (after I rename to empty_trunk.nif). And these become my trunks and are never updated with CAO or SSE NIF Optimizer. They do work as expected with LODGen in creating the hybrids or changing the textures. I will also add that I have always copy/pasted crowns into emptypassthru_lod.nif (after I rename to empty_passthru_lod.nif). Early on, I did not run these through CAO or SSE NIF Optimizer, and they worked without issue for hybrids or 'standard' LOD trees in my testing, so I must just be lucky or it doesn't matter for LOD? These days I run through an optimizer just to clean up junk if it came over with the mesh parts I copied (and after getting that advice from you).
  10. z929669
    Yes, it obviously helps to read the crash report ... @Mousetick doesn't miss much
  11. z929669
    Yep, I get it. This is why I finished my last post with a positive note about it being maintained. I tend to update every time just to keep abreast of changes. Still frustrating, but I do get it.
  12. z929669
    Will do Part of the process I use is running all crowns through SSE NIF Optimizer, which takes care of SSE format in my standard workflow. Good to know this though. In my workflow, this is just emptypassthru_lod.nif renamed as indicated above (I rename this same mesh for both crown and trunk for convenience). I use this for pasting the trunks, and those are consumed by hybrid.bat without issue and TexGen doesn't seem to care about this either way. So doing it that way, you must be renaming the base node to BSFadeNode, or it doesn't matter? I avoid cleaning up unused strings and such left from removing mesh parts, since it's an added step. Perhaps I will run emptypassthru_lod.nif through SSE NIF Optimizer before renaming to trunk/crown NIFs. This would ensure trunks are SSE format ... but I would still run crowns (and what I call "standard LOD models") through SSE NIF Optimizer either way to clean up strings and perform other menial tasks. In the meantime, I will try your method to see how it works for me. Thanks for the tips! I updated the article note at top to include a disclaimer that my workflow is one approach and that a standardized method is yet to come. I also changed options 1-3 to now be options 1 & 2 with preference as you indicated. The goal is to familiarize people with the general process, so I will update the article as I learn more.
  13. z929669
    It's almost certainly a compatibility issue having to do with the SAE updates. Some mods are not yet updated to SAE 1.6.353, and many more are not updated to 1.6.xxx. The Step Patches may also be incompatible with some mods at this point. We aren't really maintaining support for the SSE guide with all of the flux. You will need to be certain that you are running the version of Skyrim you expect and that all mods are supporting 1.5.97. Some mod authors are not supporting 1.5.97 and have hidden those versions of their mods (Arthmoor and the USP team). Not a great time for those without a lot of modding XP, and we are limited in how we can help. Ensure you are sorting with LOOT whenever plugins change and paying attention to all LOOT messages at the top of the LOOT window. Disable the highest-priority half of your mods, run LOOT (enable or disable mods if MO warns in the top right of the app). Sort with LOOT and test. Keep enabling/disabling blocks of mods until you know for certain which ones are causing isues. Then go to those mod pages and carefully read their requirements. ASLAL and (ASLAL is compatible) CRF (among others) do not support 1.5.97, so you really need to study the requirements and posts on the mod pages.
  14. z929669
    I'm officially getting frustrated with this mod updating so frequently on Nexus. Another update this morning followed by yet another 'beta' update this afternoon, which means that this update will likely be posted later today or tomorrow. With sooooo many tweaks needed, it's really obvious that the MA is not testing anything comprehensively before releasing. If relying on community feedback, it would be great to accumulate a list of fixes and constrain the updates to once a month or something. I think this mod has been updated nearly 50 times in the past 6 months. Geez. That said, at least it's being maintained!
  15. z929669
    Good to know. I forget those compares, but if after April 2021, they still apply, since this mod has not been updated since then. Now we have the mod page anyway.
  16. z929669
    @sheson I don't want to spread any misinformation, so if you are so inclined, please revise this article as you like or post recommendations here (you have edit rights on the wiki like any member).
  17. z929669
    Discussion topic: Creating Tree LOD Models by The Step Team A discussion topic for suggestions and feedback relating to the guide.
  18. z929669
    Discussion topic: Mari's flora by ArtByMari Wiki Link Looks like a good replacer for about 100 plants, but there are a couple of bugs that should be addressed. MA is active on Nexus, but seems to have stalled work on this mod. Just posting it in case it eventually evolves.
  19. z929669
    What's your tree mod? Looks like HLT or Jedi? I manage the LOD models for HLT, so I will verify those and the base models when I have time. I had been troubleshooting this issue on some of the dead pines with sheson's and T4's input, but we weren't able to cure it with texture revisions. If alpha and UV need tweaking, I think it would be best done on the base meshes and rebuild each of the LOD.
  20. z929669
    Looks like this mod has an unofficial update file ... updated. Plugin revision and INI that might make more sense now.
  21. z929669
    I created LOD for a few trees that might benefit or override vanilla or other mod's versions. Only about 5 trees, but shared with wSkeever, and he has added them in the most recent update (0.42). I won't be supporting Fixed Mesh Lighting trees for this, since I think that tweak to trees is not desirable, IMO (which is great, because that would be a lot of trees to work on).
  22. z929669
    I'm sure you noticed my false TexGen report on the DynDOLOD alpha topic. I just used that same output and ran DynDOLOD (HLT "all trees" option, no size change option selected, and add-on quality option). No such errors for me. This is the only missing textures stuff (these have always been missing and should probably be fixed): Did you have "HD Tree" and "Render" options ticked in TexGen? That would cause issues. It may also cause issues if you used wrong TexGen Output or had conflicts with that somehow. It may also be the AV/OS security problem.
  23. z929669
    I can confirm the output is as expected. Sorry for the false alarm. I should have checked the output and generated DynDOLOD myself. I just ran DynDOLOD without issue for these textures, so this confirms my false supposition. The only way I can think of that DynDOLOD complains about these textures is if the TexGen output is wrong somehow. Or the AV/OS security issue.
  24. z929669
    Click the message? That will give you answers
  25. z929669
    Got it. That is odd. I'm guessing it's an INI setting with a really short distance. @DoubleYou may know. Check your tree INI settings. The tree settings guide may help.
×
×
  • Create New...

Important Information

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

  I accept