Nightcaller Temple Save Bug

[Shell]

For some reason whenever I try to quicksave or make a clean save within Nightcaller Temple, my game CTD's. It doesn't happen anywhere else. I've updated all of my mods to see if that would solve the problem, but no. Still crashes. Any help or feedback would be much appreciated.

Thanks,
-Shell

[stabbykitteh]

No, it's not your mods. It's a known and apparently very common bug with the 1.8 patch.

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.

[Ashe X Falls]

+1. I had the same problem a few weeks ago, ^^^ this was the only thing that worked.

[Shell]

Thanks, I tried that and it worked. Much appreciated.

[zOmbIE]

This did not help me any, I finished the temple, left and fast-travelled to another location. When I did a manual save at the new location the game crashed again.

[zOmbIE]

Update: I found a way to bypass the problem on UESP.net:

"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

[Leaf]

stabbykitteh님이 먼저 게시:

No, it's not your mods. It's a known and apparently very common bug with the 1.8 patch.

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.

I also suggest not tabbing too as my game crushed right after I competed the mission.

[KemonoMio]

I had the same problem too,i don't quicksave and turn autosave-off while did this quest, after finished and leave nightcaller temple, i didn't have any problem anymore

[AlwaysTired]

Didn't save the entire quest...traveled to Whiterun, attempted to save there...ctd...now i get to do the whole damned quest again.. is it seriously too much to ask of Bethesda that they fix their own f*****ng bugs instead of relying on modders to do it for them?

[Pax_Rabbit]

This is caused by the Dreamstride, there is a work-around but it seems to prevent you from getting the Daedric Walker achievement.

zOmbIE already mentiond the workaround I am talking about,

zOmbIE님이 먼저 게시:

Update: I found a way to bypass the problem on UESP.net:

"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 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.

[FurryGuyJeans]

stabbykitteh님이 먼저 게시:

No, it's not your mods. It's a known and apparently very common bug with the 1.8 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.

[FurryGuyJeans]

SRK Mr^Rabbit님이 먼저 게시:

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.

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.

[Pax_Rabbit]

furryoldguyjeans님이 먼저 게시:

SRK Mr^Rabbit님이 먼저 게시:

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.

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.

Well I did say "perhaps" ;) If they do, all well and good if not then I hope an Iron meteorite crushes their offices into dust.

[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]

[stabbykitteh]

SRK Mr^Rabbit님이 먼저 게시:

If they do, all well and good if not then I hope an Iron meteorite crushes their offices into dust.

But then we'll have no Fallout 4... and all the issues that will probably come with it...

[Pax_Rabbit]

stabbykitteh님이 먼저 게시:

SRK Mr^Rabbit님이 먼저 게시:

If they do, all well and good if not then I hope an Iron meteorite crushes their offices into dust.

But then we'll have no Fallout 4... and all the issue that will come with it...

Their apparent lack of professionalism leads me to think that the Bethesda team are one of the Cowboy Developers of the software world. It would probably be better if future editions of Bethesda games were passed on to a more quality aware team.

[FurryGuyJeans]

SRK Mr^Rabbit님이 먼저 게시:

stabbykitteh님이 먼저 게시:

But then we'll have no Fallout 4... and all the issue that will come with it...

Their apparent lack of professionalism leads me to think that the Bethesda team are one of the Cowboy Developers of the software world. It would probably be better if future editions of Bethesda games were passed on to a more quality aware team.

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.