81 réponses à ce sujet

[InebriatedPizza]

Thank you, CrustyCat.

[Mustang68jd]

I am on Vista 64, quad-core, using nVidia drivers 195.62 for my 280m cards. Tried everything -- affinity core settings, compatibiity modes, -dx9, reinstalling C++ runtime components, reinstalling directx, reinstalling game (dowloaded from Impulse) multiple times, etc. Still get errors. Here's some examples in the Windows event logs (all different errors notice):

DAOrigins.exe
1.3.11253.0
4b7057ab
PhysXCore.dll
2.8.1.33
4a84f7c4
c0000005
000d428a
b3c
01cac92a0923931d

DAOrigins.exe
1.3.11253.0
4b7057ab
fmod_event.dll
0.4.24.1
49f8a62e
c0000005
00021381
1370
01cac92b380606dd

DAOrigins.exe
1.3.11253.0
4b7057ab
DAOrigins.exe
1.3.11253.0
4b7057ab
c0000005
00377180
df8
01cac9320f1f661d

Modifié par Mustang68jd, 21 mars 2010 - 11:36 .

[Osiris86]

After downloading this patch, I can no longer even start up my game for some reason, I don't know what happened, but I could play it before the patch then after I downloaded the patch I can no longer start the game. Anyone willing to help? 

[Mustang68jd]

Just tried something else -- disabled physx and played for a while without a crash. It will take some more testing, however.

[Raven-sb]

Mustang68jd wrote...

Just tried something else -- disabled physx and played for a while without a crash. It will take some more testing, however.

That's interesting Mustang. Physx has been known to cause problems with other games in the past.  I'll be curious to see how your playtesting pans out.

Chalk me up as another person affected by ctd's. 

Win 7 Professional 64-bit,
Nvidia Card latest drivers,
4 Gigs Ram
Running DA:O - Awakening, no 3rd party mods, all offical DLC installed.

[redleafchewer]

something I did yesterday.

downloaded the standalone 1.03 patch installed it on top of Awakening.
downloads the latest directx and installed after the patch.

Two sessions totaling 10 hours, no crashes.

Not saying it would work for everyone, but it did the job for me. Now instead of crashing under heavy spell effects, things just slow down like a kill animation until I run out of range of the effects.

I'm running Vista64 with 8 gig of ram on a q6600 so if it's slowing down still for me, it may not be any help for someone with 1 or 2 gig of ram on a duo.

on another note, I operate dual monitors and always have CPU and memory monitoring tools open on the second. Prior too awakening, I used to get heavy use on one core, with very light loads on the other three.

Now I am thrashing all four cores from 50 to 80 percent . I really don't see anything that has been added that would suddenly load up the processor like that. No mods are running, and I don't believe this game is designed to take advantage of multi's, so it's strange.

Modifié par redleafchewer, 22 mars 2010 - 02:30 .

[GPA_Nemesis]

One common note I keep seeing is x64 operating systems (Vista and 7). When they say it's not compatible, I think they are saying it's not compatible with 64-bit OSes. Which is still unforgivable. I'm curious how many users with crashing issues are using x64 OS versions?

[Mustang68jd]

I played some more tonight. Disabling physx DOES seem to help reduce the crashes, but I think it's only part of the solution. In about 2-3 hours of play tonight I only crashed one time -- an error in the DAOrigins.exe module according to event viewer -- so I think disabling it may cure some of the nVidia issues the game has. More time is still needed to test this though.

[Nyungarochaga]

Hello,



is it possible to get information from one Staff-member of Bioware, when does an update for patch 1.03 come?

[0ts0]

So, they release a game, and don't give out info if the patch is going to be fixed?

The DA:O went perfectly fine before 1.03. Perhaps 2 crashes in over 120hrs of gameplay.

After 1.03 all hell break lose - and worst of all, after installed Awakening, nothin works!



This is soooo typical EA products.

[Kurt M.]

DA:O pre-1.03 only crashed one time for me...while 1.03 has crashed at least 7-8 times.



