1370 réponses à ce sujet

[Zayeem]

the only problem Ive had with Awakening (surprisingly) is that certain mods don't seem to be compatible with it, like the Grey Warden Runic Armor (which i downloaded and installed midway through Awakening), is there any way to fix that? Apparently from what i read from the forums there is some kind of mod/console command that fixes the Grey Warden Runic armor issue, anyone know where to find and use this?

[sk5000]

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.

Tried moving all settings to ultra low and I set Resolution to its lowest setting.  Nothing.  Still crashed.  Got Memtest and my memory looks really good.  It is (2) 4 GB sticks and Memtest came up with no problems at all.  Also took the computer into Fry's and had them test the MB and they said it is running very well.  (which for them is a good thing cause they like to tell you that things dont run well so that you will spend more money)

Also tested the Video card and it is performing very well.  No overheating and no "hiccups"

Im at a loss.  Thought you could be right about the RAM issue but alas, Im out of ideas.

[WonderGamer]

shadowdragon8190 wrote...

...I think we are EA's beta test group -.-. 

I was thinking the same thing.  I was just trying to keep myself from saying it, but you said it for me.  The problem with this thinking (if it's true) is that they are driving of their customers; this thread is proof of that. 

[wchen68]

Eurypterid wrote...

wchen68 wrote...

This patch has caused my Return to Ostagar DLC to malfunction. It's listed in my DLC menu and I have the offer files with them, but for some reason, I'm not allowed to travel to Ostagar while in game. Help anyone?

Did you go to Bann Loren's land first?

Yes I did. Is it presumable that this is a common problem then? What would you recommend that I do to fix the error?

[dragonsouce]

Memory fine I tried all the testing Memtest x86,Wish it was bad.Things drove me crazy.

Geforce 9800 gt SLI two cards.



There no reason It just crashes some systems others With identical stats are fine. Keeping thinking it's a bad codex or registry key that could not be upgrade/patched right. Or maybe a incompatible Codex/softwear?

[Quels]

There is one thing I really don't understand about all this Bioware / EA business - and I must admit I'm not very knowledgeable about these things - I understand that EA now more directly affects release dates, content, dlc, patches, economy etc. but are they really telling Bioware not to communicate with the player base as well?

If they have made this kind of restriction, what's the point of it? If they have not, why did Bioware suddently stop all communication?

[InebriatedPizza]

Maybe it's simple. Maybe they just don't have any idea what the cause of the problem is.



If you were in their position, it would be the choice between remaining silent or looking incompetent.

[DeadJediJamie]

InebriatedPizza wrote...

Maybe it's simple. Maybe they just don't have any idea what the cause of the problem is.

If you were in their position, it would be the choice between remaining silent or looking incompetent.

According to a Bioware rep, they have "a lead" on what the cause of the crashes might be, but as usual no ETA was given on when this might be fixed or when we'd hear more about the next patch.

[Koralis]

dragonsouce wrote...

Memory fine I tried all the testing Memtest x86,Wish it was bad.Things drove me crazy.
Geforce 9800 gt SLI two cards.

There no reason It just crashes some systems others With identical stats are fine. Keeping thinking it's a bad codex or registry key that could not be upgrade/patched right. Or maybe a incompatible Codex/softwear?

9800s use older shader technology.  DAO may not be working with those correctly.   Not that it's the ideal scenario (since bioware should be fixing the problem regardless), but upgrading to a 5850 would probably fix your problems and give you better image quality to boot.  (I run with super-sampled anti-aliasing... it's sweet.)

[Cloud Windfoot Omega]

Koralis wrote...

dragonsouce wrote...

Memory fine I tried all the testing Memtest x86,Wish it was bad.Things drove me crazy.
Geforce 9800 gt SLI two cards.

There no reason It just crashes some systems others With identical stats are fine. Keeping thinking it's a bad codex or registry key that could not be upgrade/patched right. Or maybe a incompatible Codex/softwear?

9800s use older shader technology.  DAO may not be working with those correctly.   Not that it's the ideal scenario (since bioware should be fixing the problem regardless), but upgrading to a 5850 would probably fix your problems and give you better image quality to boot.  (I run with super-sampled anti-aliasing... it's sweet.)

there have been people running with 58xx series with crashes,

guessing will not help PLUS you wont get better quality due to that card anyway, it only renders what information the game has to give it. and btw supersampleing has been around almost forever in computer time.

[Koralis]

Cloud Windfoot Omega wrote...

