Jump to content

sheson

Mod Author
 View Profile  See their activity

  • Posts

    13,181

  • Joined

  • Last visited

  • Days Won

    431

 Content Type 

Everything posted by sheson

  1. sheson
    Read the first paragraph of the first post. Read the section "Required Skyrim SE and Skyrim VR". It has all the links for everything that is required, including the link to DynDOLOD Resources SE. Once you downloaded and unpacked the DynDOLOD Standalone 2.96 beta, read the ..\DynDOLOD\Quickstart.html and ..\DynDOLOD\Docs\DynDOLOD_Manual_TES5VR.html
  2. sheson
    Which DynDOLOD/TexGen version are you using?
  3. sheson
    If a presets is loaded manually (or the default preset from last run automatically) its rules and settings will be used. Rules files are only loaded when using low, medium (default), high are clicked. This will always delete the currently shown rules. Enable notice=1 in the DynDOLOD INI to see message for all rules being printed to the log message window to see the exact order of rule files being loaded. Or check the debug log after the fact. The order loading the rule files defines their order in the list. The order LODGen1, 2, 3 of rules in the files defines their "local" order in the the list. Rules for plugins are loaded in the order of the plugins. If a rule that is loaded later has the exact same mesh mask or targets the same reference form id, it will replace the already existing rule. Plugin rule files in Edit Scripts are superseded by rule files with the same name in Data\DynDOLOD\ Whatever setting does not exist in the [DynDOLOD] or [TexGen] section will simply stay as it was.
  4. sheson
    The Requirements for DynDOLOD are listed on the first post and the included manual. Read the manual Overwrite/Load orders. As it explains, refer to the install instructions of the mod.
  5. sheson
    The message says in plain English: Can not find DynDOLOD Resource SE ... Do not install DynDOLOD Resources intended for Skyrim. Read requirements for Skyrim VR (from DynDOLOD_QuickStart.html): DynDOLOD Resources SE - Make sure to use DynDOLOD Resources SE versions only with matching or higher DynDOLOD Standalone versions but never with older versions. Do not mix with DynDOLOD Resources for Skyrim. The first post has Nexus and Mega links to download DynDOLOD Resources SE.
  6. sheson
    Could be terrain underside for example. In that case it has too low quality or the height distance to 0 is to low. Use the defaults 10 for quality and 500 for the height. You can edit the z position of the reference in the DynDOLOD.esp with xEdit. E.g. 500 in the drop down is -500.
  7. sheson
    There is just so many grass placements that it takes forever. I suggest to lower grass LOD density to 33% or lower even.
  8. sheson
    The path to the INI files in the mesh mask rule is for information only. It does not need to exist. Anybody uploading presets for guides should remove the outputpath line, so the default will be used.
  9. sheson
    Read the first post what log files to upload when making posts. To see if this is LOD, open console and toggle LOD on/off. If it stays it is not LOD. If it goes away it is static object or terrain LOD. If this is LOD related, read the DynDOLOD FAQ: Game: Out of place objects / floating objects / flickering full models Especially this answer: If the problems is stuck object LOD in Whiterun after fast travel, change Distant Object Detail on the View Distance tab of the Advanced options of the games launcher from Ultra to High. Alternatively try just slightly changing the value fBlockLevel0Distance=60000 in SkyrimPrefs.ini to 57000. If this is LOD related, but not stuck object LOD, it has to be terrain LOD, as it is the only LOD type that is not disabled in the load cells. If it doesn't go away, you should be able to get a form id by clicking it with console open. Could be terrain underside for example. In that case it has too low quality or the height distance to 0 is to low.
  10. sheson
    This is a support forum and not a blog. If support is required, information needs to be provided and specific questions should be asked.
  11. sheson
    I assume "this" is supposed to mean "LOD trees show in child world" Read the DynDOLOD FAQ: Game: Tree LOD: LOD trees show in child worlds / towns A: This is a game engine limitation. A mod added trees into the same area in the parent world. Either disable that mod when generating tree LOD, or add a XESP - Enable Parent to the player reference 0x00000014 to each tree in question. Tree LOD generation skips all trees with enable parents leaving them to be done as static object or dynamic LOD which don't have the limitation. See the section 'Custom Settings For Specific Mods - Mods that add trees to the same area as child worlds' in the ..DynDOLOD\Docs\DynDOLOD_Manual.html for more information and how to use DynDOLOD rules to address the issue. Or participate in the DynDOLOD 3 Alpha test. It typically detects such trees and can handle this automatically.
  12. sheson
    Nobody knows what you mean by "have trees issues".
  13. sheson
    Log messages are printed to the message window. The content of the message window is saved to the log files when the program is closed. IF the saved log file is empty, then it is because of the OS, anti, UAC etc. preventing writing to the file. That issue needs to be fixed regardless. The log messages in the message log window can still marked, copy and pasted or at least screenshotted. Read the FAQ answer as explained in the message. A: Always install the required vanilla tree LOD Billboards, then any optional LOD Billboards for tree mods in the load order. See the 'Requirements' section in the manual.
  14. sheson
    I assume with SuperDenseMode = 8? I will have to test that to see what's up.
  15. sheson
    Good to know. It should not do that. It will be addressed.
  16. sheson
    Read the log messages. Read the manual. The error stopped the DynDOLOD generation process. DynDOLOD did not print its "completed successfully" message to the log as explained in the manual. DynDOLOD should not have saved any plugins. It should be obvious that the LOD mod is not complete and can not be used in the game and that the LOD generation process with DynDOLOD needs to be started again.
  17. sheson
    Click the "Help for this message" link as explained on the first post. It will open ..\DynDOLOD\docs\help\Exception.html It explains the obvious, that is problem reading the mentioned file and what to do about it.
  18. sheson
    What probably happened is that it stopped working after a daily Windows Defender update. As you can see from the linked posts above, Windows Defender regularly causes problems. It is almost impossible to help or provide support simply being the innocent victim of 3rd party crap ware, but here are some common sense tips: Since disabling Windows Defender lets the programs work properly it is clear that the only thing that is broken is Windows Defender. It seems Windows Defender blocks the writing of a texture. Maybe the source texture changed and its content is what triggers the false positive. If Windows Defender blocks valid programs/things add an exception. If adding exceptions doesn't work, Windows Defender is broken or the exception is not matching. Hence the suggestion to check the Windows Event log to learn what actually triggers the false positive. xEdit/TexGen did not change in several years how it uses standard OS function to read/write files. The compiler did not update in several months. In case Windows Defender flags on some random byte order in TexGenx64, test with this version. I suggest to get rid of problematic crap ware like Windows 10 or its broken tools like Windows Defender or to notify the developer so they can fix it.
  19. sheson
    One would think that such a program has a log (e.g. Windows Event log) in order to check what and why it does things in order to know what type of exception to add. Add exceptions for every program involved. Mod manager, TexGen, DynDOLOD, Texconv, LODGen etc. Add exceptions for commonly used file types, like esm, esp, esl, bsa, ba2, nif, dds etc. If such a program does not work properly, maybe remove it permanently. That is all the support I can give for third party crap ware like Windows 10 and its tools. There is nothing a simple program like TexGen/DynDOLOD/FNIS/Nemesis etc. can do about third party crap ware preventing write access. This problem/error message keeps happening since years and comes and goes with daily anti vir updates. https://www.reddit.com/r/skyrimmods/comments/pwzfig/psa_windows_defender_has_recently_started_giving/ https://www.reddit.com/r/skyrimmods/comments/pgvwz9/psa_for_those_of_you_getting_nemesis_unlimited/ https://www.reddit.com/r/skyrimmods/comments/pi19zp/skyrim_crashing_due_to_windows_defender/ https://www.reddit.com/r/skyrimmods/comments/pmbdja/nemesis_error_6002_file_1st/ https://www.reddit.com/r/skyrimmods/comments/pr2ytn/nemesis_and_fnis_have_suddnely_stopped_working/
  20. sheson
    The reasons and explanations are given in the Help for this message link. "The system cannot find the path specified typically means the OS, UAC, antivir or some other 3rd party crap ware is blocking write access to the mentioned destination path. Add an exception to whatever it is that is blocking access. Remove old files from the destination/output path, which might prevent creating the new files because they are blocked by other programs etc." The help also includes troubleshooting instructions to double check the source file and manually copying it with xEdit. It is not a bad texture or NIF. Use Copy this message to clipboard instead of posting screenshots.
  21. sheson
    Read the first post. Follow its advice what to include/upload when making posts. If you are unable to post any information and log files as explained in the first post, there is no point in participating in the alpha test or making posts without any information. SuperDenseGrass should be no problem. As long as there are message like pos 52640, 98211.38, -6864 outside cell 12, 24 center 52640, 98211.38, -6864 49152,98304 in the LODGen log something is going on. If you could generate a grass cache without SuperDenseGrass and if then those messages go away, there is something I need to look at. Grass is not considered for dynamic LOD, so the NiNode is not a direct problem. On the other hand, also try to generate without grass LOD being checked, to rule out something else being the problem.
  22. sheson
    I already did this. Many months ago, by adding "Help for this message" opening a help page which explains: "The last part of the message contains the error message from the OS. The system cannot find the path specified typically means the OS, UAC, antivir or some other 3rd party crap ware is blocking write access to the mentioned destination path. Add an exception to whatever it is that is blocking access. Remove old files from the destination/output path, which might prevent creating the new files because they are blocked by other programs etc." The OS does not tell the program a specific reason for why it was denied write access, beyond the error message returned.
  23. sheson
    No point in answering if you do not read the answers, the first post or error messages for that matter. Also, it will probably "magically" fix itself like the other two times.
  24. sheson
    Read the first post. it explains: "Click help for this message" "Copy message to clipboard" and paste as text instead of posting screenshots. Which log files to upload when making posts.
  25. sheson
    The "file in question" is the destination path that can not be written to, because the OS, UAC, anti vir, or another process blocks write access. C:\Modding\DynDOLOD\TexGen_Output\DynDOLOD-temp\textures\clutter\stockade\stockadewood01snow_n.dds DynDOLOD Resources contain LOD assets for LOD generation with DynDOLOD. TexGen generates LOD assets from full models/textures to a new and empty output folder outside of the game and mod manager folders. Hence for this error message it does not matter at all if DynDOLOD Resources are installed or not when running TexGen - if the instructions are followed correctly. I suggest to pay at least some attention to log messages and read the help file what they mean. https://dyndolod.info/Messages It seems you are trying to generate grass LOD. Something seems off with the grass cache files. Did you use the new scale setting by any chance?
×
×
  • Create New...

Important Information

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

  I accept