1370 réponses à ce sujet

[Eurypterid]

The-Crack-Fox wrote...

Back in the NWN days an issue like this would have been acknowledged and fixed within a week of it being reported.

You mean like the collision detection bug in NWN patch 1.65 that took 6 months to get fixed in NWN patch 1.66, and even then wasn't entirely eliminated?

[DragonRageGT]

Perhaps that crazy room in SoU which brought framerate to zero and was fixed a few days after the xpack release or no one could ever have played it?

[Eurypterid]

RageGT wrote...

Perhaps that crazy room in SoU which brought framerate to zero and was fixed a few days after the xpack release or no one could ever have played it?

Yes, exaclty. An issue that affected everyone. Unlike the crashing and the collision detection, which isn't/didn't (at least not to the same degree for the CD bug in NWN).

I'm not trying to say BioWare is perfect. I'm just pointing out that there's a lot of 'rose colored glasses' going on when people start talking about how BioWare 'used to be'.

[dragonsouce]

RageGT wrote...

It seems that all my crashes brought by 1.03 has to do with sound issues. When the game CTD, there are still some game sounds in the background playing, broken sounds, not sure what's the English word for that but they're not clear crystalline sounds as they play during the game, before the crashes of course.

You know I read this before I wonder if it could be are  onboads sound. A bad codex or sync issue?  The mages do a lot of sound effects maybe one is the Memory culprit? I remeber I had a heat issue with ME1 (they are Similare engines very close) Wear I and others would over heat Multicore  CPU s unless we diabled Hardwear and went softwear sound.)No idear why that worked.  What kind sound hardware do you have is it on board your mother board or a sepret sound card?

[DeadJediJamie]

dragonsouce wrote...

RageGT wrote...

It seems that all my crashes brought by 1.03 has to do with sound issues. When the game CTD, there are still some game sounds in the background playing, broken sounds, not sure what's the English word for that but they're not clear crystalline sounds as they play during the game, before the crashes of course.

You know I read this before I wonder if it could be are  onboads sound. A bad codex or sync issue?  The mages do a lot of sound effects maybe one is the Memory culprit? I remeber I had a heat issue with ME1 (they are Similare engines very close) Wear I and others would over heat Multicore  CPU s unless we diabled Hardwear and went softwear sound.)No idear why that worked.  What kind sound hardware do you have is it on board your mother board or a sepret sound card?

I admit that this is plausible since the way his game crashes doesn't seem at all similar to what happens with mine (no sounds playing in the background). I suppose the more pressing question is did he have these crashes before? In my case, no, I didn't, but in his? Possible.

[KDoombringer]

Sooo 50 pages and I really don't want to read them all to see if there is a possible answer. But all of DA:O i had not a single crash, i installed awakening and the game crashes almost every 20mins +/- 10mins without fail has anyone come up with a solution to this?



I have been looking on the net and no one seems to have any answers not even Bioware Support

[Harbinger1975]

As has been said, Bioware is gathering as much information/bug reports about the 1.03 patch. It takes time to gather all the information and try to duplicate the bugs. Plus, if they can duplicate it, they have to tear the code apart to figure out where it went wrong with the patch. Patience my young padawans. Also, I found something interesting on MMORPG.com after reading some of the....shall we say, less than pleasent posts I've seen here.



http://www.mmorpg.co...Us-vs-Them.html



Before blasting Bioware, consider what could be happening.

[ShinsFortress]

Eurypterid wrote...

RageGT wrote...

Perhaps that crazy room in SoU which brought framerate to zero and was fixed a few days after the xpack release or no one could ever have played it?

Yes, exaclty. An issue that affected everyone. Unlike the crashing and the collision detection, which isn't/didn't (at least not to the same degree for the CD bug in NWN).

I'm not trying to say BioWare is perfect. I'm just pointing out that there's a lot of 'rose colored glasses' going on when people start talking about how BioWare 'used to be'.

