Soulmancer

Not sure if it’s windows 11 but grass cache rarely crashes. Though it stalls and I have to force close skyrim for it to resume.

I'll be updating to 1.6.1170 soon so I'll see if the crash persists But I am using Papyrus Tweaks NG and Scripts Carefully Reworked Optimized and Tactfully Enhanced

I am a but thrown off by this? OverwriteGrassDistance=6144 OverwriteGrassFadeRange=14128 What is the logic in those numbers? With fade the recommendation in the grass config says to keep it at "at least half of the other value" ... though STEP doubles it instead? Also... ExtendGrassDistance = False Stated above that it says this should be enabled for LOD grass?

Is this reversion intentional? I don't recall seeing this in past versions where these world not forwarded for the persistent world space cell. http://icecream.me/uploads/c9d457317922354b909a694683de623e.png

Sorry. Busy as in a ton of errors. some errors once upon loading a save that prompt once then go quiet, and other errors spamming my papyrus throughout gameplay. I am going to try to go through and clean this up by either looking into or removing the mods prompting errors. Based on what I am seeing in these logs, it is far from good. papyrus logs: https://drive.google.com/file/d/152Ay58dUX7iuaQV7HKTnj3vGbFTUZwQx/view?usp=sharing https://drive.google.com/file/d/13kTSQVjS2sar8xA1sp2NvdHWlOdFqk71/view?usp=sharing

Yah, it seems to happen "mostly" when loading a saved game, after a current game is underway. Seems ok when I start skyrim and load a save. But if I say, die and reload then this crash seems quite common. I enabled papyrus logging and it is.... busy. But the last thing I am seeing in papyrus before it crashes is. " WARNING: Missing or zero refcount on (000#####) when releasing"

