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
Alternatively, do what I suggested in your previous post and disable half your load order at a time. Instead of loading your current saves, press the ~ key from the main menu and type in the follower:
coc HonningbrewMeaderyExterior01
Now, walk towards Riverwood. If you get a crash, the issue is in one of the mods still enabled. If they vanish, then its in one of the ones you disabled. Run the test again, but with only half the mods from the group with the problem mod enabled. Do this over and over and you should find the problem. This shouldn't take long at all to do with your short load order.
On the other hand, it may be a compatibility error. In which case, the above method may not work. You could alternatively disable each mod one at a time, and run each test with all of them enabled. If you get a crash, then the mod you disabled can't be responsible. This may seem tedious, but with your short load order it shouldn't really take that long. Besides, assuming the crashes happen reliably around Riverwood, each test shouldn't take you long. If you want to speed things up, you could just teleport yourself directly to Riverwood with the following command:
coc Riverwood
I wouldn't do that though, since doing this may allow you to go to Riverwood without crashing (the issue could be caused by you crossing specific cell borders, thus teleporting would prevent the crash from happening). On a side note, do you get a crash if you try to fast travel to Riverwood? If so, can you fast travel to other places?
Did you never try that NVAC mod I suggested? That thing works miracles, and I'm far from the only witness to this.
coc HonningbrewMeaderyExterior01"
How do you do that without loading a save if it teleports you?
you can't teleport without loading the save
Uh huh, then explain why I do it all the time? In fact, I've been doing it over the past few minutes trying to get a mod to work. Anyone can try it themselves and see that it works.
Back on topic, if NVAC isn't working, then you have to test your mods using one of the two methods I suggested to find the problem. That's something mod users have to do all the time. As stated, you can use console commands from the main menu to skip the intro sequence. I chose the specific location I recommended in my last post because its not that far from Riverwood. If you want to get there a bit faster though, you can use the console command:
player.setav speedmult 200
This will double your movement speed. You can increase the number to go even faster (base speed is 100, so 300 is triple speed, 400 is 4x speed, etc...). Note that you'll have to sprint before the speed change will apply.
And XPMSE? Does it win all conflicts against other mods?
I am not talking about load order, but resource priorities. I asked about the mod manager.
- If you are using NMM, then XPMSE needs to be installed last and telling "Yes to All."
- If you are using Vortex or MO2, XPMSE should be last file in mod priority list, so that it's skeleton will win all other conflicts.
This might not be your problem, but it sounds like it could be. Best to make sure that this isn't the case.
I didn't say that XPMSE was the problem itself. It is usually the solution. I was after a chance that old obsolete skeleton file from another mod could be winning conflicts against it and that could have caused your issues.
Have you previously uninstalled scripted mods from this game and does the crashing happen with a new game?
With me that happened with some incompatibility issues between mesh improvements and flora improvements. No idea why, i made sure they were separate mods changing different things. But as usual, you can't trust most mod descriptions.
Load order and resource priority basics by Ilja
http://steamcommunity.com/app/72850/discussions/0/523890681419356033/
(from pinned topic Helpful Links and References, Section 3, Tools, Load Order, and Mod Cleaning)
Doing so should also correct the fact that the DLCs are in the wrong order - it should be:
Dawnguard
Hearthfire
Dragonborn
Also, since you have the HighRes Texture Pack installed, you should also install the Unofficial High Resolution Patch by Unofficial Patch Project Team - http://www.nexusmods.com/skyrim/mods/31255/?
Your initial load order should therefore be:
Skyrim.esm
Update.esm
Dawnguard.esm
Hearthfires.esm
Dragonborn.esm
Unofficial Skyrim Legendary Edition Patch.esp
[Your other ESM files]
HighResTexturePack01.esp
HighResTexturePack02.esp
HighResTexturePack03.esp
Unofficial High Resolution Patch.esp
[The rest of your mods]
Does this crash happen persistently in same spot, or in same distance from Riverwood, if you approach it from another direction?
Got some sleep, some coffee and short day at work: now my brains are somewhat functioning again.
If you can approach the area from another direction without crash, then issue is most likely related to scripts. Something gets tangled, or fails to load due to Papyrus spam. Game might be fine after that has been dealt with, but that is of course still a worrying sign.
If the game persistently crashes on same distance from target, despite where you are coming from, then the issue is very likely related to broken or corrupted mesh. It may also be a mistake from mod author part, which no one had noticed before. I have dealt with few of those in past and helped mod authors to isolate the problem. Mod might be new, or just recently updated. Mesh isn't applied correctly and it crashes the game when it begins to load. Even SMIM once had one of these cases and game persistently crashed on same spot behind Whiterun.