Aller au contenu

Photo

Bugs with 1.03 patch...


1370 réponses à ce sujet

#801
wolfwarp

wolfwarp
  • Members
  • 307 messages

jlc_38 wrote...

OK quick poll. How many of you that have been burned by this
patch plan not to buy the next DA game, or Awakening and it's DLC? 


Me, for sure.  Just today, my friend and I were inside a PC game store.  We were staring at Awakening.  I would have bought it had I not faced with the patch 1.03 patch problem (crash on my Vista and ATI 5850 card, all drivers updated, Windows updated, background tasks eliminated).  My friend is still playing DAO, on patch 1.02a thanks to my advise.  So far, I am asking all my friends in my social network and my website NOT to dive into Awakening as yet.  Not until we see a stable patch.

Modifié par wolfwarp, 05 avril 2010 - 03:58 .


#802
wolfwarp

wolfwarp
  • Members
  • 307 messages

jlc_38 wrote...

Well I'm really surprised that this has not been fixed by
now. I got a great deal on Awakening ($24) last week, and I was really hoping
that 1.03a would be out by now. How many people complaining about this messed
up patch does it take to get some kind of response from EA/Bioware? I see even
the moderator has stopped posting.


The last update from our moderator was that the developers are looking into the error reports and attempt to fix the problem (and then the DLC got released in a higher priority, of course).  The next step is for the developers to release the fix.  At this stage, there is nothing more the moderators can do or say, quite honestly.  "Coming soon, if ever" is not good enough.  The only way to quiet the noise down is with a quality patch, I reckon.

#803
Lexily

Lexily
  • Members
  • 3 messages
Is there a place I can go to see some of the bug issues? I actually have had some major issues? I started a new toon, to go all the way...through expansion...I chose queen, and now good ol' Al thinks he is King? huh? yet? it tells me, she is sole ruler? This has never happened. Is there a fix?

#804
Thandal N'Lyman

Thandal N'Lyman
  • Members
  • 2 407 messages

akanounnikoff wrote...

sergey_tretiyak wrote...

Win7x64 . Right now I'm stuck in the game, because it crashes constantly during some boss fight, and I can't move on.


Hi,

