sirjesto
-
Posts
466 -
Joined
-
Last visited
-
Days Won
10
Everything posted by sirjesto
-
Yeah I am getting it on the .esm Ok, yeah me too. -
I thought it was just me. I wonder if this is only happening to a few of us? Are you guys using MO2?
-
Updated from 2.44/2.50 to 2.45/2.52 today. Can't quit the program without killing the process...just keeps saying failed to create .esm and making a 0k backup file over and over.
-
Yeah I hadn't looked at videos about MO installation for a few years, but one of the first ones I looked at installed it in the skyrim directory. It was from a year ago. The "latest" one that I watched was from March of this year and it didn't show to install it in the Skyrim directory, so yeah there is a lot of conflicting information out there.
-
Just for a little insight on why this happens. When you sleep the 2nd time, you are actually travelling to a different cell when you wake up. Some follower seem to have a problem with trying to follow you this way and that seems to crash the game. By the way, what follower was it?
-
I agree.
-
Which do you like better?
-
The CTD's from the newest version are due to bad facegen files. If you delete those (and re-generate them), the CTD will be fixed.
-
Using SKEE with XPMSSE v4.32 has been known to cause this crash. Downgrading to v4.20 or not using SKEE should prevent this. There is plenty of discussion about this on the "Engine fixes" mods comment page.
-
Well, Papyrus Logs aren't crash logs. They can sometimes help, but that's not actually what they are for.
-
I.....Have never seen anything like that...........
-
Wow, nice. I was using v2.36 so that is why I wasn't crashing.
-
To be clear, if it was a bad texture or mesh, the crash would happen all the time and instantly in the cell. It wouldn't be just sometimes when entering or exiting a building. That is something else completely. I just did a test entering and exiting 8 buildings in Riften myself for kicks and had no issues.
-
Hmm nifscan had a problem reading these textures: Not sure if that has anything to do with anything though. Also, the issue isn't with DynDOLOD at all.
-
Well, I don't use the guide so I didn't know that. :P I use "HIGH" for the optional texture resolution. Original foam, smoother rivers, I do use the sound extended ambiance. I use the Water color option. The issue would be from a bad mesh, so maybe I'll do a scan on the meshes in the newest RWT and see if I find something.
-
Might be a good idea to mention it to the guys at RWT as well, right. EDIT: Also, I use this new version of RWT and don't experience crashing. It is likely you have selected an option I didn't in the installer. EDIT2: Actually, I didn't download v1.5.3 because I didn't use the option that it says was updated. So maybe something about that option is the issue. Either way, the issue is probably with an option that isn't just the default stuff.
-
There is an ITM that needs to be cleaned from the Moon and Star Immersion patch. If this ITM isn't cleaned and you load the Immersion patch AFTER the Legacy MaS patch, you will break the Legacy MaS compatibility. If you load the Immersion patch BEFORE legacy's MaS patch however, you should be fine regardless if you clean it or not. Either way, it's best you clean the ITM and load the immersion patch BEFORE Legacy's MaS patch (or in this case, the LOTD Patches Merged file).
-
512 should be totally fine and wouldn't be causing this issue unless you have a complete potato for a PC. Also, DynDOLOD wouldn't cause CTD's when entering buildings. It might be causing CTD's when leaving them however. BUT, I still think it is the fault of an asset or assets from another mod.
-
Well, removing mods and running DynDLOD wouldn't be a good way to do it, no. Probably best to do Texture/Mesh scans with various tools on mods that you suspect could contain the bad assets.
-
It's probably not Dyndolod, but bad assets in one of your mods that Dyndolod is using.
-
damned if I know, I don't use it. All I'm saying is, they don't remove mods from the Nexus for being skimpy, so it's stolen assets or mod ported without permission. It kind of has to be if you just think about it logically, which is what I'm good at.
-
Yeah I doubt that's the reason. More likely stolen assets.
-
Immersive Creatures extra spawns were 100% causing CTD's for me. I'm quite the geek modder and I never crash, so when I do, it weirds me out, lol. Anyways, didn't take too long for me to find out it was SIC. I never wanted to use SIC in my game to begin with and only added it to my list for the 2 artifacts in the Museum. So I basically just disabled everything to do with random or extra spawns in the MCM. No more crashes and I still get the artifacts.
-
The funny thing is, it doesn't always happen. On my last test playthrough, before the latest update. I used the High Res Textures and accidentally took my follower on the quest and didn't CTD. BUT, it was a standalone follower (Inigo) and not a vanilla follower, so I'm not sure.
-
Then In the future, I would remember to not have a follower when speaking to the priest and starting the quest.