there have been people running with 58xx series with crashes,

guessing will not help PLUS you wont get better quality due to that card anyway, it only renders what information the game has to give it. and btw supersampleing has been around almost forever in computer time.

I read it as as a 9800.. ie ati radeon (I had one), not the later nvidia model.   Anyone can crash.  But a 5800 user could be crashing due to flakey memory, or bad sound drivers.  That doesn't mean that the 5800 is the problem, nor does it mean that a 9800 is NOT the problem.  That's why I had him check his memory.  He may also have a flakey sound card driver, he might have a virus screwing things over, etc, etc.   All I can say is that the 5850 win7 x64 card/driver is NOT a problem.  Upgrading doesn't neccessarily mean his problems go away, but it does mean that it definitely eliminates it as the problem.

A more interesting question is whether all Geforce 9800 SLI users have the problem?   No?  How about SLI users using a given motherboard?  Could be a bad SLI implimentation on a given motherboard, or Bioware assuming certain behavior that doesn't hold true with SLI cards.   Does he still have problems if he removes one of the cards?

You can't assume that all crashes have a single cause and then try to figure out whats common between all of them.  Given the large sampling of hardware, the answer is probably "no single common problem."  Trying to break it up into subsets is more productive.


And while supersampling has "been around forever", it was basically dropped a very long time ago as an inefficient method, and only resurfaced once the cards got powerful enough (vs screen resolution) to be able to make use of it.  As for the 5850 version of SSAA, when in this mode the driver automatically uses one level less of texture LOD.  It really does make a difference.


http://forums.anandt...d.php?t=2065654

Extremely lame. even 24x Edge detect MSAA looks like crap compared to 2x SSAA with a - LOD bias.
...
It pisses me off that I can max out Call of duty 4 Modern Warfare at 24x Edge detect AA on my 4890 and still have ~60-70 fps, but the image quality is worse than a 5870 with 2x SSAA.

Sure, I'm aware that you can use 3rd party tools like nHancer to tweak similar effects in the nvidia cards, but if you're doing that it's not officially supported and could be part of the cause of crashes, etc.  Either way, nvidia's SS isn't as good as the SS method that ATI is using now.


http://alienbabeltec...?p=12648&page=6

On the GTX285 I used 16xS, which contains 4x ordered grid super-sampling. With this the floor is improved over regular AF, but aliasing is still clearly visible. In particular, we still have widespread “bows” in the third horizontal section marked by white arrows.
With 2xSS on the 5770, you can see the results are vastly superior to 16xS, despite taking only half the super-samples. This is what I meant earlier when I said ordered grid wasn’t cost-effective relative to the quality it produces. We still have slight bow patterns in the two closest horizontal sections however, marked by white arrows.
With 4xSS, all of the bow patterns are gone, and we attain almost perfect image quality.

The article talks about texture blurriness, and adding your own LOD adjustments, but that article was written before the driver did it automatically

So, yes, he would get a graphic upgrade if he did it.  The main reason I was pointing that out was that even if it didn't stop the crashing, it's not as if it was totally wasted money. 

Modifié par Koralis, 23 mai 2010 - 04:15 .

[Edge12674]

For Windows 7 users here is an article that might give you some insight into what Bioware is dealing with.

itmanagement.earthweb.com/features/article.php/3866026/Developer-Windows-7-Maxes-Out-on-Memory-Use.htm

Don't get me wrong, the 1.03 patch messed up systems that were stable prior to the patch, but it might help explain why it is taking so long to lock this issue down! Microsoft is notorious for being slow in recognizing its shortcomings and slow as molasses in letting developers know what is really going on behind those "windows"!

Modifié par Edge12674, 23 mai 2010 - 04:38 .

[Cloud Windfoot Omega]

Koralis wrote...

Cloud Windfoot Omega wrote...

there have been people running with 58xx series with crashes,

guessing will not help PLUS you wont get better quality due to that card anyway, it only renders what information the game has to give it. and btw supersampleing has been around almost forever in computer time.

I read it as as a 9800.. ie ati radeon (I had one), not the later nvidia model.   Anyone can crash.  But a 5800 user could be crashing due to flakey memory, or bad sound drivers.  That doesn't mean that the 5800 is the problem, nor does it mean that a 9800 is NOT the problem.  That's why I had him check his memory.  He may also have a flakey sound card driver, he might have a virus screwing things over, etc, etc.   All I can say is that the 5850 win7 x64 card/driver is NOT a problem.  Upgrading doesn't neccessarily mean his problems go away, but it does mean that it definitely eliminates it as the problem.