Did u (and all CTD's victims) tried this:
http://social.biowar...3999/31#2037048

It fixed nearly all CTD's in my case (I am also in win7 64 bit with patch 1.03).

The game was nearly unplayable (crashed every 5 or 10 mn), now, with this trick, it is nice (only one CTD after 6 hours playing).

Regards,


Ak;
Haven't had a lot of time to test things this weekend, and I happen to be at a point in the overall story-arc when there's *lots* of travel and dialogue to pursue, but relatively little action /combat until I reach the LOTF. So I haven't posted a "report of progress" (too soon to tell...)
But in response to your query:
Yes, I sucessfully re-coded the batch and ran it against the 1.03 "daorigins.exe", and am using that version in the game.
And yes, since doing so, I have not encountered another CtD.  (Yea!  If it holds... "Thank you! Thank you!")

#805
Thokundin

Thokundin
  • Members
  • 41 messages

-Zippi- wrote...

- Game starts lagging after 30 mins -1 hour.
- Game crashes after  1 hour - 2 hours.

Never had any lag or chrashes before 1.03.


I am having the same problem.  When the game crashes for you does it say "Dragon Age: Origins Not Work Properly, Windows is Searching for A Solution to this Problem"?

#806
cruelgretchen

cruelgretchen
  • Members
  • 184 messages
Bought my DAO:A like a week ago and couldnt bring myself to install it bc of 1.03. , most likely i wont even touch the game unless theres a half decent new patch that fixes at least the major issues.




#807
Dukoth

Dukoth
  • Members
  • 1 messages
is there a way to get return to ostagar to work with this patch, it says I need 1.02 installed to use it but I patched strait to 1.03, and I tried the updaterdiagnostic tool, but it sais that .net framework 2.0 sp1 is not compatible with vista



is there any other way to get this dlc to work

#808
akanounnikoff

akanounnikoff
  • Members
  • 16 messages

Thandal NLyman wrote...

akanounnikoff wrote...

sergey_tretiyak wrote...

Win7x64 . Right now I'm stuck in the game, because it crashes constantly during some boss fight, and I can't move on.


Hi,

Did u (and all CTD's victims) tried this:
http://social.biowar...3999/31#2037048

It fixed nearly all CTD's in my case (I am also in win7 64 bit with patch 1.03).

The game was nearly unplayable (crashed every 5 or 10 mn), now, with this trick, it is nice (only one CTD after 6 hours playing).

Regards,


Ak;
Haven't had a lot of time to test things this weekend, and I happen to be at a point in the overall story-arc when there's *lots* of travel and dialogue to pursue, but relatively little action /combat until I reach the LOTF. So I haven't posted a "report of progress" (too soon to tell...)
But in response to your query:
Yes, I sucessfully re-coded the batch and ran it against the 1.03 "daorigins.exe", and am using that version in the game.
And yes, since doing so, I have not encountered another CtD.  (Yea!  If it holds... "Thank you! Thank you!")


Thanks you for the feedback !!!

Now, we can give EA and bioware team a clue !

Hey guys, look at your code against memory management (at least for 64 bit OS's)

And thanks for this great game, really !

Regards,

#809
Guest_nosecone2010_*

Guest_nosecone2010_*
  • Guests
I'm running with patch 1.03 on 32-bit Vista Home Premium and I've looked at the last 12 DA:O CTD events in the windows logs to see if there are any clues there. They all report this:



Faulting application DAOrigins.exe

version 1.3.11253.0

time stamp 0x4b70580a

faulting module DAOrigins.exe

version 1.3.11253.0

time stamp 0x4b70580a

exception code 0xc0000005



but there are sometimes different fault offsets:



fault offset 0x00392afe (4 times)

fault offset 0x0016d163 (once)

fault offset 0x00053870 (once)

fault offset 0x0041bc64 (6 times)



Does this mean anything to anyone?


#810
Bassooner

Bassooner
  • Members
  • 29 messages

akanounnikoff wrote...

Dragon age CTD's in Windows 7 64 bits --> partial fix maybe here !

Hi,

I encountered similar CTD's problem with fallout 3 that where solved with the trick provided here (thanks to NMC and Madboris):
http://www.fallout3n...ile.php?id=6510
I used the same solution for the main dragon age executable (daorigins.exe) and ... big ammélioration, only 1 CTD after more than 6 hours playing (before I couldn't play more than 10 mn).

How it works:

Windows 7 64 bits is able to address large memory space (in my case I hace 12 GB memory), "standard" win32 executable can't use more than 2 GB of memory.
Sometimes, when memory space is exhausted, it may cause CTD's and other bad things.
The files provided for fallout 3 by NMC can be used to patch the header of any executable, including the dragon age exe file, to make it able to exceed the 2 GB memory limit.

It is quite simple:

1) download the archive on the provided link
2) edit the start.bat file and replace any occurence of "fallout3.exe" with "daorigin.exe"
3) IMPORTANT: make a backup of your daorigin.exe file
4) copy the file in the folder where you have extracted the 3 GB enabler files
5) execute the modified start.bat and follow the instructions
6) move the patched daorigin.exe in your fallout 3 bin directory, replacing the original file.

WARNING: If you are using a 32 bit OS, you also need to allow large memory address at system level via boot.ini edition. Please read the readme included in the archive

Note: no reverse engineering here, just a modification of the header.

Please, let me know if it solved your CDT as it solved mine.

Best regards and have fun with Dragon Age,

P.S.: I imagine it will not help for any quest related bugs

I'm willing to give this fix a try. Unfortunately, I couldn't find the exe file to change. I have a DAOriginsLauncher.exe file and a daorigins.exe file (note the S on the end). Should I be modifying one of these files? If so, do I need to change the script in the start.bat file? Or am I just looking in the wrong place? Thanks for your help.

#811
Kastagir

Kastagir
  • Members
  • 359 messages
