EddyTeddy Posted November 22, 2011 Posted November 22, 2011 Hey! It's my first post on this forum, but I'll try to make it good. I have put over 40 hours of gameplay on Skyrim now. Loving the game so much, one of the best games out. But I ran into a real game breaker. After finishing most of the Companions quests, I ran into a quest called "Purity". In the quest, you have to help Vilkas to clean his "Beast blood", which allows him to turn into a werewolf. (At this point, I also have beasts blood). So, I started the quest, because I want to get rid of the blood too. When starting the quest, I was told to take Vilkas to the tomb where you can burn the witches heads. So I fast travel there, and Vilkas is nowhere to be seen. I go back to the Jorvaskr and he's there, enjoying his meat. I talk to him and he gives me the same quest. I fast travel to the tomb once again, and he is still nowhere to be seen. Now I get pissed at this guy. I go back to Jorvaskr and he is there still sitting and eating. Now he doesn't give me a quest, and I have two finished quests in my quests list. And I also can't get a follower. Everybody says that I already have somebody, but I don't. I tried waiting, fast travelling and everything really, and I have no follower. I can't get anybody to follow me and even worse, I can't get rid of the beast blood. I'm at the point in the game, where loading an older save is not an option, have done waaaay too many things after that. Any help would be very appriciated.
EddyTeddy Posted November 22, 2011 Author Posted November 22, 2011 Try waiting 24 hrs after Fast Travel yet ?I tried everything. Waited for 100+ hours in total.
cyox Posted November 23, 2011 Posted November 23, 2011 I'm in the exact same boat. like 30 hours of playtime since then so no possible hope of going back. I've looked everywhere i could think of to try to find an answer and haven't had any luck. i played most of the game fine without it but now there's several quests i can't complete because of this issue. i noticed on the skyrim forums they had it listed in the known bug issues so maybe hope for a fix for the issue in the patch. none of the normal companion summon stuff works because it's not tied to someone you hired. and i know theres a few quests than can momentarily cause this issue when they go "wait for you" at a dungeon for a quest but i completed cleared my quest log and it didn't make any difference either. i even tried killing everyone in Jorrvaskr to no avail. i don't understand why they dont just give you the option to remove your old follower when you inquire into a new one.
EddyTeddy Posted November 23, 2011 Author Posted November 23, 2011 I'm in the exact same boat. like 30 hours of playtime since then so no possible hope of going back. I've looked everywhere i could think of to try to find an answer and haven't had any luck. i played most of the game fine without it but now there's several quests i can't complete because of this issue. i noticed on the skyrim forums they had it listed in the known bug issues so maybe hope for a fix for the issue in the patch. none of the normal companion summon stuff works because it's not tied to someone you hired. and i know theres a few quests than can momentarily cause this issue when they go "wait for you" at a dungeon for a quest but i completed cleared my quest log and it didn't make any difference either. i even tried killing everyone in Jorrvaskr to no avail. i don't understand why they dont just give you the option to remove your old follower when you inquire into a new one.This friggin' sucks. Waiting for a mod to come out, that would add that feature.
BGatot Posted November 24, 2011 Posted November 24, 2011 I can attest that sometimes followers / NPC's supposed action did not trigger as they're supposed to. The only solution I can find on this problem was to reload from a save before the intended event and try again. I know, that sucks! Sorry I didn't have a better answer for you...
cyox Posted November 24, 2011 Posted November 24, 2011 I'm just worried its not going to get addressed because it seems to be a pretty isolated bug. Hopefully someone can figure it out.
Recommended Posts