A more interesting question is whether all Geforce 9800 SLI users have the problem?   No?  How about SLI users using a given motherboard?  Could be a bad SLI implimentation on a given motherboard, or Bioware assuming certain behavior that doesn't hold true with SLI cards.   Does he still have problems if he removes one of the cards?

You can't assume that all crashes have a single cause and then try to figure out whats common between all of them.  Given the large sampling of hardware, the answer is probably "no single common problem."  Trying to break it up into subsets is more productive.


And while supersampling has "been around forever", it was basically dropped a very long time ago as an inefficient method, and only resurfaced once the cards got powerful enough (vs screen resolution) to be able to make use of it.  As for the 5850 version of SSAA, when in this mode the driver automatically uses one level less of texture LOD.  It really does make a difference.


http://forums.anandt...d.php?t=2065654

newsflash i have a 5900, a 5870 and a 9800 and there is no to little diffrence in image quality in this game. they are also subject to the same problem.

[EivindTheChef]

My game crashes 9 out of 10 times when it comes to battling the sloth demon in the fade.

Every single time he changes from his Ogre form, the game stops responding, and I have to ctrl-alt-delete.

[Koralis]

Cloud Windfoot Omega wrote...

newsflash i have a 5900, a 5870 and a 9800 and there is no to little diffrence in image quality in this game. they are also subject to the same problem.

Newsflash.  that leaves your motherboard or something else in the system.  The OS isn't the issue, and neither is the 5870. 


And if you don't value good AA, then more power to you.  I do.   Different strokes.

[rage-monk]

WonderGamer wrote...

shadowdragon8190 wrote...

...I think we are EA's beta test group -.-. 

I was thinking the same thing.  I was just trying to keep myself from saying it, but you said it for me.  The problem with [...]

While having installed 1.03 makes me feel like a guinea pig, I believe we should consider what Edge12674 has pointed out about Windows' policy of keeping quiet about their fook-ups and if I'm not mistaken DA:O on PC is played by people with either XP, Vista or "7", which probably complicates things for BioWare. In addition they where probably under time pressure because of the Awakening compatibility stuff.

Anyways, for me stealing is broken and the longer I play, I have increasingly heavy performance hiccups to outright lagg. Tuning graphics (down) only affects how long it takes for the jerking to begin. Sound effects also get messed up after some time (random chatter is almost muted depending on where camera is or the direction I look).

My System:
ASRock P55pro with Intel i5 750 @ 2.67GHz & 4GB RAM
Windows 7 x64 Home Premium
ATI radeon HD 3870
Soundblaster X-Fi (pci-e)

As for Mods, I have 30-40 (morphs, tweaks, items, gameplay-alterations) activated. Not sure how that effects performance.

[Cloud Windfoot Omega]

[quote]Cloud Windfoot Omega wrote...

[quote]Koralis wrote...

[quote]Cloud
Windfoot Omega wrote...

newsflash i have a 5900, a 5870 and a
9800 and there is no to little diffrence in image quality in this game.
they are also subject to the same problem.

[/quote]


Newsflash. 
that leaves your motherboard or something else in the system.  The OS
isn't the issue, and neither is the 5870. 


And if you don't
value good AA, then more power to you.  I do.   Different strokes.

[/quote]do
you even reilize that it does not matter what AA setting you use?
anything 4x or higher your monitor wont be able to show therefore makes
no visiual diffrence byond the placebo effect

as for the
motherboard is it bad that i have 7 bad motherboards? or 7 bad PSU's or
18 bad memory sticks, or 6 bad sound cards?

theres an old saying.

STOP GUESSING

Modifié par Cloud Windfoot Omega, 23 mai 2010 - 08:45 .

[Cloud Windfoot Omega]

system double posted

Modifié par Cloud Windfoot Omega, 23 mai 2010 - 08:44 .

[J.Desanto]

If it hasn't already been mentioned I'd like to add that I can no longer talk to questgiving NPCs.