Maybe they're too busy to talk right now (preparing the next prank DLC, no doubt). Seriously, if Wachter put a post up on these forums acknowledging that a patch was being worked on, what would it accomplish? We know it is being worked on since they're gathering data and have more plans for DA. Anything they say at this point will just invite meaningless adulation from some fans (who are ecstatic over any/every Bioware attempt at information) or caustic derision directed at the imperfection of the current state of the game. The more I understand just how bad 1.03 is, the more Bioware's strategy of staying quiet about it makes sense. We just have to be patient and hope they have enough respect for their intellectual property and the community to not let it go the way of Obsidian's NWN2.

Modifié par Kastagir, 05 avril 2010 - 10:15 .


#812
wolfwarp

wolfwarp
  • Members
  • 307 messages

Kastagir wrote...

Maybe they're too busy to talk right now (preparing the next prank DLC, no doubt). Seriously, if Wachter put a post up on these forums acknowledging that a patch was being worked on, what would it accomplish? We know it is being worked on since they're gathering data and have more plans for DA. Anything they say at this point will just invite meaningless adulation from some fans (who are ecstatic over any/every Bioware attempt at information) or caustic derision directed at the imperfection of the current state of the game. The more I understand just how bad 1.03 is, the more Bioware's strategy of staying quiet about it makes sense. We just have to be patient and hope they have enough respect for their intellectual property and the community to not let it go the way of Obsidian's NWN2.


I understand where you come from, the whole keeping quiet strategy.  But action often speaks louder than words. The fact that BioWare / EA releases another DLC (Feastday) to make more money before they even fix the patch 1.03 that affects a segment of their player base (read: some unfortunate PC gamers) is an action that is hard to swallow.  In fact, they really should have stablized the patch *before* even thinking of releasing Awakening, don't you think?

These actions speak.  And I am not sure why BioWare / EA would want to send such a signal to their fans.  The fact that we are hit with another DLC prior to fixing the patch?  That is not keeping quiet in my humble opinion.

#813
Jallard

Jallard
  • Members
  • 927 messages

wolfwarp wrote...

Kastagir wrote...

Maybe they're too busy to talk right now (preparing the next prank DLC, no doubt). Seriously, if Wachter put a post up on these forums acknowledging that a patch was being worked on, what would it accomplish? We know it is being worked on since they're gathering data and have more plans for DA. Anything they say at this point will just invite meaningless adulation from some fans (who are ecstatic over any/every Bioware attempt at information) or caustic derision directed at the imperfection of the current state of the game. The more I understand just how bad 1.03 is, the more Bioware's strategy of staying quiet about it makes sense. We just have to be patient and hope they have enough respect for their intellectual property and the community to not let it go the way of Obsidian's NWN2.


I understand where you come from, the whole keeping quiet strategy.  But action often speaks louder than words. The fact that BioWare / EA releases another DLC (Feastday) to make more money before they even fix the patch 1.03 that affects a segment of their player base (read: some unfortunate PC gamers) is an action that is hard to swallow.  In fact, they really should have stablized the patch *before* even thinking of releasing Awakening, don't you think?

These actions speak.  And I am not sure why BioWare / EA would want to send such a signal to their fans.  The fact that we are hit with another DLC prior to fixing the patch?  That is not keeping quiet in my humble opinion.


Unfortunately for and with corporations today it's all about the revenue with very little substance to back-it-up. They no longer care about quality assuance or customer satisfaction. The shareholders are the main focus. They care more about the investments their shareholders shell out to them.

Here we are the consumer pissing and moaning about the 1.03 patch, the Awakening expansion being a bust and full of bugs and with very little substance --not at all like the original DAO game-- and now the Feastday BS!?!

THEY DON'T GIVE TWO ****S ABOUT QUALITY CUSTOMER SERVICE AND SUPPORT.

The fact that they have kept silent and not produced a fix  is undeniably evident. Again, I challenge them to prove me wrong?

#814
darkizzle

darkizzle
  • Members
  • 108 messages
The feastday stuff is worthless garbage that adds nothing to anything. Why they think anyone wants this crap is beyond me. Oh yes, almost forgot about the blind sheep who would buy Bioware's feces if they put a price tag and their logo on it, and that's exactly what they did. The best part is that, somehow, inexplicably, this garbage dlc STILL came out bugged, though it was literally nothing but a bunch of icons with mildly amusing text. APRIL FOOLS!!