All that may be true.  But it was some time ago.  Companies and systems are supposed to develope and improve over time, not stagnate or get worse.  Things were different then, the game business is more mainstream commercial now.....

[Zepplin_Rules]

misles75 wrote...

Before blasting Bioware, consider what could be happening.

Screw you, I'm not thinking. Hating is soooooo much easier.

[Levi28001]

Zepplin_Rules wrote...

misles75 wrote...

Before blasting Bioware, consider what could be happening.

Screw you, I'm not thinking. Hating is soooooo much easier.

Lol, thats quotable.

[Quels]

Eurypterid wrote...

The-Crack-Fox wrote...

Back in the NWN days an issue like this would have been acknowledged and fixed within a week of it being reported.

You mean like the collision detection bug in NWN patch 1.65 that took 6 months to get fixed in NWN patch 1.66, and even then wasn't entirely eliminated?

In my case I have never bought a game I wasn't able to play at all before Awakening. And I'm really surprised Bioware was the first company to put me in this situation. Comparing not being able to play with the collision bug in NWN really makes no sense - bugs and a broken game (in my case) are two very different things.

Generally I'm very patient with bugs and errors in games and I expect them and I'm willing to tweak my pc or find other user made workarounds to prevent them until fixed. In this case I can't play the game at all before Bioware makes a fix to CTD on certain spells uses ... I haven't seen any user made workarounds for this error (yes, tried all the suggestions for different pc settings on my end)

Edit: fixed the Blizzard error ... just where my attention is now that it cannot be on Awakening.

Modifié par Quels, 21 mai 2010 - 05:52 .

[ShinsFortress]

"Blizzard"?

[Desasosiego]

Zepplin_Rules wrote...

misles75 wrote...

Before blasting Bioware, consider what could be happening.

Screw you, I'm not thinking. Hating is soooooo much easier.

I support this philosophy.

[Seibzz]

Seeing as it's a major request here, I just wanted to point out that a pickpocket fix does exist already through dragon age nexus. It's a simple mod, I use it and I have no more problems with this. Problem is I can't paste a link to it, my DL history there doesn't show the link anymore (I got it very early). But if you have a few minutes to spend, look there, it will be faster than waiting for Bioware to wake up and fix things.

nvm it's here too: http://social.biowar...t/2335/#details

sorry if it's old

Modifié par Seibzz, 21 mai 2010 - 08:14 .

[-Zippi-]

misles75 wrote...

As has been said, Bioware is gathering as much information/bug reports about the 1.03 patch. It takes time to gather all the information and try to duplicate the bugs. Plus, if they can duplicate it, they have to tear the code apart to figure out where it went wrong with the patch. Patience my young padawans. Also, I found something interesting on MMORPG.com after reading some of the....shall we say, less than pleasent posts I've seen here.

http://www.mmorpg.co...Us-vs-Them.html

Before blasting Bioware, consider what could be happening.

All they have to do is to remove the code in 1.03 back to how it was in 1.02a. 1.02a has the problem with slow loadingscreens, but the game is working perfect. The game is totally broken with 1.03, and I think it is shocking that it after two months still is the latest - and for steam users only - patch.

I use 1.02a now, so the game works great, but I can't play Awakening with this patch. Looks like I have to play it on PS3 and that is very disappointing.

[TriXteR]

-Zippi- wrote...

All they have to do is to remove the code in 1.03 back to how it was in 1.02a. 1.02a has the problem with slow loadingscreens, but the game is working perfect. The game is totally broken with 1.03, and I think it is shocking that it after two months still is the latest - and for steam users only - patch.

I use 1.02a now, so the game works great, but I can't play Awakening with this patch. Looks like I have to play it on PS3 and that is very disappointing.

Various
changes have been made to code and resources to support the Dragon Age:
Origins - Awakening expansion pack. Most of these changes do not affect
Origins itself.

