Steam telepítése
belépés
|
nyelv
简体中文 (egyszerűsített kínai)
繁體中文 (hagyományos kínai)
日本語 (japán)
한국어 (koreai)
ไทย (thai)
Български (bolgár)
Čeština (cseh)
Dansk (dán)
Deutsch (német)
English (angol)
Español - España (spanyolországi spanyol)
Español - Latinoamérica (latin-amerikai spanyol)
Ελληνικά (görög)
Français (francia)
Italiano (olasz)
Bahasa Indonesia (indonéz)
Nederlands (holland)
Norsk (norvég)
Polski (lengyel)
Português (portugáliai portugál)
Português - Brasil (brazíliai portugál)
Română (román)
Русский (orosz)
Suomi (finn)
Svenska (svéd)
Türkçe (török)
Tiếng Việt (vietnámi)
Українська (ukrán)
Fordítási probléma jelentése
You can still do the quest but you have to turn autosave off. Don't try to save from the time you drink the torpor until you exit Nightcaller Temple. Upon exiting the temple it will be ok to save.
There are some other tricks listed on UESP but I find it's easiest to just avoid saving.
"As the bug originates during the Dreamstride, use the console command tcl, cross through the barrier, and remove the soul gem. Since the quest progress is scripted through the status of the soul gem, this will progress the quest just as if you had used the Dreamstride. The only impact it will cause on the game is that there will be no enemies except one orc in the dining room, Torek and Veren."
Source: http://www.uesp.net/wiki/Skyrim:Waking_Nightmare#Bugs
I also suggest not tabbing too as my game crushed right after I competed the mission.
zOmbIE already mentiond the workaround I am talking about,
I agee with the sentiments of usfjerry wrt Bethesda's apparent lack of motivation to fix this bug. Perhaps now that Dragonborn has been released they will fix it in the next patch.
While that is not encouraging news, it is good to know. There have been a number of times I have saved the game and immediately CTDed. I was getting really aggravated it was so random and therefore unpredictable.
Nice to know it is a known bug, less nice that it isn't fixed yet.
I expect pigs to do aerial acrobatics before Bethesda squashes this bug. Maybe my perception is wrong, but Bethesda seems quite content for most problems to let the fan community fix the bugs before they bestir themselves to do the job.
[EDIT]Or their chief person responsible for deciding what does and does not get fixed gets just deserts - I am personally half inclined to not buy another Bethesda product in protest at their shoddy quality assurance measures.
This was a bug introduced into the game in an update, it was not there in the original release.[/edit]
If you want a true lack of professionalism evidenced by utter avoidance of customer complaints, then you get left with Microsoft. Bethesda is nothing like MS in that respect.
Mind you, not every customer complaint of problematic software ends up actually being a real problem with said software. Most complaints of buggy software is really a user error situation. It takes time for a company to definitively say that a bug is actually a bug, and even more time to discover what is the cause with even more time used to quash the offending bug.