#815
Funkjoker

Funkjoker
  • Members
  • 486 messages
Ageless isn't at its full potential!

Weakens Nearby Darkspawn
Messy Kills
Increases
Hostility and Intimidation

Those three properties do not work - BioWare, when do they do work? Oh, and why don't you give it the two rune slots in the first place instead of forcing us to use workarounds...

#816
Funkjoker

Funkjoker
  • Members
  • 486 messages

Modifié par Jean-Funk Van Damme, 06 avril 2010 - 12:42 .


#817
Rizcarn

Rizcarn
  • Members
  • 14 messages
I had posted before I had no crashes with 1.03. Well Post Ati hd 5850 upgrade and non legacy driver install ....Crashes. Not as frequent as some. Mostly loading new area slow slowwer slooowwer Crash. Still Only like 3 crashed in 15ish hours but still...

#818
Basher of Glory

Basher of Glory
  • Members
  • 1 026 messages

Jallard wrote...


The fact that they have kept silent and not produced a fix  is undeniably evident.
Again, I challenge them to prove me wrong?


Well, I guess you will remain one more lone voice in the wilderness.

On the other hand, the denial of feedback on the part of BioWare is a distinct message in itself, right?

#819
Kastagir

Kastagir
  • Members
  • 359 messages

Jallard wrote...

THEY DON'T GIVE TWO ****S ABOUT QUALITY CUSTOMER SERVICE AND SUPPORT.

The fact that they have kept silent and not produced a fix  is undeniably evident. Again, I challenge them to prove me wrong?


That's hardly a fair assessment if you're referring to Bioware.  They clearly care, but their priorities are suspect as we've seen with the Bioware Bazaar and the Feastday DLC.  If you're referring to the publisher, EA, then you are 100% correct and this shouldn't be news to anyone - they're the publisher.

DAA had a release deadline.  Bioware likely did the best they could (which was evidently not good enough) to meet this deadline set by EA and the RTO snafu likely didn't help.  Water under the bridge.  With no clear deadlines on the horizon (I don't consider the 02.01.2011 date relevant without a title), Bioware is free to show us where their priorities lie with regards to providing quality, comprehensive updates to their game.  The Feastday DLC was silly and didn't address the much more visible problems with the game, but ultimately was a very small investment in time/effort.  What Bioware does from here is most important.  If they spend this time to fix the game, everyone will be happy.  If EA sets arbitrary deadlines for patch releases, like Atari did for Obsidian's NWN2, then nothing worthwhile will ever get fixed.  I'm sure Bioware wants to fix this game as much as they want to continue creating new content for it, but as far as I'm concerned, they haven't demonstrated their ability to do it, whether due to restrictions imposed by their publishers or by the weakness of their QA.  A Bioware announcement of a patch tells us nothing.  Addressing these concerns tells us much more.  The ideal "coming out" announcement would address both of these matters, honestly and succinctly.

Also, I'll admit my own ignorance regarding the QA effort involved in a multi-platform title like this.  It is likely that at least some of the console testing takes place outside of Bioware's control/supervision.  However, PC testing should be under Bioware's control, and as we've seen, this area needs some work.

#820
Jallard

Jallard
  • Members
  • 927 messages

Kastagir wrote...

Jallard wrote...

THEY DON'T GIVE TWO ****S ABOUT QUALITY CUSTOMER SERVICE AND SUPPORT.

The fact that they have kept silent and not produced a fix  is undeniably evident. Again, I challenge them to prove me wrong?


That's hardly a fair assessment if you're referring to Bioware.  They clearly care, but their priorities are suspect as we've seen with the Bioware Bazaar and the Feastday DLC.  If you're referring to the publisher, EA, then you are 100% correct and this shouldn't be news to anyone - they're the publisher.