[Thandal N'Lyman]

Edge12674 wrote...

For Windows 7 users here is an article that might give you some insight into what Bioware is dealing with.

itmanagement.earthweb.com/features/article.php/3866026/Developer-Windows-7-Maxes-Out-on-Memory-Use.htm

Don't get me wrong, the 1.03 patch messed up systems that were stable prior to the patch, but it might help explain why it is taking so long to lock this issue down! Microsoft is notorious for being slow in recognizing its shortcomings and slow as molasses in letting developers know what is really going on behind those "windows"!

Dont' get *me* wrong!  While 1.03 has botched-up DA:O/A on a whole lot of our systems, (mine included) the nonsense reported by "Devil Mountain" (and carried in various outlets like the one in the above link ) about Windows memory usage does no one any good. 

The guy behind that "report", Randall Kennedy Barth [edited to correct], aka "Craig Barth", was fired from a well-respected IT publication because he was writing for them under the one name, and saying great things about, (as it turned out) *himself*, who was the owner of "Devil Mountain Software" under the other.  

The methods he used to "evaluate" memory performance under Windows had been obsolete and inaccurate ever since the kernel architecture changes introduced in VIsta. But he didn't even seem to realize it.  He was just trying to hype his own (badly coded) tools.

There are fairly complete histories of the entire story (including the announcements of the "termination of relationship" from the publication involved) in various places, including at:
 http://www.osnews.co..._from_InfoWorld

Just saying... 1.02a = stable with memory leak, 1.03 = CtD.  I'm looking to Edmonton, not Redmond, for a solution on this one!

Modifié par Thandal NLyman, 24 mai 2010 - 02:18 .

[john_boy]

Edge12674 wrote...

For Windows 7 users here is an article that might give you some insight into what Bioware is dealing with.

itmanagement.earthweb.com/features/article.php/3866026/Developer-Windows-7-Maxes-Out-on-Memory-Use.htm

Don't get me wrong, the 1.03 patch messed up systems that were stable prior to the patch, but it might help explain why it is taking so long to lock this issue down! Microsoft is notorious for being slow in recognizing its shortcomings and slow as molasses in letting developers know what is really going on behind those "windows"!

IIRC Win 7 uses something like GNU/Linux re memory management. It's intentional.

[gamer247]

SirPalamedes wrote...

Prevalent bugs:

Inventory Screen: weapon damage stats
Weapon damage will not update correctly on the inventory page when swapping weapons, activating abilities, etc. You must check the Character Record page for correct/updated values.

Pickpocketing
Picking pockets will no longer result in loot.  Pickpocketing an NPC with items will result in a "Success" message, but no loot will be added to your inventory. Pickpocketing for coin or for plot items still works.
-- It also appears that "stealing" can no longer be set as a tactic (useful for stealing in combat)
-- Something interesting to note is that the bug appears to kick in only after your character has first looted coins from an NPC. For instance, if your very first target has an item then you will loot it successfully, including subsequent targets; but as soon as you have looted coins from an NPC the bug appears to kick in and items can no longer be looted at all.

Lag and Crashes
Game slowdowns occur intermittently, often severely, which result in crashes for some. This lag occurs most often and is most severe when loading between cut-scenes, during combat, or when looting corpses. Loading to a new area or restarting the game will often delay the problem for a time.

-------------
Feel free to post other bugs which appear to be associated with Patch 1.03

[Koralis]

Cloud Windfoot Omega wrote...
do
you even reilize that it does not matter what AA setting you use?
anything 4x or higher your monitor wont be able to show therefore makes
no visiual diffrence byond the placebo effect

Do you even realize that you're totally wrong in what SS AA does?

AA improves the APPARENT resolution, by averaging in data from pixels that would not have been able to be shown.  That means that the number of pixels is constant, but the pixel COLORS are more accuate in representing the area .   The lower the resolution, the more useful it is.  at 1680x1050, I find 4x to be neccessary to avoid cringing.  8x is a very small improvement over 4x and not worth the added workload to the GPU at this resolution.  At 1024x768, 8x would probably be useful and since there are fewer actual output-pixels to render, not a problem for the card.

As for placebo, there are numerous articles with screenshots at various settings.  It's a real change.

as for the
motherboard is it bad that i have 7 bad motherboards? or 7 bad PSU's or
18 bad memory sticks, or 6 bad sound cards?

BS.  

I'll play along... I can "win" this arguement by noting that I have 30 gigabyte motherboards + 5870s and none have a problem, but all 10 of my systems with 9800s crash.  there... proof, and I win! *eyeroll*

Unbacked, and ridiculous, claims from annonymous people on the internet have absolutely no evidentiary value.


But lets suppose that you did have all of this hardware, that all has this problem, for the sake of discussion.  You assert that it's some magic bug that only afflicts people whose middle name starts with the letter M, and it has absolutely nothing to do with hardware and software on people's systems, is that about the size of it"?

No?  So... because software is deterministic, there must be SOMETHING about your system(s) that cause the problem, right?  And since you have so much hardware, you could certainly throw a spare hard drive into the cause by reinstalling Windows 7 and Dragon Age only, with no add-in cards, and virtually everything unneeded disabled, and see if it works"?  And then you could add hardware and software piece by piece until something breaks?

Naw... too much work.  It's so much more productive to simply complain that Bioware can't fix the magic bug than to help them figure out what the bug involves so that they can figure out what needs to be fixed.

theres an old saying.
STOP GUESSING

No.   It's called the scientific method, maybe you've heard of it.  Or maybe not, and that would explain a great deal.


http://en.wikipedia....ientific_method




1) observe the problem
2)  formulate a hypothesis (ie guess)
3)  test it.