so, from reading that patch note, taken from patch 1.03 notes, i`m guessing that if they revert the code to the one used in 1.02a, the awakenings expansion won`t work properly anymore... i`m a bit clueless when it comes to these stuff, but i got a feeling that i`m right on this one

oh, and thanks for this post, it enlightened me to make this sacrifice and give up awakening in favour of getting to play DA:O properly

i hope a fix is on its way though...

Modifié par TriXteR, 21 mai 2010 - 08:45 .

[DragonRageGT]

RageGT wrote...

It seems that all my crashes brought by 1.03 has to do with sound issues. When the game CTD, there are still some game sounds in the background playing, broken sounds, not sure what's the English word for that but they're not clear crystalline sounds as they play during the game, before the crashes of course.

dragonsouce wrote...

You know I read this before I wonder if it could be are onboads sound. A bad codex or sync issue? The mages do a lot of sound effects maybe one is the Memory culprit? I remeber I had a heat issue with ME1 (they are Similare engines very close) Wear I and others would over heat Multicore CPU s unless we diabled Hardwear and went softwear sound.)No idear why that worked. What kind sound hardware do you have is it on board your mother board or a sepret sound card?

DeadJediJamie wrote...

I admit that this is plausible since the way his game crashes doesn't seem at all similar to what happens with mine (no sounds playing in the background). I suppose the more pressing question is did he have these crashes before? In my case, no, I didn't, but in his? Possible.

Well, yeah, it's an onboard sound and no, I had no issues before 1.03.  And Win7 64 on a quad 9550 with 8gigs RAM should be able to handle it. It did up to 1.02.

While I don't have that many crashes per hour, perhaps one every 2-3 hours (I play a lot and long long sessions) they seem to have something in common. The sound thing was just my illiterate wild guess. I can't really say what tthey have in common but it feels like there's a pattern there.

Sometimes is right at entering some area. I can enter it 1000 times w/out problem but then poof... CTD. Sometimes is in the middle of a battle, that I can play 1000 times w/out problem and then, CTD.

[Eldtricht]

Hmm, I get frequent black screens where for about 30 seconds nothing happens, and then Loading... appears on the bottom right for a few seconds, then the scene/area loads. CPU usage has nearly tripled, and RAM usage went up by about 30-40%. It's like 1.03 increased the minimum system specs or something.



System:

AMD Phenom II X6 2.8 GHz

8GB Patriot RAM

2X RADEON HD 5770 (Nvidia can suxx0rs it)

HT | OMEGA Sound card



It also has memory fans, and liquid cooling on the CPU, and GPU's. Case ventilation is also good enough to keep it cool without the liquid cooling, so my system isn't the issue. They need to crank out a 1.03a/b or a 1.04 and fix this mess.

[Arkannis]

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 "daorigins.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 daorigins.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

This worked perfectly. Thank you!

[zartan88]

As well as the crashes is it also possible for bioware to get the Ancient Elven Boots to appear in Lothering as intended without using a mod!

[akanounnikoff]

Arkannis wrote...

This worked perfectly. Thank you!

Hello,

Thanks for the feedback, have fun with DAO :-)

Regards,

[Koralis]

misles75 wrote...

As has been said, Bioware is gathering as much information/bug reports about the 1.03 patch. It takes time to gather all the information and try to duplicate the bugs.

Many of the bugs are obvious and repeatable (pickpocketting), and others can't have that many variations that running a simultation with different gear loadouts wouldn't have triggered it quickly (architect stealing gear bug.)

They could have released a quick patch 1.04 while working on the rest.  I'd be shocked if these two (in addition to the ancient elven boots, etc, bugs) haven't already been fixed in-house, but not released yet.   They haven't released it yet though...