DAA had a release deadline.  Bioware likely did the best they could (which was evidently not good enough) to meet this deadline set by EA and the RTO snafu likely didn't help.  Water under the bridge.  With no clear deadlines on the horizon (I don't consider the 02.01.2011 date relevant without a title), Bioware is free to show us where their priorities lie with regards to providing quality, comprehensive updates to their game.  The Feastday DLC was silly and didn't address the much more visible problems with the game, but ultimately was a very small investment in time/effort.  What Bioware does from here is most important.  If they spend this time to fix the game, everyone will be happy.  If EA sets arbitrary deadlines for patch releases, like Atari did for Obsidian's NWN2, then nothing worthwhile will ever get fixed.  I'm sure Bioware wants to fix this game as much as they want to continue creating new content for it, but as far as I'm concerned, they haven't demonstrated their ability to do it, whether due to restrictions imposed by their publishers or by the weakness of their QA.  A Bioware announcement of a patch tells us nothing.  Addressing these concerns tells us much more.  The ideal "coming out" announcement would address both of these matters, honestly and succinctly.

Also, I'll admit my own ignorance regarding the QA effort involved in a multi-platform title like this.  It is likely that at least some of the console testing takes place outside of Bioware's control/supervision.  However, PC testing should be under Bioware's control, and as we've seen, this area needs some work.



It is nice that you support BioWare despite their obvious shortcomings. I also agree that EA as the publisher are down and out crooks. However, if quality customer service was a priority for BioWare they should be fortcoming with news of a new workable patch --along with an apology to their faithful customers. Undoubtly hell will freeze over before that ever happens: and, the same applies to EA. There is just no excuse!

I got to tell too that I had prepaid for the Awakening through the Internet with Gamespot, they took my money and claimed to have mailed it out on March 15th. However, it has been nearly three weeks and I have yet to receive it. Another nail in the coffin! Hereinto, after reading all of the negative post about the Awakening you can rest assure that I will be refusing delivey upon receipt: though I seriously doubt that Gamespot will refund my $40?!?

Modifié par Jallard, 06 avril 2010 - 04:00 .


#821
wolfwarp

wolfwarp
  • Members
  • 307 messages

Kastagir wrote...

Jallard wrote...

THEY DON'T GIVE TWO ****S ABOUT QUALITY CUSTOMER SERVICE AND SUPPORT.

The fact that they have kept silent and not produced a fix  is undeniably evident. Again, I challenge them to prove me wrong?


That's hardly a fair assessment if you're referring to Bioware.  They clearly care, but their priorities are suspect as we've seen with the Bioware Bazaar and the Feastday DLC.  If you're referring to the publisher, EA, then you are 100% correct and this shouldn't be news to anyone - they're the publisher.

DAA had a release deadline.  Bioware likely did the best they could (which was evidently not good enough) to meet this deadline set by EA and the RTO snafu likely didn't help.  Water under the bridge.  With no clear deadlines on the horizon (I don't consider the 02.01.2011 date relevant without a title), Bioware is free to show us where their priorities lie with regards to providing quality, comprehensive updates to their game.  The Feastday DLC was silly and didn't address the much more visible problems with the game, but ultimately was a very small investment in time/effort.  What Bioware does from here is most important.  If they spend this time to fix the game, everyone will be happy.  If EA sets arbitrary deadlines for patch releases, like Atari did for Obsidian's NWN2, then nothing worthwhile will ever get fixed.  I'm sure Bioware wants to fix this game as much as they want to continue creating new content for it, but as far as I'm concerned, they haven't demonstrated their ability to do it, whether due to restrictions imposed by their publishers or by the weakness of their QA.  A Bioware announcement of a patch tells us nothing.  Addressing these concerns tells us much more.  The ideal "coming out" announcement would address both of these matters, honestly and succinctly.

Also, I'll admit my own ignorance regarding the QA effort involved in a multi-platform title like this.  It is likely that at least some of the console testing takes place outside of Bioware's control/supervision.  However, PC testing should be under Bioware's control, and as we've seen, this area needs some work.



Truth been told, I don't think we PC gamers are an unreasonable bunch. After all, we are here in this particular forum because we care. All BioWare needs to do is to acknowledge the issues some of us are facing and what is the plan to address them. For all I know, these issues can be caused by external factors outside BioWare's anticipation. But they should make proper communication. And not to remain silence and keep releasing DLC. They have been pretty active on the social media front like Twitter and Facebook. I am surprised that they let this communication disaster goes on. One month is a very long time to remain silence.

