1370 réponses à ce sujet

[Koralis]

didymos1120 wrote...

Koralis wrote...
If they don't know what to fix for wierd crashes, and they can easily fix plot flags, then they should be fixing all the plot flags.  Siting on your hands and shrugging isn't a good use of time.

Umm, not what I said. I said they won't put out a patch for plot flags and the like while they're trying to figure out the cause of the crashes. 

A single developer can deal with the easy problems while others spin their wheels and try to figure out problems that they couldn't figure out before.  (ie.  probably hopeless.)

 That's rather different than sitting around shrugging.  It is possible to hunt for and do testing to reveal the source of bugs you don't yet know how to fix.  And for all you or I know, they are fixing plot flags and such in the meantime.  That doesn't mean they're gonna release another patch for that stuff. 

And again... WHY NOT?   Why leave bugs untreated jsut because there are "more important" bugs still to fix?  Why aren't they fixing the ones that they can?  Because they don't want to be accused of ignoring the important ones?  Good job Bioware... instead people will jst accuse you of ignoring all of the bugs.

 Sure, just fixes for plot flags would probably be fine, but what about other, somewhat lower-level stuff?  Might make the crashing worse, and ****** people off even further. Or ****** additional people off who up to now weren't getting a ton of crashes. 

Plot flags have nothing to do with crashing whatsoever.  I myself am pretty pissed off... I just lost a game that I was enjoying  to the lost-inventory bug.

Modifié par Koralis, 04 mai 2010 - 08:28 .

[Nathan Willis]

Hello all,



First, I wanted to take a moment to say that we're very sorry to hear that some of you are having issues with our game. We're aware of the issues at hand and are investigating them as completely as we can. As such, we hope to have more information for you soon.



Second, thank you to everyone that is reporting your issues in a constructive manner, as well as the members of the community doing your best to help out your fellow gamers. Please feel free to continue doing so - the more information we have, the better a chance we have of coming up with a solution.



So, we appreciate your continued patience! We're working on it and as soon as we've got some news we'll let you know.

