READ HERE to fix KEEP not showing on map (and other keep bugs), SHALE'S stuff not showing on the map (and other SHALE bugs), Orz bugs, Circle bugs, landsmeet bugs and most other game stopping...
#101
Posté 24 novembre 2009 - 12:07
Last night I fixed Shale, and was therefore able to use her in my party again. Only minor bugette: she always has the "quest" icon hovering above her head, and moving around with her on the map, and if you talk to her, a quest icon stays on the map wherever you spoke to her, even when you and she later move away. But as far as I'm concerned, that's MUCH better than not being able to talk to her at all without being warped to the Twilight Zone. Thanks to your help, I was able to not only play with Shale again, but play through the Thaig as well.
I also used your advice to fix Warden's Keep and was thus able to play through that before starting the final battle. So, all in all, you've given me the £10 value that EA/Bioware's ineptitude and refusal to fix bugs had lost me. Ta very much!
Only other concern: after playing through all that, I got the usual "can't connect to DA servers" message, and noticed that DA:O had decided that not only could I not sign in, but I was not connected to the internet (with no way of retrying, or telling it otherwise). Now, Outlook, Live Messenger and Internet Explorer were all running at the same time just fine, so DA:O was clearly wrong, but presumably it means next time I sign in my save games will be broken again and I'll need to go through these steps again? (This time to the "repaired Keep" instead of "beginning Keep"). Not a big deal, now I know this works I'm happy, but does show that EA/Bioware still have some work to do, especially if they expect me to buy the Return to Ostagar DLC. Not currently going to happen! Too big a chance of throwing my money away.
But, once again, thanks hugely for effectively fixing this problem, at least as well as anyone outside of EA/Bioware themselves can.
#102
Posté 24 novembre 2009 - 12:09
Almost certainly not QA at fault. The main game is basically OK, it's the DLC that is causing most of the problems, and with day zero DLC, how much time have QA got to check it?
I'd be looking at the publishers, PR, and the absolutely useless support team who have to learn that providing a public forum and ignoring all requests for actual help does NOT qualify as "support".
#103
Posté 24 novembre 2009 - 12:27
BittermanAndy wrote...
PR, and the absolutely useless support team who have to learn that providing a public forum and ignoring all requests for actual help does NOT qualify as "support".
How many times must the facts of life be spelled out in all caps? EA does all SUPPORT.
There is no official Bioware after-release support for the game itself. None. There isn't supposed to be any. This forum is hosted as a place to discuss EA's bad support, and try to fill in the gaps, but all based on User to User input.
Gorath
-
#104
Posté 24 novembre 2009 - 01:04
BittermanAndy wrote...
> If I were high up in BW, I'd seriously fire a few ppl on the QA team (unless the QA team wasn't give the time and budget to properly QA the game)
Almost certainly not QA at fault. The main game is basically OK, it's the DLC that is causing most of the problems, and with day zero DLC, how much time have QA got to check it?
I'd be looking at the publishers, PR, and the absolutely useless support team who have to learn that providing a public forum and ignoring all requests for actual help does NOT qualify as "support".
LOL even w/o DLC installed there are many, MANY game stopping bugs that people are plagued with so I'd have to disagree.
The QA team is still responsible for testing the DLC as well. I hold them at fault for both.
This one one of the best games I have ever seen - yet it's been the WORST, most buggy nightmare of a single player game release I have seen in history
#105
Posté 24 novembre 2009 - 04:10
Has anybody figured out how to add Soldier's Peak to the map? I was able to get the icon to show up by editing my save file with the toolset, but it is not selectable. Not the end of the world, but it would be nice to be able to select it when I am camped there.
#106
Posté 24 novembre 2009 - 04:48
Gorath Alpha wrote...
BittermanAndy wrote...
PR, and the absolutely useless support team who have to learn that providing a public forum and ignoring all requests for actual help does NOT qualify as "support".
How many times must the facts of life be spelled out in all caps? EA does all SUPPORT.
There is no official Bioware after-release support for the game itself. None. There isn't supposed to be any. This forum is hosted as a place to discuss EA's bad support, and try to fill in the gaps, but all based on User to User input.
Gorath
...and that contradicts what I wrote how...? What exactly did I say that was factually incorrect and needs "spelling out" to me?
In fact, if you'd actually quoted more of what I wrote, just ONE WORD before what you quoted I placed the blame firmly on the publishers. Which is EA, no? So, if you'd actually, like, read my post instead of jumping on your high horse, you might have saved yourself some time.
Of course, all that is also beside the point - I bought this game which means EA and Bioware have my money. Speaking as a customer I don't care, I could not possibly care less about who is responsible for providing after-sales support - it makes no difference to me whatsoever. Whether it be EA or Bioware is for them to argue about, all I know is, the support that is provided is shocking. Practically non-existent in fact. And saying "it's not Bioware's fault it's EA" does nothing to change that fact. Especially when I'm not picking out Bioware over EA in the first place.
#107
Posté 24 novembre 2009 - 04:59
TallBearNC wrote...
The QA team is still responsible for testing the DLC as well. I hold them at fault for both.
This one one of the best games I have ever seen - yet it's been the WORST, most buggy nightmare of a single player game release I have seen in history
You are of course entitled to your opinion but in my extensive experience in the last eight years as a professional developer, QA tend to be placed firmly at the bottom of the pile and have absolutely the least influence on when a game gets released. I absolutely guarantee to you that there were QA testers saying "but we can't release without bug 29364 getting fixed!" or whatever, and an executive decision was made to overrule that. Most likely from the publishers, who after all were presumably paying for development, and made the decision (rightly or wrongly) that paying for another 12 weeks of testing would mean that although they'd have a more stable game they'd miss Thanksgiving/Christmas and lose millions of pounds. That's what usually happens anyway.
I have to say... my first playthrough of DA:O has just reached 100 hours and (according to the game itself) covered only 50% of the game. The sheer volume of content is staggering, and every time a new release candidate was produced, the QA team had to cover all of it, on PS3, 360 and PC, including multiple PC hardware configurations, several times over in case anything gets missed... that's a LOT of man hours. So I have a lot of sympathy with the QA team.
Which, obviously, won't make anyone who's suffered a game-breaking bug (including me with this DLC!) from feeling any better, and the argument could be made that they should therefore have invested more in QA, knowing in advance the size and complexity of the game - all of that is true, I don't deny it. I just think it's a bit more complex than "it's QA's fault".
(And no, I don't work in QA, and never have! I'm a programmer.)
#108
Posté 24 novembre 2009 - 07:21
#109
Posté 24 novembre 2009 - 08:57
Ok Fine maybe it's not the QA teams fault and some exec ignored them. At this point IDC... It's still someone at the companie's fault. I've worked for game dev companies before. I know the drill, but this goes to the absurd. If I really worked for EA ( high up) I'd fire someone over this. It's a PR nightmare for BW and EA
#110
Posté 24 novembre 2009 - 09:11
My game (Collector's Edition - hardcopy) is crashing during dialogue cutscenes. Sometimes it freezes and I'm able to start Task Manager and get back into the game, skipping the problem dialogue. Unfortunately, this happens rarely - crashing is the usual response. On my thread relating to the issue, someone suggested it was my sound drivers. I'm hoping you can help me out. I'm currently stuck at huge amount of dialogue surrounding Arl Eamon's recovery and can't progress until this problem is solved.
EDIT: This problem is a recent development: it started last week (Nov. 18-19). I had no problems before then. Could it be the most recent patch, or the most recent Nvidia drivers (8600 GTS)?
Help me, Tallbear. You're my only hope.
foz
Modifié par fozfoster, 24 novembre 2009 - 09:13 .
#111
Posté 24 novembre 2009 - 09:31
#112
Posté 24 novembre 2009 - 11:23
Yes, that's absurd. They provide these user-driven forums because they can't be bothered to support the game properly, then don't like the answers the users come up with? What tosh. Besides anything else - who cares if someone cheats? It's a single player game, right? They'd only be cheating themselves... and that's up to them!
I guess we'll have to keep bumping it.
#113
Posté 25 novembre 2009 - 12:15
#114
Posté 25 novembre 2009 - 12:20
Atrenar wrote...
I was able to recover both Warden's Keep and Shale last night using these debug methods. Nice work Tall.
Has anybody figured out how to add Soldier's Peak to the map? I was able to get the icon to show up by editing my save file with the toolset, but it is not selectable. Not the end of the world, but it would be nice to be able to select it when I am camped there.
That's odd mate. I debuged the keep transporting to it via the method and when I left it appeared on my map and it's selectable. How are you launching the game? I'm playing via the .exe file and noth the DA:O launcher.
Regards.
#115
Posté 25 novembre 2009 - 01:35
#116
Posté 25 novembre 2009 - 03:13
#117
Posté 25 novembre 2009 - 04:14
Krull_ wrote...
Atrenar wrote...
I was able to recover both Warden's Keep and Shale last night using these debug methods. Nice work Tall.
Has anybody figured out how to add Soldier's Peak to the map? I was able to get the icon to show up by editing my save file with the toolset, but it is not selectable. Not the end of the world, but it would be nice to be able to select it when I am camped there.
That's odd mate. I debuged the keep transporting to it via the method and when I left it appeared on my map and it's selectable. How are you launching the game? I'm playing via the .exe file and noth the DA:O launcher.
Regards.
So, it turns out that after I finished the keep it now shows up on my map. So everything apperars to be back to normal for me.
#118
Posté 25 novembre 2009 - 05:05
#119
Posté 25 novembre 2009 - 05:05
#120
Posté 25 novembre 2009 - 05:36
Because of this post i was *finally* able to add Shale to my party - definitely a post that should be stickied... i mean, it actually *helps* people.
so cheers, mate
#121
Posté 25 novembre 2009 - 06:38
Thank you kindly and great job with this thread.
#122
Posté 25 novembre 2009 - 07:01
Thanks!
#123
Posté 25 novembre 2009 - 07:25
#124
Posté 25 novembre 2009 - 07:38
#125
Posté 25 novembre 2009 - 07:48
roperratt wrote...
Ok, I'm not stupid, I'm not a programmer, but I can troubleshoot and navigate a little bit. I can't seem to make this work. I went into bin_ship and made a sortcut of the exe file to the desktop. I changed the target name in properties; Here is the actual target name I now have: "C:\\\\Program Files (x86)\\\\Dragon Age\\\\bin_ship\\\\daorigins.exe" enabledeveloperconsole It still doesn't give me the developer console. And Wardens keep is still gone. Can anyone tell me what I am doing wrong? I have spent more time in the past week trying to fix this *#@&% bug than playing the stinking game. I am really pissed off at bioware right now.
If what you wrote about the command is correct then you have made a slight omission : the command should read [...]Dragon Age\\bin_ship\\daorigins.exe" -enabledeveloperconsole. the "-" IS important.





Retour en haut