Even with those all disabled, still getting this same crash very frequently. Probable callstack { [0] 0x7FF737662691 (SkyrimSE.exe+902691) SkyrimScript::HandlePolicy::Func1_902560+131 [1] 0x7FF737662CE4 (SkyrimSE.exe+902CE4) SkyrimScript::HandlePolicy::Func9_902CB0+34 [2] 0x7FF737F943C8 (SkyrimSE.exe+12343C8) unk_1234360+68 [3] 0x7FF737FBFF5D (SkyrimSE.exe+125FF5D) BSScript::IVMSaveLoadInterface::Func7_125F7C0+79D [4] 0x7FF73768E23F (SkyrimSE.exe+92E23F) SkyrimVM::unk_92DAE0+75F [5] 0x7FF8226BF640 (skse64_1_5_97.dll+F640) [6] 0x5B the call stacks are always indentical... Trainwreck gives me this log. https://pastebin.com/dP0PpEAX

Foolishness on my part. They were disabled at some point, not sure why but they had somehow become reenabled… I will turn em off and see if the ctd stops. thx

Recently I have started experiencing a very frequent crash on a new game that occurs when leaving an indoor area. I don't recall ever seeing a log like this before. May be worth noting that I upgraded to 1.6.1130 then downgraded to 1.5.97 with best of both worlds. https://pastebin.com/stuPBPBu I have five more just like this within 5 hours of starting a new game, this log means nothing to me in the probable object/callstack. Thx

Since updating to 163 I've been getting this error. http://icecream.me/uploads/31f3595963c16ccfa1b27a011985eea2.png Haven't encountered it on 162 or prior. This is the texture: https://drive.google.com/file/d/1vbiZ7F1EO1s0qqXS0VvQk1NdapLqUiKh/view?usp=sharing This is the log: https://drive.google.com/file/d/1Yd9k0X0IF4znWwCRxd3i-5bnTMqNfq9m/view?usp=sharing I tried running it through Cathedral Asset Optimizer but it did not process/modify the texture.

I thought the issue with SSE engine fixes was mostly due to the Steam API and broken DRM. And that the 11% mismatch with the address library was mostly was mainly UI, control map and console.

That’s disconcerting… If a mod is crashy will it generally do this quickly at either the main menu or early in gameplay? I ve about 100 skse mods and just doing some basic testing on a portable profile for 1.6.1130 and skse mods.

Not sure why but this mod will crash on 1.6.1130.

Might be a dumb question, but checking the log I am seeing. Perhaps I am looking at the wrong message / log to see if the workaround was successful or failed. Large reference bugs workarounds: enabled (DynDOLOD.DLL: NG, Scripts: NG, Deleted references: no) But when dyndolod completes it does note. Error: Deleted reference Gabby.esp [REFR:0003BF63] (places TreePineShrub02Snow [TREE:0009DAA1] in GRUP Cell Temporary Children of [CELL:00009352] (in Tamriel "Skyrim" [WRLD:0000003C] at -1,18))

How does that retroactively impact/effect a mod that I released in 2021 which included those assets when permissions were still open?

I was curious if the Just Ice permissions had changed during or after 2021? I was certain these were open or at least more lenient in the past. Checking now though it says textures may not be used under any circumstances? Edit: Apparently so. I pulled up an older cache of the nexus page and permissions used to be "You may use assets without asking if credit is given" to "You may not use these under any circumstances" currently... I had already included these assets in a mod I put together back in 2021 when the permissions were open based on credit so not sure what I should do now? When were permissions locked down.

Oddly enough when using the more informative console I cannot click select the tent at all until dyndolod initiates. I can click on and get data from literally everything else behind the tent, but cycling through with the mouse wheel never prompts the tent. Once dyndolod initializes and the tent gets the inconsistent snow shader applied I can get a console click on it NP https://imgur.com/a/6mkVO9q edit: sorry, it appears I fixed the issue and likely due to me not following update instructions? I updated dyndolod and just loaded a save at the tent. I can fix it by either setting dyndolod to inactive in the MCM and re-activating it... or simply loading the save in the abandoned prison... then after choosing the camping start I don't experience the issue when dyndolod initializes. In the future you recommend deactivating the plugins and saving the game... isn't that ill advised?

Hello, I am experiencing something weird. As soon as I load my save, once Dyndolod has initialized, it changes the tent added by alternate start - live another life "Camping in the woods" start. The tent looks fine after immediately loading the save, but then Dyndolod seems to turn it into this. I am using the latest alpha. I have attached logs below the screen shot. https://drive.google.com/file/d/1EuH6eTUmbvkWawb8q_kz4UQ7QmaIStGp/view?usp=share_link

Hello, I appear to be encountering issues with the Sovngarde Braziers due to Dyndolod 3.0 106 and ELFX? https://cdn.discordapp.com/attachments/710269640005386240/1053493918290956299/20221216175217_1.jpg The settings I am using are these; oddly enough I don't even have FXGlow or Candles enabled for lod... maybe fake lights in child worlds? http://icecream.me/uploads/d340e67e4b8c781dfc1642c8aab5029d.png

Hello, I noticed as of a recent update running texgen generates a white / blank diffuse for the mountainslabHQlod.dds ... although the normal texture is fine. In a prior build the diffuse looked as though it was generated from my mountainslab

Hi Sheson, I do know this. But up until recently the mountainslabHQlod.dds was never generated by TexGen. A recent update seems to have changed that and just curious if this has any bearing on your quote above. The generated mountainslabHQlod.dds will also override/override the mountainslabHQlod.dds included in the Majestic Mountain Dyndolod 3.0 package as it creates itself based on whatever mountainslab01 or 02 texture you have installed.

Hello, I notice Texgen now creates a mountainslabHQlod.dds and matching normal based on your mountainslab texture. With Majestic Mountains though it has an abundance of LOD specific textures beyond mountainslabHQlod.dds ... will this create miss matching if I am using an MM texture replacer without full lod support built into it?

is there another solution?

This is weird. I just updated to Happy Little Trees 3D LOD - Quality 2.02 to match the new Happy Trees 2.02 ... Previously I was using the performance LOD version for older Happy Trees 1.0+ and didn't encounter this issue. My pine trees haven't turned out properly; they appear to be partially invisible? Not something I ever encountered with the previous version performance mode. https://imgur.com/a/yi4OrFl These are my options when I created the texgen and dyndolod http://icecream.me/uploads/f9acf4671faad3bd802512c8aca88480.png http://icecream.me/uploads/3717d70a991d61aa1647c61cd740adbf.png EDIT: I tried the performance version and didn't experience the same issue; only seems to happen with the quality version.

Yah, I find the issue with almost all mountain mods is that they don't include any textures for LODs. and sounds like not installing the MM LOD pack will do nothing to correct the lack of textures, and end up without the meshes I need instead. So I guess any texture replacer for Majestic Mountains, will just end up with the MM LOD textures. I am just using the mountainslabhqlod_n.dds from MM lod pack as well. The MM texture replacer I use is Northfire OG which doesn't have LOD texture support. How much do you think setting LOD4 for mountains to "full" annihilate performance?