[Thandal N'Lyman]

Nathan Willis wrote...

Hello all,

First, I wanted to take a moment to say that we're very sorry to hear that some of you are having issues with our game. We're aware of the issues at hand and are investigating them as completely as we can. As such, we hope to have more information for you soon.

Second, thank you to everyone that is reporting your issues in a constructive manner, as well as the members of the community doing your best to help out your fellow gamers. Please feel free to continue doing so - the more information we have, the better a chance we have of coming up with a solution.

So, we appreciate your continued patience! We're working on it and as soon as we've got some news we'll let you know.

Wow! And Nathan isn't even a Moderator.

[Thandal removes tongue from cheek. and makes assumption that previous poster has read all 40+ pages of the topic.]

Glad to see a BW logo accompanying the (belated) acknowledgement of Patch 1.03 problems.  Now we can hope to see a real fix from the devs, and not just wonder if they even know about the issue.

Thanks, Nathan.  Look forward to your next update.

[Zepplin_Rules]

One dev came into a thread and said the exact same thing last month.

[Morte78]

One bug I have found is that Alistair keeps referring to my male player character as "my love" ever since I got his approval rating to 100 despite the fact that I haven't "romanced" him.



I respect the fact that Bioware decided to include non-traditional romance options in this game but considering there isn't an option to have an "I'm just not into you that way" conversation with Alistair this response is a bit inappropriate if the player character hasn't gone down the romance path with Alistair.

[Desasosiego]

Well well, if we have somebody w/ a Bioware logo in here!

A li'l cute bird told me we paying customers are having the crashing issues while pirates don't, how much truth is there regarding this matter?

If this is true, having a look at that crack could be helpful.



I think somebody actually mentioned this before in these forums, he/she might know who made the crack, but somehow, I've come not to expect much, complete and absolute distrust are actually the words best suited to illustrate my perceptions.

[didymos1120]

Desasosiego wrote...
A li'l cute bird told me we paying customers are having the crashing issues while pirates don't, how much truth is there regarding this matter?.

You mean the little bird that posted a couple pages back?  Well, one guy took said bird's advice and guess what? His game still crashes.  So much for that.

[didymos1120]

Morte78 wrote...
I respect the fact that Bioware decided to include non-traditional romance options in this game but considering there isn't an option to have an "I'm just not into you that way" conversation with Alistair this response is a bit inappropriate if the player character hasn't gone down the romance path with Alistair.

You know why you don't have that option with him?  Alistair isn't supposed to be into dudes, period.  Only Zevran and Leliana are available for same-sex romances without using mods.  You might be able to fix this by editing the savegame in the toolset.  Here's the structure:

Top
 |
 (bunch of other irrelevant crap)
 |
 |___SAVEGAME_PARTYLIST
         |
         |
         (bunch of other irrelevant crap)
         |
         |___SAVEGAME_PLOT_MANAGER
                |
                |___SAVEGAME_PLOT_LIST
                       |
                       |
                       (list of relevant crap)

You then have to hunt through all the sublevels for the particular specific SAVEGAME_PLOT_GUID string that identifies the core approval/romance related stuff:

840C666EA1FE48CBA260AB1FE42FCFA7

One of the SAVEGAME_PLOT_FLAGS entries should have the value 260.  Change it to 259,  and Alistair will no longer crave your smokin' man-flesh, and will simply be your wacky hetero pal.  Or at least I think he will.  If you try this, suffice to say that backing up the save beforehand is a good idea. Unforseen consequences and all that jazz, plus there could very well be other screwy romance-related plot flags lurking about in your save. 

Oh, and you may want to change the description of his approval state, too:

Top
 |
(bunch of other irrelevant crap)
 |
 |___SAVEGAME_PARTYLIST
         |
         |
         (bunch of other irrelevant crap)
         |
         |___SAVEGAME_PARTY_APPROVAL_LIST
                |
                |
                (list of relevant crap)

Look at the various SAVEGAME_PARTY_APPROVAL_ID values.  3050 is Alistair.  His SAVEGAME_PARTY_APPROVAL_DESC should be 394165.  That's "Love".  Change it to 371489, for "Friendly". Save and exit the toolset, then load up that save in the game.

This should work, but, again,  I'm not totally certain.

Modifié par didymos1120, 05 mai 2010 - 10:36 .

[Cloud Windfoot Omega]

i hope we get a crash fix is all i can say

[jsmile39]

Haven't played since 1.01something, recently reinstalled game (boxed version plus 1.03) and crash constantly. I played through game with v1.01 and CTD'd maybe 5 times total (most in lothering).

I've gotten about 1/5 of the way through v1.03 and have CTD'd ~50 times (randomly in combat, entering/ending combat, or shapeshifting to mouse in Fade -- possibly sneak related?).

Finally gave up and am reinstalling now with v1.02a (hopefully not virus infected since I never dl'd 1.02 from bioware).

Retail version
XP-SP3 (32bit)
E8400
Radeon 5850
Lastest drivers, directx, etc.

Well over a month since this game breaking patch and still nothing? At the very least they could provide an option to DL 1.02. And sure as hell not buying Awakening till it gets sorted, this patch makes TES4/Fallout3 look stable.

Modifié par jsmile39, 06 mai 2010 - 02:32 .

[WonderGamer]

didymos1120 wrote...

You know why you don't have that option with him?  Alistair isn't supposed to be into dudes, period.  Only Zevran and Leliana are available for same-sex romances without using mods.  You might be able to fix this by editing the savegame in the toolset.  Here's the structure:

Top
 |
 (bunch of other irrelevant crap)
 |
 |___SAVEGAME_PARTYLIST
         |
         |
         (bunch of other irrelevant crap)
         |
         |___SAVEGAME_PLOT_MANAGER
                |
                |___SAVEGAME_PLOT_LIST
                       |
                       |
                       (list of relevant crap)

You then have to hunt through all the sublevels for the particular specific SAVEGAME_PLOT_GUID string that identifies the core approval/romance related stuff:

840C666EA1FE48CBA260AB1FE42FCFA7

One of the SAVEGAME_PLOT_FLAGS entries should have the value 260.  Change it to 259,  and Alistair will no longer crave your smokin' man-flesh, and will simply be your wacky hetero pal.  Or at least I think he will.  If you try this, suffice to say that backing up the save beforehand is a good idea. Unforseen consequences and all that jazz, plus there could very well be other screwy romance-related plot flags lurking about in your save. 

Oh, and you may want to change the description of his approval state, too:

Top
 |
(bunch of other irrelevant crap)
 |
 |___SAVEGAME_PARTYLIST
         |
         |
         (bunch of other irrelevant crap)
         |
         |___SAVEGAME_PARTY_APPROVAL_LIST
                |
                |
                (list of relevant crap)

Look at the various SAVEGAME_PARTY_APPROVAL_ID values.  3050 is Alistair.  His SAVEGAME_PARTY_APPROVAL_DESC should be 394165.  That's "Love".  Change it to 371489, for "Friendly". Save and exit the toolset, then load up that save in the game.

This should work, but, again,  I'm not totally certain.

Probably easier to just patch up to 1.02a than trying to edit the coding in the game save manually.  I've posted a link to the patch on FileFront in this thread a few times already; you won't need to look far for it again. 

[wolfwarp]

Hey, I haven't checked into this thread for quite some time. Has there been any BioWare response and action on fixing the game crashing issue with patch 1.03 for DAO? I just read that they've announced another DLC. I really hope that I can play it by then. I am still wanting to play Awakening.

[Gnaeus.Silvanus]

I got excited when I saw that Bioware logo only to read further and get disappointed that only "some" are experiencing problems with performance and stability. Great, just great! Keep on investigating and procrastinating on this issue until we bury and forget your game.



I, are got biowared!

[Zepplin_Rules]

Yep keep pumping out that DLC Bioware.



Patches don't make money. So why fix it when you can ignore it and tell your fans to basically f themselves.

[WonderGamer]

The way I see it, why make more DLC when people are not willing to install buggy patches which are required to use the new DLC?  They need to fix the content that is already there before adding new content.  I for one won't be buying any more DLC until they have a stable patch to run them on; I already made that mistake with the Feastday packs & it's not going to happen again. 

[DeadJediJamie]

Yeah, I realise that Bioware said they will support this game for two years, but I was under the impression that it would be somewhat stable during that time. The crashing is way too common an occurrence to be coincidence or isolated.



Come on Bioware, I want to actually buy Awakenings, but I cannot bring myself to do it knowing how badly this patch screwed up Origins for me. I can honestly say this is unprecedented in my 20 years of gaming that I had to avoid buying a game because of such a game breaking bug. Hell I bought Shivering Isles expansion at release and Oblivion was a buggy mess!

[Desasosiego]

didymos1120 wrote...

Desasosiego wrote...
A li'l cute bird told me we paying customers are having the crashing issues while pirates don't, how much truth is there regarding this matter?.

You mean the little bird that posted a couple pages back?  Well, one guy took said bird's advice and guess what? His game still crashes.  So much for that.

Hmmm, actually that wasn't my source, I did however know that somebody posted it in here too. Funny, I think something like this happened way back w/ ME 1 release, I remember people talking about pirated version being much more stable. Wether this is the case again or not, we still can't tell, and I doubt pirates are going to come here and go like: so we like pirated your stuff, and we are (or aren't) having these issues.

Modifié par Desasosiego, 06 mai 2010 - 01:23 .

[searanox]

I like how BioWare only felt the need to respond to this several months after 1.03 came out and caused so many problems.

Also, is it just me, or does this canned response reek of arrogance?  The whole "oh, well we think our game is awesome and perfect, and there really aren't any problems with it, but hey, if you guys are going to complain, then I guess maybe we'll do something" attitude strikes me as mildly insulting.  I'm not sure if that's intentional or not.

Modifié par searanox, 06 mai 2010 - 01:25 .

[dragonsouce]

dragonsouce wrote...

Ok it work thank you Forumzilla for the -dx9 command. It IS Direct x 10 or 11!!!!

I Fixed it and this time I had my mage hide in a room for the fight and made breakfast (set all my video to max) combat lasted 35 minutes no crash !!!!!
ATI Catalyst uses might want try this as my guess is there downgraded drivers do not use the Dx fuction that doing the leak.So they might be able to re upgrade.
Here how to do it.
Go to your Dragon Age Origins folder look inside for a folder named bin_ship then look for a file named daorigins.exe
in my case that's H:\\\\\\\\\\\\\\\\Dragon Age Origins\\\\\\\\\\\\\\\\bin_ship (yes I got lot drives.)
then create a shortcut for daorigins.exe.
in the shortcuts property's look for target line.and put this in using the correct path AND INCLUDE the " " marks and a space before -dx9 !
"H:\\\\\\\\\\\\\\\\Dragon Age Origins\\\\\\\\\\\\\\\\bin_ship\\\\\\\\\\\\\\\\daorigins.exe" -dx9
in my case in most it will be
C:\\\\\\\\\\\\\\\\Program Files (x86)\\\\\\\\\\\\\\\\Dragon Age Origins\\\\\\\\\\\\\\\\bin_ship\\\\\\\\\\\\\\\\daorigins.exe" -dx9
hit apply
go to the compatibility tab set to run in windows XP system pack 3 mode
set privilege Level to administration and apply.

OK Your Crash free so long as you run the game from this shortcut.

PS
I derlibratly stressed my system to make certain this works (not only did I run video to max and ram Combat beyond normal time I also left my Fire fox browser running with 150 tabs open and a bunch of explorer windows, so all I had was about 1 gig ram free and it still worked!

Icrashed again even with this after 2 hour tryed restart crashed again after 15 minutes tried again crashed in 10 going off to cry now . And my agrance is spent.

I even tried the damed Memory hack with Explorer Suite (I know how to use it) even knowing that Memory fix is pointless one on a 64 bit OS. (then tried it with Xp sp3 comp enabled) even threw in -Dx9. Nothing works.
-DX9 seems to be the only thing that has any posstive impact And it Still not stable enough to rick playing with cold reboots.
I give up.

Nathan Willis thank you for at least admitting there a problem. Why I can not speak for everyone here I myself started feeling like Bioware was treating me like I was saying that I needed To put Aluminum Foil in my hat to protect my self from Government Mind Control and keep the voices away. 

Modifié par dragonsouce, 06 mai 2010 - 02:30 .

[didymos1120]

WonderGamer wrote...


Probably easier to just patch up to 1.02a than trying to edit the coding in the game save manually.  I've posted a link to the patch on FileFront in this thread a few times already; you won't need to look far for it again. 

Why would that be of any help at all?  It didn't fix any of Alistairs dialogue/approval bugs. 

[didymos1120]

searanox wrote...

I like how BioWare only felt the need to respond to this several months after 1.03 came out and caused so many problems.

Ummm, what? "Several months"?  The patch only came out 2 months ago, and there's been an official topic about the crashing problems stickied on the first page of this forum for just under a month now.  Should they provide more frequent updates on what progress is or is not being made? Yes, absolutely.  Have they totally ignored it for "several months"?  Uh, no.

Modifié par didymos1120, 06 mai 2010 - 04:56 .

[Nathan Willis]

Hello again, quickly wanted to state that there was no arrogance or anything of the like intended. My apologies if it came off that way - my only intent was to state the fact that not everyone is experiencing issues.

That does not mean that those who are experiencing issues are somehow less important to us! To be clear: fixing what we can is still a priority of ours and we're tracking everything reported to the best of our ability. While we believe we've narrowed some the root causes down of many of the issues reported on the forums (and mentioned in this thread), unfortunately the nature of things is that it takes time to bring solutions to you, the community.

So! I want to reiterate that we're working on it. No news as of yet. As soon as we have some news, we'll let you know.