Vigilance Bug
#26
Posté 21 mars 2010 - 10:13
http://dragonage.wik.../Vigilance#Bugs
also look at the gallery. the reason why i care about the bug is the way Vigilance looks like normal
#27
Posté 22 mars 2010 - 02:05
Tsuzo wrote...
Zevais go here it will explain the bug:
http://dragonage.wik.../Vigilance#Bugs
also look at the gallery. the reason why i care about the bug is the way Vigilance looks like normal
It sounds like a Warden's Keep issue. If you have WK, you are screwed. Appearantly, other Awakening items such as the Sentinel armor will resemble WK items like Warden Commander armor. I wish I never bought Warden's Keep now. I am not going to delete at this point. Lord knows the glitches that would result from playing it through with multiple characters that I plan to use in Awakening.
My Awakenings should arrive in the mail tomorrrow. Hopefully, I don't suffer this bug on my PS3.
#28
Posté 22 mars 2010 - 02:29
the Sentinel Helm is unaffected because the Warden Commander Armor set lacks a helm.
if you get to the point where you are gonna craft Vigilance you must craft a Grandmaster Fame Rune yourself as an ingredient.
#29
Posté 22 mars 2010 - 02:54
#30
Posté 22 mars 2010 - 03:07
#31
Posté 22 mars 2010 - 03:14
#32
Posté 22 mars 2010 - 05:29
#33
Posté 22 mars 2010 - 05:36
#34
Posté 22 mars 2010 - 05:39
#35
Posté 22 mars 2010 - 06:23
It's a console only bug. If Warden's Keep DLC is present, Sentinel armor looks like Warden's Commander armor on human characters.KigenBarzhad wrote...
Sorry but what is the sentinel armor bug?
#36
Posté 22 mars 2010 - 06:24
Thats a pretty good theory, I was thinking this as well.Tsuzo wrote...
this is just speculation but i have a theory maybe it was intentionally done because people were complaining about Starfang and Warden Commander Armor not being transferred over and they decided to do this.
#37
Posté 22 mars 2010 - 01:18
#38
Posté 22 mars 2010 - 05:03
KigenBarzhad wrote...
I've fixed this issue for PC users. Check http://social.biowar...m/project/2310/
Kigen, it says it disables all Warden's Keep textures. What does that mean for the actual Warden Commander armour? What will happen if I'm using it in Awakening?
EDIT: Never mind, i was looking at the wrong link. Cheers bud!
Modifié par JaegerBane, 22 mars 2010 - 05:14 .
#39
Posté 22 mars 2010 - 05:05
That's tin foil hate nonsense.Tsuzo wrote...
this is just speculation but i have a theory maybe it was intentionally done because people were complaining about Starfang and Warden Commander Armor not being transferred over and they decided to do this.
It was a clear oversight
#40
Posté 22 mars 2010 - 05:15
Mad Method wrote...
Already have a half-assed solution here. Just read the part saying "About Warden's Keep."JaegerBane wrote...
I hope the modders fix this.
Cheers, but I wasn't too keen on disabling the WK textures. The Warden Commander armour is pretty much the best armour there is for a balanced AW, so I'm still using it, and I don't want the textures killed
#41
Posté 22 mars 2010 - 05:26
#42
Posté 22 mars 2010 - 06:08
#43
Posté 22 mars 2010 - 07:52
#44
Posté 22 mars 2010 - 07:59
KigenBarzhad wrote...
sorry I wasnt very descriptive. the patch goes in your \\\\\\\\Documents\\\\\\\\Bioware\\\\\\\\Dragon Age\\\\\\\\packages\\\\\\\\core folder
Yeah, no problem, you already answered me on the nexus, I'm under a different name over there and I posted on both to maximise reponse potential
Cheers for the fix!
#45
Posté 22 mars 2010 - 08:00
Tsuzo wrote...
Haexpane, its a mere speculation. i'm leaning sort of towards an oversight like you are. but it's a slight possibility. since how can this bug gotten through testing? i mean it is such an obvious glitch that it should have been fixed early on.
The fact of the matter is it's a conflicting 2da that's causing the issue. You wouldn't normally create a conflict if you were intentionally trying to get a texture to display. You'd just duplicate the texture and override it.
#46
Posté 22 mars 2010 - 08:32
Tsuzo wrote...
Haexpane, its a mere speculation. i'm leaning sort of towards an oversight like you are. but it's a slight possibility. since how can this bug gotten through testing? i mean it is such an obvious glitch that it should have been fixed early on.
If you've ever worked in software development, you'd know how it got through... one of a million ways.
Testing is only as good as the executor, script writer, QA lead, QA manager, QA director, QA test plan etc... there are many possible craks to fall through.
Sometimes it's as simple as "we tested on dev kits, not consumer kits" or there was a last minute bug fix and they did not re-execute all the scripts.
To say that it was done intentionally, is actually accusing them of consumer fraud
#47
Posté 22 mars 2010 - 09:07
#48
Posté 23 mars 2010 - 12:01
Kinda like the many other bugs/glitches that are obvious,. Apparently by your statement, it fell through the cracks while in development. Seriously, how in the hell can so many obvious issues be missed then?Haexpane wrote...
Tsuzo wrote...
Haexpane, its a mere speculation. i'm leaning sort of towards an oversight like you are. but it's a slight possibility. since how can this bug gotten through testing? i mean it is such an obvious glitch that it should have been fixed early on.
If you've ever worked in software development, you'd know how it got through... one of a million ways.
Testing is only as good as the executor, script writer, QA lead, QA manager, QA director, QA test plan etc... there are many possible craks to fall through.
Sometimes it's as simple as "we tested on dev kits, not consumer kits" or there was a last minute bug fix and they did not re-execute all the scripts.
To say that it was done intentionally, is actually accusing them of consumer fraud
Why so many?
#49
Posté 10 avril 2010 - 09:06
#50
Posté 24 avril 2010 - 03:01





Retour en haut






