Forum Discussion

EA_David's avatar
EA_David
Icon for Community Admin rankCommunity Admin
11 years ago

Re: Dragon Glitches - Kaltenzahn doesnt die/ map glitch

Was your reload to before you even engaged the boss? What system are you on? If on PC, please try running the repair function, and if on console please try a full restart. 

5 Replies

  • Anonymous's avatar
    Anonymous
    11 years ago

    2 seperate reloads . One autosave was while I was fighting the dragon another at skyhold . Xbox 360 and its been pretty glitchy with graphics and voice but the gameplay has been decent . But a dragon not dieing at 0 health then fully respawning is a little crazy . Im going to fight it agian and if it does the same thing ill take a video

  • Same thing happened to me this afternoon. I was at level 16 so the battle was very hard fought and I stood alone at the end(my party was dead) and then the dragon won't die with 0 health and I have to start all over again
  • Anonymous's avatar
    Anonymous
    11 years ago

    Damn 16? That mustve been hard ha . Do the sulelevn blade quest or w/e its called . Best 2h in the game , did it agian with that and the dragonslayer axe you can buy at skyhold and it was over in almost 10min . Highland dragon was by far the easiest to do with the items . So I gues if it glitches like that your screwed and need to di it agian . Now that I think about it same thing happened to druffy in the hinterlands for some reason.

  • Anonymous's avatar
    Anonymous
    11 years ago

    I have tried to kill two difference dragons so far, both at Zero just stand there bleeding but not dieing???????????????????????????????

  • Anonymous's avatar
    Anonymous
    8 years ago

    Hi, I see that after 4 years since this topic started it's still not fixed, but EA still sells this game, so it should be supported. It's the first dragon killed and this issue happened (PC). I don't think I can say how frustrating it is. Can you deliver the fix? I suppose it should have been prepared a long time ago for a really significant bug. I can't imagine it didn't show up during testing.

    Regards,

    Agnieszka