Jump to content

PRieST

Citizen
  • Posts

    212
  • Joined

  • Last visited

  • Days Won

    1

Everything posted by PRieST

  1. To 3: Hm, I had the *.json error massage, active box was greyed out (and DynDOLOD deactivated)...thought it was so, 'cause I was in a house. I meant do deactivate it manually, if it isn't already. Can't say what difference it makes, if you deactivate the esp while DynDOLOD is still active To 6: So NMM? I thought it won't make any differenes at this point To 9: We should leave this out from now on
  2. What I exactly did was: 1. Load an existing savgegame (It also was 'infected' by a bad 1.46 integration) 2. Went into a house 3. Looked up, if DynDOLOD was deactivated -> when not, deactivate it -> check 4. Saved the game 5. Closed Skyrim 6. Deactivated DynDOLOD and DynDOLOD - Output files via Mod Organizer 7. Load the game 8. Waited 2 ingame days 9. Changed the house (because a NPC remind me to leave his house oO ) -> I was outside a few seconds, but I don't think this was essential 10. Waited another 5 days 11. Saved the game again 12. Cleaned the save via Savegame script cleaner 12b. 10 unused scripts were removed from my save 13. Deleted everything of existing DynDOLOD files/scripts 14. Downloaded DynDOLOD 1.46, newest papyrus scripts from sheeson, and the functions.pas to fix the 'GLOW error' 15. Installed DynDOLOD like supposed to be (overwrite scripts and function.pas with the new ones) 16. Loaded my savegame, went outside and realised that everything worked fine That's it, this is how it worked for me.
  3. It worked!!! Did it with your latest papyrus scrips and a clean save + savegame cleaner. (probably this was my fault before, 'cause I made a mistake when I 'created' a clean save ) New Game: And my old savegame: Thanks for your patience and helping to resolve our errors ;)
  4. I'll try it tomorrow with a clean install of the mod and a savegame script cleaner. I just don't understand, why there is the error, if everything of dyndolod was deleted and a 'mod free' savegame was ready until I installed version 1.46 Don't know where my fault was, but I'll find it reasons
  5. I did it like always, but I'll try it again tomorror. Except that I can't see any differences, so I think your mod works just fine.(or do I see only static and tree lod and think it looks right?) Even a new game has the 'error', maybe only the text comes up, in fact it shouldn't?
  6. Tried a new game, still the same, except one thing: In the new game I have a new entry in mcm -> "settings" "Old Game": "New Game":
  7. Check it a few minutes ago...I habe the same error, too. I installed DynDOLOD yesterday from scratch. Nothing was left, so only 1.46 is installed and active, but ingame (mcm menu) it shows "DynDOLOD Active [x]" and in section last massages "DynDOLOD_Tamriel_Objecsts.json does not belong to DynDOLOD.esp"
  8. Yeah, that fixed it for me, too :) There are also "3DName lookup could not open" massages in DynDOLOD GLOWLOD section. Here is the log: DynDOLOD_Log
  9. Thanks for your reply...I'll try it tonight, when I'm back home from work
  10. Was my intention, too. Still the same. I tried many different solutions now, but nothing worked
  11. I always get an error massage while generating LOD with version 1.46 Pictures of the error: TES5Edit ErrorLog: And my LoadOrder (sorted by LOOT, except the last 5 ESP): I don't know what I'm doing wrong. Installed DynDOLOD from scratch, just like in your FAQ...with version 1.45 evereything worked fine. I used the new GLOW options in expert mode, but even without activating them i get the error. EDIT: These are the settings, which I used: Hope You can help.
×
×
  • Create New...

Important Information

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