.
Why not?   The answer is unfortunately, business.  Patching the code means postponing DLC, because all of the DLC code has been written/validated based on a given codebase.   DLC has caused the problem.  In the past there's no way that they would have let glaring and infuriating bugs go unaddressed for months.  We're not talking hardware incompatibility problems here, which are understandably hard to diagnose and replicate because of the HUGE number of variations and combinations.

So, in pursuit of the greater-buck, we're party to crappy service.  Welcome to the future!

http://www.mmorpg.com/showFeature.cfm/feature/4254/Jon-Wood-Us-vs-Them.html

Before blasting Bioware, consider what could be happening.

There's not much point in confirming to us that it will take 3 months to get a patch, because that will just infuriate people even more than silence and also get press.   Stringing us along until it doesn't impact the bottom line is the least painful way for them to handle it, because the Powers that Be aren't going to allow a patch earlier than that. 

They've got a full years worth of DLC coming, and can't stop the gravy-train.  Some of the later DLC can be converted to work with 1.04 since there's time to catch problems.  When the next DLC-to-be-released is based on the current patch, then we'll get the patch, and not a moment sooner.

Modifié par Koralis, 22 mai 2010 - 02:11 .

[sk5000]

I am having a problem with the game crashing regularly. How can I fix this? I am running the following.



AMD Phenom 3Core Processor

8GB RAM

Radeon HD 4600 1GB RAM

Creative Labs Sound Blaster X-Fi Platinum



I am playing a warrior and I am at the point of cleaning out the Mage tower and I get to the second part after entering and talking to the Tranquil Store room guy and after leaving that area, I defeat the first 2 waves of abominations and the game just suddenly crashes for no reason. It is getting frustrating and annoying. Oh and Im running Windows 7 Home Premium 64 Bit OS. Please help?



Also, I have the latest Direct X version and all drivers are up to date as of the date of this post. And Windows is also up to date with all the updates to date. I am at a loss as to what to do about this.

[dragonsouce]

Koralis wrote...

misles75 wrote...
I so agree. People who keep saying not to bash Biowear I serjest they read to entire 50 page thread first I did.
There plenty to BASH!


As has
been said, Bioware is gathering as much information/bug reports about
the 1.03 patch. It takes time to gather all the information and try to
duplicate the bugs.

Many of the bugs are obvious and
repeatable (pickpocketting), and others can't have that many variations
that running a simultation with different gear loadouts wouldn't have
triggered it quickly (architect stealing gear bug.)

They could
have released a quick patch 1.04 while working on the rest.  I'd be
shocked if these two (in addition to the ancient elven boots, etc,
bugs) haven't already been fixed in-house, but not released yet. 
 They haven't released it yet though...

.
Why not?   The
answer is unfortunately, business.  Patching the code means postponing
DLC, because all of the DLC code has been written/validated based on a
given codebase.   DLC has caused the problem.  In the past there's no
way that they would have let glaring and infuriating bugs go unaddressed
for months.  We're not talking hardware incompatibility problems here,
which are understandably hard to diagnose and replicate because of the
HUGE number of variations and combinations.

So, in pursuit of the
greater-buck, we're party to crappy service.  Welcome to the future!

http://www.mmorpg.com/showFeature.cfm/feature/4254/Jon-Wood-Us-vs-Them.html

Before
blasting Bioware, consider what could be happening.

There's
not much point in confirming to us that it will take 3 months to get a
patch, because that will just infuriate people even more than silence
and also get press.   Stringing us along until it doesn't impact the
bottom line is the least painful way for them to handle it, because the
Powers that Be aren't going to allow a patch earlier than that. 

They've
got a full years worth of DLC coming, and can't stop the gravy-train. 
Some of the later DLC can be converted to work with 1.04 since there's
time to catch problems.  When the next DLC-to-be-released is based on
the current patch, then we'll get the patch, and not a moment sooner.

I agree fully!

And people who say do not bash Bioware till you have the facts,I would ask that they give us the same considration and read the 50 page thread!

There plenty to BASH!