Fortunately, all the crashes were in the same area (the Sloth demon fight), and I've left that part behind long ago...

[shnauser]

Gladiador2 wrote...
DA:O pre-1.03 only crashed one time for me...while 1.03 has crashed at least 7-8 times.
Fortunately, all the crashes were in the same area (the Sloth demon fight), and I've left that part behind long ago...

Pretty much the same experience.
Played through the Sloth deamon fight yesterday. The hole fight and the confrontation in the mage tower took about 4 hours. Had about 10 crashes through those 2 fights.

[Kurt M.]

I hadn't any crash in the confrontation with the final mage/demon/abomination/idiot battle...in fact, the whole game has only crashed in the Sloth demon part (+110 hours by now, and 2 chars) for me. Odd...

[Skaila]

Just wondering if this also affected other games or just DA:O? I'm currently running DA:O (not Awakening), foolishly enough got the 1.03 patch and am now experiencing the infamous 'pc reboot' crash. I got tired of DA:O crashing so i started playing another game and sure enough... my pc rebooted after 10 minutes.



Just wondering if this could be part of the problem or something else entirely?



Running Vista32 (quadcore)

4GB RAM

NVIDIA GeForce 9500 GT

[Wormrose]

I had a similar experience. DA:O crashes after 10 seconds everytime since 1.03. So until a fix is release I thought I'd play another game. That game also now crashes within 5 minutes every time.

[carlosjuero]

Skaila wrote...

Just wondering if this also affected other games or just DA:O? I'm currently running DA:O (not Awakening), foolishly enough got the 1.03 patch and am now experiencing the infamous 'pc reboot' crash. I got tired of DA:O crashing so i started playing another game and sure enough... my pc rebooted after 10 minutes.

Just wondering if this could be part of the problem or something else entirely?

Running Vista32 (quadcore)
4GB RAM
NVIDIA GeForce 9500 GT

That sounds like a hardware/heat issue on your PC - it isn't related to the patch.

[Jules Rules]

I'll post in this thread too.. I really hope they fix it soon. Was planning on buying Awakening this week but if I'm still randomly crashing every 10 mins there's no point is there?

[Obode]

HadesScorn wrote...

I'm frustrated at the crashing as well, but here's what needs to be kept in mind. A decent sized studio might keep anywhere from 20-50 QA personnel on hand depending on the size of the game and the time until going gold. At a max, those testers can usually work up to 16 hours during "crunch time" depending on state laws. In IL, where I worked for Volition INC during the Saints Row development, we could work a max of 12 hours a day.

Assuming that they had 50 QA testers and they worked 12 hours a day, 7 days a week, for 3 months straight [which would be awesome overtime pay], that's a total of 50400 hours put into testing the game.

Now, do you *honestly* think that less that 50400 people bought DAOA and played for an hour or more?

Here's the point. In the first *day* of a large release, people will always find a ton of bugs that the developers never saw. Instead of complaining about it in a manner that is unlikely to gain a good response, post detailed crash information. Include what rig you are running the system on, what your party was, and what *you* think may have led to it. This gives their in-house techs a chance to try and track it down to fix in the next patch.

And no, EA tech support never knows anything. Because it's EA!

Lets be honest here ey ? 1.03 march 8.. today march 22 ... If you use 14 days to fix a Showstopper, you might aswell start looking for a new job...Minor bugs.. sure take your time... CTD (widespread) hotfix... anything more then a week to fix is simply unacceptable, especially when theyr precious new expansion which you have to pay for FYI, Demands that you use a Unplayable version of the game... Not to mention they Do not offer older patch versions..

To be perfectly honest I am disgusted to see this coming from bioware... but then again I guees thats what happens when you jump in bed with EA..

And to be perfectly honest, considering how widespread the problem is, theres NO ****g way they would have missed It if they did proper testing of the patch. If you put 10 diffrent people on the same computer, or the same build for that mather. Then that Is not proper testing.... and In anycase... It wouldnt even have been a big issue if they put time into a hotfix, Instead of releasing a expansion that is more or less unplayable because It requires you to use a patch that is a showstopper..

