Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
disable ELFX and test it out - we cant do it for you.
Blackreach isn't currently my concern. I've disabled ELFX to see if it was the cause of the Mzulft crash, CTD still occurred. ELFX is not my problem at the moment
Meaning? as far as i know mzulft doesn't lead to blackreach. If the crashes are connected i have no idea how. Which is why i've posted my logs and minidump files in the hopes someone would be willing to help.
The fact i've tested ELFX and reported back that the crash still occurs i believe rules it out as the cause.
Also I dont recall if it is possible to issue a killall console command to a zone you havent entered, but if you kill everyone in the area before zoning in you might be able to see if it is a problem with one specific enemy or character thats causing the crash.
If its not an NPC then it could be a problem with a mesh. You can rename the meshes folder temporarily so the game uses the default meshes then try entering the zone. If the game doesnt crash then you have to find the model causing the crash.
thanks for the advice, after a whole lotta trouble shooting, turns out aMidianborne of all things was the cause. I am now able to enter dwarven ruins as normal.
Though now i'm having trouble loading the saves of my playthrough, even when i restored my previous loadorder. so i guess i have a lot more troubleshooting to go.
Also, looking at your modlist on Reddit, not sure if that's your load order or just a random list of the mods your using, but if its your load order it definately needs sorting.
For whatever reason modwatch has it completely out of order. I've sorted it with LOOT in my actual mod organizer.
As for what you said about amidianborne, i thought exactly the same thing. But it all worked fine after i disabled the book of silence mods. What this leads me to think is that since dwemer ruins are already texture resource intensive, all my texture mods simply overloaded skyrim into having a meltdown whenever i entered any dwemer ruins. Which is strange considering i'm getting a solid 40+ fps anywhere else in the game.
But, the game is all smooth as butter now. If someone had the knowledge to understand the minidump better than I, maybe they would have a better idea of what exactly was happening.
Looking through the book of silence, it did include the differentlyebony.esp and AMBglassvariants.esp. Still would be weird if those were causing issues, but i'm not sure what it could be.
I think your right about the overloading, however Amidianborn is only 2k textures so doesn't have much of an impact. If you're using any 4k textures, dump them and change to 2k, 4k textures are total overkill. There is only so much you can add into the game before it overloads and either crashes to desktop or freezes up.
Also, have you got SKSE with the SKSE ini installed. Also ENBboost will help alot with memory issues. These are essential in Oldrim, don't know if they are the same in SE but its worth looking into.
You dont need SKSE or ENB anymore regarding memory stuff because SSE is already 64bit and can use all the memory it wants. The real limiting factor is his GPU's VRAM. Given that he has a GTX1060, he has either 3GB or 6GB.
In "Oldrim" it was the memory lack, the game was using all the available RAM and eventually crash. But in SE, the most "popular" reason for CTDs are the meshes. If you used several meshes besides the classic mods' (like SMIM), then you need to disable several of those mods and re-test.
It's a VERY HARD work to do, to track the guilty mesh mod, so personally most of the time I'm simply re-starting (modding) from scratch, its less work than to find that guilty mod.
I've already went this route before, completely restarting a couple times. I delved too much time into my current playthrough to completely start over, so i went mod by mod enabling until it crashed, then enabled everything else but the culprit mod.
i do have SMIM installed, my amidianborne textures are 2k, and i still have no idea why disabling a texture mod saved my game from the CTD. my graphics card has 6gb of vram, so i would hope it wouldn't have too many issues loading textures.
I'm beyond the... 100th time of re-installing all from scratch!
I know it. i've been modding skyrim since it's PC release, every hour spent in game is matched by the time i've spent modding it. I couldn't count how many times i've redone a skyrim install. 'a couple times' refers to my attempts with special edition in the past couple weeks. Most of my experience is with oldrim