Win7 64 on a quad seem to be have most problems and most use outboard sound.
One thing to remember if want talk about fair is this.
Pretty much told us there was no glitch at first.
Several of us my self include wear informed in email that patch 1.03
was never testesd Win7 64 with this patch.
Funny on my cd case the system requirements say Windows 7 that is all it said not just Windows 7 32

The game is supposed to work with 64 and the game before that patch was tested with 64 so why not 1.03?
That is blatant incompetence and Disrespect for us End users as well as just plain lazy!
On Bioware part so let stop giving them the benefit of the doubt.

AND I SAY IT AGAIN! There was no Public Beta.That could of prevented this. (Could not Guarantee but it would of cost them little to tried public testing first.)

Bioware Quality controls become a bad Joke and I am tied of being a punch line.
End of story.

Modifié par dragonsouce, 22 mai 2010 - 04:09 .

[Koralis]

dragonsouce wrote...

Win7 64 on a quad seem to be have most problems and most use outboard sound.
One thing to remember if want talk about fair is this.
Pretty much told us there was no glitch at first.
Several of us my self include wear informed in email that patch 1.03
was never testesd Win7 64 with this patch.
Funny on my cd case the system requirements say Windows 7 that is all it said not just Windows 7 32

The game is supposed to work with 64 and the game before that patch was tested with 64 so why not 1.03?
That is blatant incompetence and Disrespect for us End users as well as just plain lazy!
On Bioware part so let stop giving them the benefit of the doubt.

Well, to be fair, it's not a problem with Win7 x64 per se.  That's what I run, along with the quadcore cpu, and don't have any crashing, etc.

In this case it's much more likely to be an incompatibility introduced with sound or video card, but yeah, quality assurance on dlc and awakenings was much less robust than the main game, and much less than it should have been.


A lot of people with problems seem to be running 3000/4000 era graphics cards?   I'm running the 5850, so modern drivers, a lot of bug fixes and compatibility for Win7, etc, and probably much less likely to see problems that crop up.   What graphics card/sound board are you using?

AMD Phenom 3Core Processor
8GB RAM
Radeon HD 4600 1GB RAM
Creative Labs Sound Blaster X-Fi Platinum


I am playing a warrior and I am at the point of cleaning out the Mage tower and I get to the second part after entering and talking to the Tranquil Store room guy and after leaving that area, I defeat the first 2 waves of abominations and the game just suddenly crashes for no reason. It is getting frustrating and annoying. Oh and Im running Windows 7 Home Premium 64 Bit OS. Please help?

As an experiment, you may want to try turning your graphics settings WAAAY down for the game... low res textures, low AA, etc, and drop resolution to say 800x600.

If it doesn't crash, it indicates either an overheating problem or a bug in trying to do a particular effect without enough memory, etc.  If it still crashes then its not an overheating problem.  Could still be a bug in the driver/video card firmware doing things differently than Bioware assumes though,


I've got a X-Fi platinum too with the latest drivers, so that's not likely the problem.


Given 8 GB of ram... you might be having a timing issue on your memory.  You may want to download and burn a Memtest x86+  CD and let it run through for a while.   When you increase the numbers of chips, you often need to turn down the timings a bit.   The memory allocation could go from accessing bank 1 for the early part, then swapping to bank 2 later due more and more memory used, and bank 2 may not be doing so well.


Before pooh-poohing the ram scenario, know that after upgrading to 10.1 drivers from ATI I started crashing all over the place, where I wasn't before, and usually before windows was fully running.  I blamed ATI.  Turns out to be a motherboard issue.  I found that memtest was giving me a ton of errors!  it turns out that I'd also upgraded my bios around the same time... 

Ultimately the solution for me is to hit the reset button after the memory test.  If I do that, the computer works like a champ.   I'm not sure what Gigabyte is doing differently between cold boot and reset, but it makes a huge difference.

Modifié par Koralis, 22 mai 2010 - 06:39 .