[gizmert]

It would be nice to have some feedback from developers as to when this will be fixed, or even simply an aknowledgment that they are aware a problem exists and are working to rectify it.



It would be appreciated by many, i'm sure, if a quick post could be made. Maybe even included some suggested short-term fixes (?).

[Surango]

That's the thing, there ARE some fixes posted. Both on the bugs list page and the patch release page. There is also a thread full of suggestions: social.bioware.com/forum/1/topic/58/index/1798733/1

[adrichardson]

The reason 1.03 is still with us is the cash cow called DA Awakening. They should never have tied Awakening to the patch in the first place. Either EA is playing patch politics (you're not releasing another patch this month) or it's taking longer to fix than anticipated. Neither is good news for customers, especially given the lack of communication.



On another note, I really don't buy all the "it's X64" responses. Are people honestly saying that it's only supposed to be played on an OS that's now 9 years old?!

[Obode]

Surango wrote...

That's the thing, there ARE some fixes posted. Both on the bugs list page and the patch release page. There is also a thread full of suggestions: social.bioware.com/forum/1/topic/58/index/1798733/1

Yeah, ive seen these suggestions and theyr about as wise as "Put toothpaste on your pimples to get rid of em"..


I mean seriously.. "Turn of autosave" "Turn of Online Options" "Turn on Online Options" "Lower Graphics" .... about as useful as "Hey, try restart your computer"


And lets be totally honest here.. If you release a Expansion which is only supported by a specific patch, when the patch in question is a showstopper, then you might aswell add a "Not a working product" to the god damn box.

I don't care how deep the problem Is, If you dont have enough insights into your own codes, to be able to locate the problem, then you obviously arnt worthy of your salary. The fact that they pushed Awakening out the door knowing that the patch it operated with was a showstopper Only makes it  worse.

Modifié par Obode, 22 mars 2010 - 09:47 .

[Melisenta]

I give up.I haven't even completed Awakening. But after 3 days of struggle, trying out all potential fixes people have come up with,I just don't feel like going on. I've lost my interest in this expansion. Oh what a fool I've been pre-ordering it from ea store

[Obode]

Im sorry but If you call this "acknowledgement" then your fairly dense:

Just want to let you guys know that we are going through this thread and others like to compile your feedback and make sure these sorts of things are entered into our bug database. Thanks a lot and keep it up!

This Is pretty much the basic response for minority bugs... Yeah, we see some people reporting this problem, but theres not nearly enough people for it to be a major concern.

The fact that he speaks of entering it into the bug database sais alot in it self... If they actually took it seriously It would be the number one priority, and entering documenting the bug would be the least of theyr worries.

Edit: bleh seems like I ended up responding to a entirely diffrent page.... Blame the forums for jumping you back to page 1 after submitting a reply

Modifié par Obode, 22 mars 2010 - 09:56 .

[Melisenta]

Obode wrote...

Im sorry but If you call this "acknowledgement" then your fairly dense:

Just want to let you guys know that we are going through this thread and others like to compile your feedback and make sure these sorts of things are entered into our bug database. Thanks a lot and keep it up!

This Is pretty much the basic response for minority bugs... Yeah, we see some people reporting this problem, but theres not nearly enough people for it to be a major concern.

The fact that he speaks of entering it into the bug database sais alot in it self... If they actually took it seriously It would be the number one priority, and entering documenting the bug would be the least of theyr worries.

Edit: bleh seems like I ended up responding to a entirely diffrent page.... Blame the forums for jumping you back to page 1 after submitting a reply

Well, considering that devs have shown themselves up only in the "Awakening bug thread", I bet that patch 1.03b, or 1.04 (whatever they call it) will contain fixes for bugged quests, approval rating etc. Our crashes will be addressed much-much later. Just like it was with slow loading times.