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
I just e-mailed Bethsoft Support about this (essentially the same content as my post here), so I'll see what they say. I'll post their reply.
EDIT — I also verified the cache. The problem persists.
I looked up 'Trouble In Skyrim' on UESP to get its code (CR05), and then the appropriate commands for the 'Console' ('getstage' and 'setstage'). Even though the quest is still listed in the 'Journal' as complete (with a hollow diamond next to 'Talk to Farkas', and Farkas nowhere to be found), the 'Console' response to 'getstage CR05' was: GetStage CR05 1.00. I still don't know how that occurred.
Holding my breath and hoping, realizing that my game was broken and I risked breaking it even more, I entered:
setstage CR05 20
When I went back into the game and went to the Journal, I now had two entries for 'Trouble In Skyrim', one broken and one operating normally. I found Farkas, who rewarded me for completing my quest, then directed me to Skjor for the next one.
With any luck, this solved my problem and didn't create any new ones. We'll see.
I don't like unsolved problems, so I decided to post the results of what I did regardless of the result. Fortunately, it seems to be fixed now. If anyone has any suggestions or cautions about what I did and wants to warn me about what may yet go wrong as the result, please do so!