repeat steps 1-3 to eliminate problems until you're left with something that tests true.



There's an older saying, "If you're not part of the solution, you're part of the problem."   I think it's safe to say that you're not part of any solution.

[Cloud Windfoot Omega]

Koralis wrote...

Cloud Windfoot Omega wrote...
do
you even reilize that it does not matter what AA setting you use?
anything 4x or higher your monitor wont be able to show therefore makes
no visiual diffrence byond the placebo effect

Do you even realize that you're totally wrong in what SS AA does?

AA improves the APPARENT resolution, by averaging in data from pixels that would not have been able to be shown.  That means that the number of pixels is constant, but the pixel COLORS are more accuate in representing the area .   The lower the resolution, the more useful it is.  at 1680x1050, I find 4x to be neccessary to avoid cringing.  8x is a very small improvement over 4x and not worth the added workload to the GPU at this resolution.  At 1024x768, 8x would probably be useful and since there are fewer actual output-pixels to render, not a problem for the card.

As for placebo, there are numerous articles with screenshots at various settings.  It's a real change.

as for the
motherboard is it bad that i have 7 bad motherboards? or 7 bad PSU's or
18 bad memory sticks, or 6 bad sound cards?

BS.  

I'll play along... I can "win" this arguement by noting that I have 30 gigabyte motherboards + 5870s and none have a problem, but all 10 of my systems with 9800s crash.  there... proof, and I win! *eyeroll*

Unbacked, and ridiculous, claims from annonymous people on the internet have absolutely no evidentiary value.


But lets suppose that you did have all of this hardware, that all has this problem, for the sake of discussion.  You assert that it's some magic bug that only afflicts people whose middle name starts with the letter M, and it has absolutely nothing to do with hardware and software on people's systems, is that about the size of it"?

No?  So... because software is deterministic, there must be SOMETHING about your system(s) that cause the problem, right?  And since you have so much hardware, you could certainly throw a spare hard drive into the cause by reinstalling Windows 7 and Dragon Age only, with no add-in cards, and virtually everything unneeded disabled, and see if it works"?  And then you could add hardware and software piece by piece until something breaks?

Naw... too much work.  It's so much more productive to simply complain that Bioware can't fix the magic bug than to help them figure out what the bug involves so that they can figure out what needs to be fixed.

theres an old saying.
STOP GUESSING

No.   It's called the scientific method, maybe you've heard of it.  Or maybe not, and that would explain a great deal.


http://en.wikipedia....ientific_method




1) observe the problem
2)  formulate a hypothesis (ie guess)
3)  test it.

repeat steps 1-3 to eliminate problems until you're left with something that tests true.



There's an older saying, "If you're not part of the solution, you're part of the problem."   I think it's safe to say that you're not part of any solution.

it is hardly scientific. when the fact is that more prople are experienceing this crash. and you being an exception hardly means its because everyone else has broken hardweare. wake up.

[Koralis]

it is hardly scientific. when the fact is that more prople are experienceing this crash. and you being an exception hardly means its because everyone else has broken hardweare. wake up.

the ones having the problem are the exception, not the rule.  There is bad hardware/software causing problems or else EVERYONE would have the problem like they do with pickpocketing.  That's a fact.  Wake up.   

Waving your hands in the air and professing helplessness doesn't help the problem get resolved.   Chasing off anyone that attempts to help people isolate the problem not only doesn't help, it's actually counterproductive. 

So, if you've got nothing useful to add, just ignore the thread please.

Modifié par Koralis, 24 mai 2010 - 02:58 .