I hope BioWare can learn something from this mistake. I was just begin to like their games.

Modifié par wolfwarp, 06 avril 2010 - 05:06 .


#822
Phonantiphon

Phonantiphon
  • Members
  • 787 messages

wolfwarp wrote...

Kastagir wrote...

Jallard wrote...

THEY DON'T GIVE TWO ****S ABOUT QUALITY CUSTOMER SERVICE AND SUPPORT.

The fact that they have kept silent and not produced a fix  is undeniably evident. Again, I challenge them to prove me wrong?


That's hardly a fair assessment if you're referring to Bioware.  They clearly care, but their priorities are suspect as we've seen with the Bioware Bazaar and the Feastday DLC.  If you're referring to the publisher, EA, then you are 100% correct and this shouldn't be news to anyone - they're the publisher.

DAA had a release deadline.  Bioware likely did the best they could (which was evidently not good enough) to meet this deadline set by EA and the RTO snafu likely didn't help.  Water under the bridge.  With no clear deadlines on the horizon (I don't consider the 02.01.2011 date relevant without a title), Bioware is free to show us where their priorities lie with regards to providing quality, comprehensive updates to their game.  The Feastday DLC was silly and didn't address the much more visible problems with the game, but ultimately was a very small investment in time/effort.  What Bioware does from here is most important.  If they spend this time to fix the game, everyone will be happy.  If EA sets arbitrary deadlines for patch releases, like Atari did for Obsidian's NWN2, then nothing worthwhile will ever get fixed.  I'm sure Bioware wants to fix this game as much as they want to continue creating new content for it, but as far as I'm concerned, they haven't demonstrated their ability to do it, whether due to restrictions imposed by their publishers or by the weakness of their QA.  A Bioware announcement of a patch tells us nothing.  Addressing these concerns tells us much more.  The ideal "coming out" announcement would address both of these matters, honestly and succinctly.

Also, I'll admit my own ignorance regarding the QA effort involved in a multi-platform title like this.  It is likely that at least some of the console testing takes place outside of Bioware's control/supervision.  However, PC testing should be under Bioware's control, and as we've seen, this area needs some work.



I don't think we PC gamers are an unreasonable bunch. After all, we are here in this particular forum because we care.

That bit made me LOL.

Modifié par bassmunkee, 06 avril 2010 - 05:33 .


#823
Levi28001

Levi28001
  • Members
  • 536 messages
Why do people always seperate Bioware and EA. EA bought bioware,

It's not like THQ and say GSC for an example.(Stalker) Publisher and game developer...

Bioware is owned by EA! Why you think that Muzyka is VP at EA. They are just a studio of EA now. Keeping the Bioware name for people who hold on to it.

They could have changed to EA RPG ITS IN THE FAKE WORLD.
That would just suck however.

Stop trying to dump  the blame off of Bioware(for those of you who are). Anyways, fix awakening or 1.03a so i can buy awakening.(If 1.03a or 1.04 fixed it anyways).

O Yeah and Ka-bump to the top so maybe if they keep staring at this they will say something about thier broken patch.

Edited

Modifié par Levi28001, 06 avril 2010 - 06:03 .


#824
wolfwarp

wolfwarp
  • Members
  • 307 messages

bassmunkee wrote...

wolfwarp wrote...

I don't think we PC gamers are an unreasonable bunch. After all, we are here in this particular forum because we care.

That bit made me LOL.


Eh. Which bit makes you lol, lol. That we are an unreasonable bunch or we are the indifference bunch that seek group therapy here due to a bad patch?!

:)

#825
Phonantiphon

Phonantiphon
  • Members
  • 787 messages

wolfwarp wrote...

bassmunkee wrote...

wolfwarp wrote...

I don't think we PC gamers are an unreasonable bunch. After all, we are here in this particular forum because we care.

That bit made me LOL.


Eh. Which bit makes you lol, lol. That we are an unreasonable bunch or we are the indifference bunch that seek group therapy here due to a bad patch?!

:)

--

I don't think we PC gamers are a reasonable bunch. After all, we are here in this particular forum because we just want to complain about everything all of the time and we are never happy with anything because we think - every single one of us - that we could do it better. 

EFA.