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
"The dragon sometimes doesn't spawn correctly. This causes the compass to point towards Markarth with the map pointing to the "correct" location. If you follow the marker into Markarth, it changes to the bold arrow and points toward the correct location, thus insisting your objective can be reached from inside Markarth.
Try console commands "prid 32AC2" and "moveto player" to have the dragon appear. You can confirm the correct id by checking the quest variables.
You can also skip the quest by using the console command "setstage BQ04 100", or "setstage FreeformSkyHavenTempleB 100"."
Thanks. This worked!
They are cascading failures that will come to a head, and roll over like a wave crest and crash.
If this error appears in every new game, you have a serious problem, either with mods, or "cleaned masters", or some other wild edit someone on the internet suggested you make.
If after looking on the wiki to see if the problem is a known bug, you do not see it listed, then the problem is a mod issue, and must be dealt with by troubleshooting your mod build.
Wiki describes it as a "known bug". Which means lots and lots of other people experience it. I don't have a "serious problem" with my game.
Ilja:
"....Skyrim bakes script data to save file. There is no such thing as a clean save, when mod is removed. "Clean save" is for mod updates only. This includes work done with Save Script Cleaner. That tool cleans obsolete entries and orphaned scripts from the game, but script data will remain in the save file, causing Papryus to constantly check it and creating errors.
http://steamcommunity.com/app/72850/discussions/0/343788552537617802/#c343788552538346202
Also:
http://steamcommunity.com/app/72850/discussions/0/365163686057140233/?tscn=1504123538#c365163686058904424
And, again from Ilja:
"I believe that misunderstanding here is that people can not make a difference between closing active scripts from the game world and wiping Papyrus script data from Papyrus. Latter is impossible to make in a clean way."
https://steamcommunity.com/app/72850/discussions/0/1495615865205745360/?tscn=1529568370#c1696043263497229374
You will need to start a new game. When you do is up to you to decide. When you do so, however, make sure that you thoroughly check your mod load for compatibility issues and for unstable mods.
In fact, when you do eventually start a new game, you may wish to post your LOOT sorted load order in the forum as a discussion, so that people can examine it for issues.