Jump to content

z929669

Administrator
 View Profile  See their activity

  • Posts

    13,086

  • Joined

  • Last visited

 Content Type 

Everything posted by z929669

  1. z929669
    Got it. I failed to look at posts. I would expect this to be in the description though
  2. z929669
    What about SSE compatibility, since these are SLE-compatible meshes?
  3. z929669
    just my take: This is probably confusing for those less familiar with DynDOLOD dev. I know it's not 'incorrect' but it's a little misleading due to some visual inconsistencies. The Main Files don't have "2.xx" label (analogous to the Misc File), and the Misc File would benefit from a file description analogous to the Main Files: "Alpha version: ignore the Main Files if using this version". I usually get all of the files from the OP, but even our dev guide instructions were wrong due to recent changes to the SSE Nexus source files/layout. In my XP, many people don't read/see much other than what they want or expect.
  4. z929669
    Looks good. I prefer a controller with this mod, which adds a lot of good options as well.
  5. z929669
    Yes, I saw this MA posting with sheson. The screen shared looked very good
  6. z929669
    I haven't been messing with grass LOD for a while now. Glad you agree. Did you get decent performance? SSE FPS Stabilizer active?
  7. z929669
    Be sure you have a trailing slash for the path in the EXE config in MO for the "start in" line. Also check for spaces and enclose paths in quotes if there are any.
  8. z929669
    There are potentially many things that can cause this, including presense of expected TexGen output, DynDOLOD Resources conflicts, disabled mods, on, and on. You will be asked to provide the log files mentioned in the OP and forum rules of this topic to resolve and avoid guessing.
  9. z929669
    Special chars are almost always an issue in the programmatic dependency chain. I didn't know Windows allowed these chars (Although, I do know it allows ampersand, which is also a problem).
  10. z929669
    DynDOLOD Version 3.00 Alpha 59 DynDOLOD.exe - unset some problematic flags on copied base records used for dynamic LOD DynDOLOD.exe - added dynamic flag to mesh mask rules DynDOLOD.exe - added principle support for base record swapping via _SWAP.INI DynDOLOD.exe - fixed a case of not creating an overwrite for material shader added by ESP DynDOLOD.exe - fixed a case of wrongly applying mesh mask rules without VWD flag and existing LOD model DynDOLOD Resources - updated/added meshes for better compatibility DynDOLOD Resources SE - updated/added meshes/textures for better compatibility
  11. z929669
    Have you tried updating LOOT and rebooting? If you still get this, you may want to check your OS security, firewall, and AV logs.
  12. z929669
    This sounds like a winner for my own game when I finally decide to play again for real (once Requiem is fully compatible). I love a good and deep quest line. Sounds like some plugin fixes or patching may be in order though.
  13. z929669
    So the first issue of BOS breaking LOD Looks as if sheson is aware and making forthcoming changes to account for BOS
  14. z929669
    I agree and have modified the instructions likewise for the time being. We had been skipping trees from this mod originally anyway, and I assumed it was for the LOD problem.
  15. z929669
    I split the mesh LOD discussion topic from this to a new topic in the dev admin forums so taht we don't go OT here more than necessary.
  16. z929669
    we shouldn't be using the 'Trees' fix. It will break the DynDOLOD for those trees unless I create models specifically for FML. Same is true for The MA should be made aware, so I will do that. Looks like EVT LOD will also be nullified. What exactly is this fixing anyway? The AA meshes have always looked fine to me. PS: We also need to keep this in mind for any DynDOLOD Resources and mention to sheson if any are affected by this or other mesh replacers.
  17. z929669
    I will make a note about this on the FML page -- we shouldn't be using that fix. It will break the DynDOLOD for those trees.
  18. z929669
    I updated the mod page accordingly. This is user preference, but 'Autumnal' is most vanilla friendly.
  19. z929669
    Yes, I love Requiem and have been basically not playing the game until this overhaul is fully compatible with SSE. It changes SSE into a much richer and vastly more complex RPG that will add hundreds of ours to a given playthrough, IMO. I will definitely support a SSE guide around Requiem (probably would need to be unofficial though, as this completely breaks the Mandate). I'm aligned mostly with all of you on these predicted directions but don't want to spend an hour posting my own nonsense
  20. z929669
    @DoubleYou has VR I think, so he may be interested in curating a VR guide that aligns mostly with our SSE guide at some point.
  21. z929669
    Bumping this. I think we should be using both optional files. CACO Cleaned Textures - BC7 format textures instead of uncompressed DDS True Fortify Effects for Magic Skills - this make fortify magic effects consistent with other CACO fortify effects and should apply to Odin if I am interpreting that mod correctly (scales spell strength according to skill level)
  22. z929669
    But this mod has an all-in-one option that applies to Step, which should be our guide requirement anyway (all DLC CC content required). This way, it's just like USSEP and what we've been saying applies.
  23. z929669
    ... so it is written, and so it shall be done. I expect that this will be well maintained. If Garthand steps down, someone else on the USP team will probably pick it up again without delay. Krypto's patches could be more of a headache, but no more than updating each of the 20+ patches as they change (and guide instructions). I will begin doing this in the patches I'm working on and see where it goes.
  24. z929669
    In looking more closely at the changes, I agree. We may need to look at the falmer temple chandelier and solcairn meshes though. I'd say to install the loose files rather than the FOMOD Updated instructions accordingly
  25. z929669
    Agree. It's not a fix. It's an interface modification. It's also additionally an 'Extender' strictly speaking, but we have already agreed that any extender-format mod with a singular purpose that associates its impact with a given ModGroup should be placed into that ModGroup ... so again, 'Interface'.
×
×
  • Create New...

Important Information

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

  I accept