1560 réponses à ce sujet

[BTCentral]

Kayden SiNafey wrote...

Okay guys I got the offical word from Bioware from Luke Barret to who'm I have been PM! You are not going to believe this WE ARE ALL RIGHT and a little wrong here's what he has to say.

However, Tesselation, and other “Very High” features than those two extra checkboxes will not turn on on a DX10 card.

For the record, all I was ever disagreeing with was that Tessellation could be used in DX10 mode - you'll notice that when looking at any of my posts, so no "little wrong" here

Anyhow - good to know that this is all cleared up once and for all.

Withidread wrote...

A bit of news from the Nvidia forums.

1st: "The next driver release will give better performance with DA2 over 267.59."
forums.nvidia.com/index.php


2nd: "It was pushed back to early April. For major driver releases, we generally release a beta driver followed by a minor WHQL driver update about 2 weeks later."
forums.nvidia.com/index.php


Edit: You'll probably have to scroll up one post in that first link.

Great to hear, any more performance nVidia can push our way is more than welcome

Modifié par BTCentral, 23 mars 2011 - 01:42 .

[Kayden SiNafey]

BTCentral wrote...

Kayden SiNafey wrote...

Okay guys I got the offical word from Bioware from Luke Barret to who'm I have been PM! You are not going to believe this WE ARE ALL RIGHT and a little wrong here's what he has to say.

However, Tesselation, and other “Very High” features than those two extra checkboxes will not turn on on a DX10 card.

For the record, all I was ever disagreeing with was that Tesselation could be used in DX10 mode - you'll notice that when looking at any of my posts, so no "little wrong" here

Anyhow - good to know that this is all cleared up once and for all.

Well you just gave me gun (metephorically speaking) and now I'm going to use it

BTCentral wrote...
Thanks ../../../images/forum/emoticons/smile.png - but you're fighting a loosing battle there, he'll just refuse to listen and state it's "not a fact".
He just does not understand the fact that DX10 hardware can not process DX11 only API features ../../../images/forum/emoticons/tongue.png

(from another post)

The simple version? Direct X 11 only allows cards to use features
supported by the hardware. If a Card is DX11 if can make use of all the
features. If it is DX10.1 it can use DX10.1, 10.0 and 9 features. If it
is DX 10 it can use DX10 and 9 features. And finally if it is DX9 it
could only use DX9 features (in which case they may as well just be
using a DX9 renderer).

With what you say there you are saying NO Dx11 features will run on a DX10 card. Also you are saying you are 100% right where that is not the case. Even by the bioware tech blog it says "An optional visual feature for players with DirectX 11 hardware is our new diffusion depth of field effect." It doesn't say it can run in DX10 mode yet it can be enabled from the answer that Luke got. I may have been making Tessellation my prime candadite but I did itterate (not all the time) that it could be the other features and it was proven to be correct.

Lesson here is don't give some one a gun unless you know where there going to point it.

We were all right and all wrong can we all just accept that and move on?

EDIT:  Anyways here is the pic I said would get incase you didn't believe me and here it is, if you want an uncut I can do that to.

http://i127.photobuc...ionwithluke.jpg

Modifié par Kayden SiNafey, 23 mars 2011 - 01:54 .

[BTCentral]

Kayden SiNafey wrote...

Well you just gave me gun (metephorically speaking) and now I'm going to use it

BTCentral wrote...
Thanks ../../../images/forum/emoticons/smile.png - but you're fighting a loosing battle there, he'll just refuse to listen and state it's "not a fact".
He just does not understand the fact that DX10 hardware can not process DX11 only API features ../../../images/forum/emoticons/tongue.png

The simple version? Direct X 11 only allows cards to use features supported by the hardware. If a Card is DX11 if can make use of all the features. If it is DX10.1 it can use DX10.1, 10.0 and 9 features. If it is DX 10 it can use DX10 and 9 features. And finally if it is DX9 it could only use DX9 features (in which case they may as well just be using a DX9 renderer).

Lesson here is don't give some one a gun unless you know where there going to point it.

We were all right and all wrong can we all just accept that and move on?

Actually no - SSAO/High Quality Blur are not DX11 specific API features, they've been used in DX10 games for years.
DX11 API features can not be used on DX10 cards. Fact. So yes - what I said is still correct.

BioWare chose to enable the tick boxes when Very High was selected - I would imagine because they assumed that DX10 hardware was not going to handle it well (even my DX11 hardware handles it fairly poorly at the moment, but that may well change with later nVidia drivers/software patches).

Anyhow, as you said. The discussion is over, time to move on.

Modifié par BTCentral, 23 mars 2011 - 01:56 .

[Kayden SiNafey]

BTCentral wrote...

Kayden SiNafey wrote...

Well you just gave me gun (metephorically speaking) and now I'm going to use it

BTCentral wrote...
Thanks ../../../images/forum/emoticons/smile.png - but you're fighting a loosing battle there, he'll just refuse to listen and state it's "not a fact".
He just does not understand the fact that DX10 hardware can not process DX11 only API features ../../../images/forum/emoticons/tongue.png

The simple version? Direct X 11 only allows cards to use features supported by the hardware. If a Card is DX11 if can make use of all the features. If it is DX10.1 it can use DX10.1, 10.0 and 9 features. If it is DX 10 it can use DX10 and 9 features. And finally if it is DX9 it could only use DX9 features (in which case they may as well just be using a DX9 renderer).

Lesson here is don't give some one a gun unless you know where there going to point it.

We were all right and all wrong can we all just accept that and move on?

Actually no - SSAO/High Quality Blur are not DX11 specific API features, they've been used in DX10 games for years.
DX11 API features can not be used on DX10 cards. Fact. So yes - what I said is still correct.

BioWare chose to enable the tick boxes when Very High was selected - I would imagine because they assumed that DX10 hardware was not going to handle it well - but they are still not Direct X 11 features.

Anyhow, as you said. The discussion is over, time to move on.

But Bioware says they coded it for DX11 ONLY for Very High not DX10 or for High thus it is being forced. The point I have been advocating is that DX11 only features are or could be running on DX10 hardware. Thats a fact proven by Bioware that I will happen.

Your right it is over and you were wrong so again I was proven right that at least one of you guys would not change your mind even with the proof right in front of you.

Modifié par Kayden SiNafey, 23 mars 2011 - 02:07 .

[nayrbth]

Dragon Age 2 will stop working and I'll det a message saying that the driver amdkmdap stopped working... how do I fix it?

[BTCentral]

Kayden SiNafey wrote...

But Bioware says they coded it for DX11 ONLY for Very High not DX10 or for High thus it is being forced. Thats the fact.

I am not arguing that it can be forced on when using High if you change the you manually change the INI though, but as most people that buy the game are not going to be looking through the settings.ini as far as they would be aware with a DX10 card it would be off.

It's disabled by default - so unless they manually changed it there is no way to easilly turn it on (unless they are using a DX11 card of course).

Technically they didn't say they coded it for Direct X 11 only, but rather that it was "an optional visual feature for players with Direct X 11 hardware" - which it normally would be as DX10 players can not enable it without manually changing the INI.

At the end of the day something that can only be enabled on DX10 cards through the use of an INI hack is not going to be supported by BioWare.

nayrbth wrote...

Dragon Age 2 will stop working and I'll det a message saying that the driver amdkmdap stopped working... how do I fix it?

That's a graphics card driver crash. If you are not already try using the ATI preview driver.

Modifié par BTCentral, 23 mars 2011 - 02:26 .

[MaxPayne37]

Kayden SiNafey wrote...

I was saying that DX11 features could be turned on and that is was more then likely Tessellation was causing the problem for poor FPS, well I was wrong about the Tessellation. However, by the same token so were you guys saying that none of the DX11 features could be turned on with a DX10 card which they said they could under the right circumstances. This would also mean Tess might have still been enabled when I went to High and the same could be said for your guys pics.

You guys remember me telling you ppl had features enabled when they shouldn't have been? Well this is what lead me down this path and left me with such a hard line because I could do it myself.

I am very glad we got this answer back because now we all now know it is indeed possible to turn on DX11 features on a DX10 card and cause performance issues and advocate for ppl to change their settings in game and not through the launcher or the ini anymore or it could put them in these situations.

I appreciate all of your guys input we did butt head and get something accomplished to get ppl the right the answer and I know it has been rocky but in the end we were all right how often does that happen?


EDIT: I did send Luke the info about the thread and etc so some one should post here like he said. Also if you want me to take a screen shot and post it I will,  just in case there is any skepticism in the crowd.

You're talking about .ini changes that are not supported through the game or launcher, and as such, shouldn't be used for the regular DA2 user anyways. To do so would be their own fault, and as the game itself doesn't allow you to change these options, this should be null and void, as people doing this are doing this at their own discretion, knowing full well it isn't supported in the game options.

And it's not a DX11 feature if it's just blocked out of the game settings, but can be enabled with a .ini hack. Case in point, the first Crysis and its "DX10 only" features, which were hacked so it could run on DX9. Obviously they weren't "DX10 only" if they could do so. Tessellation for example, can not be enabled on DX10 cards, because it is a DX11 feature, however the other features that can be enabled via .ini would be DX10 features as well, just "labelled" as DX11 ones, kind of like Crysis did. In that case, they probably disabled them because DX10 cards can't handle those features well, but they would be DX10 features nevertheless, and not DX11 ones if they actually can be enabled.

Modifié par MaxPayne37, 23 mars 2011 - 06:08 .

[TallBearNC]

Kayden SiNafey wrote...

Okay guys I got the offical word from Bioware from Luke Barret to who'm I have been PM! You are not going to believe this WE ARE ALL RIGHT and a little wrong here's what he has to say.

Luke Barrett
12:20 PM 2011-03-22

Alright, here is the answer(s) I got (melted in to one response):

With dx10 hardware the very high setting should be disabled
preventing the dx11 features like teselation from being enabled. There
are [however] some inconsistencies if you edit the ini file manually:



On my DX11 card I was able to enable everything in very high, then
exit the game, and change settings to GraphicsDetailLevel=2 in the ini
file. When I restarted, Diffusion DOF was on even though I was not in
very high mode. (until I opened the settings window, which fixed it)



So, I expect, if you turn on diffusion dof and high quality blur in
the ini file and you have a dx10 card, it will actually turn on in game.

However, Tesselation, and other “Very High” features than those two extra checkboxes will not turn on on a DX10 card.



Ie:

EnableHighQualityBlur=1

EnableDiffusionDOF=1

In the ini file will make a dx 10 card run slower.

GraphicsDetailLevel=3

Will do nothing

If you give me a link to that thread I'll happily flex my Bioware
tag with this response. Hopefully it will clear things up a bit.

I was saying that DX11 features could be turned on and that is was more then likely Tessellation was causing the problem for poor FPS, well I was wrong about the Tessellation. However, by the same token so were you guys saying that none of the DX11 features could be turned on with a DX10 card which they said they could under the right circumstances. This would also mean Tess might have still been enabled when I went to High and the same could be said for your guys pics.

You guys remember me telling you ppl had features enabled when they shouldn't have been? Well this is what lead me down this path and left me with such a hard line because I could do it myself.

I am very glad we got this answer back because now we all now know it is indeed possible to turn on DX11 features on a DX10 card and cause performance issues and advocate for ppl to change their settings in game and not through the launcher or the ini anymore or it could put them in these situations.

I appreciate all of your guys input we did butt head and get something accomplished to get ppl the right the answer and I know it has been rocky but in the end we were all right how often does that happen?


EDIT: I did send Luke the info about the thread and etc so some one should post here like he said. Also if you want me to take a screen shot and post it I will,  just in case there is any skepticism in the crowd.

you still cant NOT turn on dx11 features on a DX10 card... even if the game "lets" you turn them on, it will be 100% IGNORED by the DX11 rendering system. DX 11 does NOT support emulation of *any* kind on a DX10 card using DX11 features... I have verified this by running the game on 2 nvidia 8800s and manually editing the ini file. Just as I said, the game ignores it.

However, if the game rendered them on the CPU via software emulation, that would be possible... and that would cause massive CPU use (which isn't being done)

However, with a DX11 card, and editing the ini file as well as the configuration xml file, you could set DX11 features to manually be on or off at any detail level. Again, only with a DX11 card. I suppose you could edit the lower end detail levels to also use DX10 effects with a DX10 card as well...

With a DX10 card, it doesn't matter what DX11 features you chose.. they will be IGNORED by the DX11 rendering system in windows itself, and the game doesn't have software emulation to run them on the CPU

The problem with the game is BW doesn't give us enough Adv Graphics configuration.. it's mostly hardcoded into detail levels. There should be another detail level: CUSTOM. And under custom there's 3 sections for DX9, 10, and 11 where the gamer and turn on and off every feature that their DX level has to offer... that would really be the best way to do it imo

Modifié par TallBearNC, 23 mars 2011 - 02:40 .

[MaxPayne37]

TallBearNC wrote...

you still cant NOT turn on dx11 features on a DX10 card... even if the game "lets" you turn them it, it will be 100% IGNORED by the DX11 rendering system. DX 11 does NOT support emulation of *any* kind on a DX10 card using DX11 features...

However, if the game rendered them on the CPU via software emulation, that would be possible... and that would cause massive CPU use (which isn't being done)

so yes, with a DX11 card, and editing the ini file as well as the configuration xml file, you could set DX11 features to manually be on or off at any detail level

With a DX10 card, it doesn't matter what DX11 features you chose.. they will be IGNORED by the DX11 rendering system in windows itself, and the game doesn't have software emulation to run them on the CPU

Exactly, the effects that can be .ini enabled would just be allowed to do so because they would be DX10 effects masqueraded by the game as DX11 ones, and that's where Kayden's confusion is drawn from.

EDIT: Also note Kayden, that Luke did say "So, I expect" to the same scenario on a DX10 card, which denotes that he doesn't know for sure in that case.

Modifié par MaxPayne37, 23 mars 2011 - 06:05 .

[TallBearNC]

MaxPayne37 wrote...

TallBearNC wrote...

you still cant NOT turn on dx11 features on a DX10 card... even if the game "lets" you turn them it, it will be 100% IGNORED by the DX11 rendering system. DX 11 does NOT support emulation of *any* kind on a DX10 card using DX11 features...

However, if the game rendered them on the CPU via software emulation, that would be possible... and that would cause massive CPU use (which isn't being done)

so yes, with a DX11 card, and editing the ini file as well as the configuration xml file, you could set DX11 features to manually be on or off at any detail level

With a DX10 card, it doesn't matter what DX11 features you chose.. they will be IGNORED by the DX11 rendering system in windows itself, and the game doesn't have software emulation to run them on the CPU

Exactly, the effects that can be .ini enabled are just allowed to do so because they are DX10 effects masqueraded by the game as DX11 ones, and that's where Kayden's confusion is drawn from.

I read his convo with Luke, and luke says what we are saying, but Kayden is misinterpreting somethings luke said. Luke said you CAN turn DX11 features on in the game on a dx10 card by editing the ini file... but he did NOT say they would actually work...

Edit: removed the will do nothing section of my post (see below posting)

Modifié par TallBearNC, 23 mars 2011 - 03:12 .

[MaxPayne37]

They would not be DX11 features per se, just marketed as such, due to being able to turn them on, POSSIBLY, on a DX10 card through a .ini tweak. If they were true DX11 effects, you couldn't just enable them that way.

And in the screenshot, the "Will do nothing" comment refers to the "GraphicsDetailLevel" variable.

Modifié par MaxPayne37, 23 mars 2011 - 06:05 .

[TallBearNC]

Deleted.... I got what luke meant by Will do nothing.. he meant Graphics Level =3 does nothing if u ahve a DX10 card

Modifié par TallBearNC, 23 mars 2011 - 03:11 .

[TallBearNC]

For those wondering what the ini file entry EnableLatentQueries does.. I did some digging.. it's part of the umbra 3rd party dll for SSAO that DA2 uses.. I got the definition from one of umbra's websites.. Tweaking this setting may or may nor help performance.. turning it on suggests a performance boost (when using SSAO) at the risk of possible, unwanted effects.

************

Latent Queries
The timing of occlusion queries may have a significant effect on Occlusion Booster performance. Three timing modes are supported: latent, latent (high quality) and immediate occlusion queries. The sample has implementations for immediate and latent occlusion queries and they can be toggled at runtime (see Controls).
When using immediate occlusion queries, Occlusion Booster uses occlusion query results on the same frame as they've been issued. This feature enables Occlusion Booster to do artifact free rendering. In some cases immediate occlusion queries can introduce GPU stalls if the application's CPU and GPU usage are not carefully synchronized. However, it's entirely possible to use immediate occlusion queries without extra GPU stalls if the rendering thread can quickly feed the GPU with rendering calls after the query results have been read back.

*When using latent occlusion queries Occlusion Booster uses occlusion query results from the previous frame. This may result in rendering artifacts since objects that have become visible during a given frame are drawn one frame later. This can be observed as visible popping of objects. The amount of rendering artifacts can be reduced by using high quality latent queries.s

The utilization of Occlusion Booster's internal data structures depends on the timing mode. Changing the timing mode can change the order in which commands are issued, the set of objects reported visible and the amount of occlusion queries issued may also vary.

When running the samples with latent queries and wireframe mode enabled, you may observe that occluded objects occasionally flicker, indicating a false positive result in determining object visibility. This is expected behavior due to performance tradeoffs in the algorithms employed by Occlusion Booster.

Modifié par TallBearNC, 23 mars 2011 - 03:42 .

[Viscera1969]

I have no clue if other people with this on again off again lagging issues with 60 or higher frams dropping right down to 0 frams in a blink of an eye, but i made a discovery last night a couple of my programs stopped working to the point that it seems fishy so i did just a malware scan with malware bytes pro which i got off of google, any way it picked up 1 or 2 things i got rid of them and bang my programs were back to normal and then i went into dragon age 2 to lag around town again and after about 10 minutes i realized i had not lagged in all that time so i got excited and pushed my setting as far as they could get with dx-9 and another 20 minutes went by no lag. Ok i thought lets go for broke turned on DX-11 and bumped setting even higher thats with AA and ATPC all the up and i had a nice 35 to 65 fps lowered AA and ATPC a couple notches and the frames went up a little more. on DX-9 fps went thru the roof all as high as it will allow, but bottom line do a malware scan and see if u got a little bit of the plague messing with your APPS. It was a freak discovery but it is one that had me just playing for 5 hours (OMG) of lag free fun and adventures. I mean what would you have to lose by doing a malware scan besides just maybe get lucky like me and lose that lag....

Hey Bioware devs or whom it may concern. you may want to look into this and warn people to do a malware and perhaps other protecting scans virus and other wise....

good luck to all...

[Kayden SiNafey]

I guess you can't argue with crazy even with the proof right in front of your eyes. I should have knowen better but thanks guys for further killing the hope that I have that ppl can be better or admit when their wrong.

EDIT: You guys are focusing on one detail between all of my statements when it isn't the whole of what I said. I said the game was running DX11 only features on DX10 cards, granted I was wrong about Tess and I have admited to this because of the API here I'll say it again you were RIGHT. Now the game was supposed to have DX11 features not accesable for DX10 cards but you can trigger them to turn on. It wasn't perfect and NO WHERE did I say it was but you guys weren't 100% right either. You guys ego's need to get in check because your just pointing out one thing and not the whole truth of what I was saying and now what Bioware is telling you.

Modifié par Kayden SiNafey, 23 mars 2011 - 04:26 .

[MaxPayne37]

Kayden SiNafey wrote...

I guess you can't argue with crazy even with the proof right in front of your eyes. I should have knowen better but thanks guys for further killing the hope that I have that ppl can be better or admit when their wrong.

EDIT: You guys are focusing on one detail between all of my statements when it isn't the whole of what I said. I said the game was running DX11 only features on DX10 cards, granted I was wrong about Tess and I have admited to this because of the API here I'll say it again you were RIGHT. Now the game was supposed to have DX11 features not accesable for DX10 cards but you can trigger them to turn on. It wasn't perfect and NO WHERE did I say it was but you guys weren't 100% right either. You guys ego's need to get in check because your just pointing out one thing and not the whole truth of what I was saying and now what Bioware is telling you.

Unfortunately you're right, we can't argue with your craziness because you refuse to see the proof right in front of your eyes.

One BioWare rep saying he "expects" it will be the same on DX10 hardware, is not proof. Like I said in my post above, they're POSSIBLY pulling the old Crysis 1 trick, if those .ini effects work on DX10 cards. This time instead of supposed "DX10 only" features that obviously weren't, it's "DX11 only" features, that obviously weren't. A DX10 card can't pick and choose which DX11 features to have, and not to have, like tessellation, hence why it's not a DX11 card!! It wouldn't be a DX11 only feature if it could run on older hardware.

Once again, real DX11 only features cannot run on DX10 hardware, it's a physical impossibility. What may be marketed as DX11 only features are not if they can be used on older hardware in any way. You have to learn that, get passed the "trick", and get it through your head.

http://blogs.msdn.co...nouncement.aspx

DirectX 11 will have better compatibility with DirectX 10 hardware than most expected. What does that mean? Yes, there is some confusion over the "11 running on 10 hw" part of the announcement.

There are parts of the new API that are hardware independent, those can indeed run downlevel. The mult-threaded resource handling, for instance, can be enabled to run on DirectX 10 class hardware if the IHVs ( ATI, Intel, nVidia ) update their DirectX 10 drivers. Think of that part of it as "11 on 10".

Then there are parts of the new API that do require new hardware support and will only run on DX11 class hardware. The hardware tesselator and Shader Model 5.0 are examples of those parts.

Modifié par MaxPayne37, 23 mars 2011 - 06:03 .

[KyiMin]

Hopefully a beta or whql nvidia driver will be released on the 24th.

[Kayden SiNafey]

MaxPayne37 wrote...

Unfortunately you're right, we can't argue with your craziness because you refuse to see the proof right in front of your eyes.

Well I guess the referee or dad just needs to step in because you know what I see it like this now because now were just bickering and I've conceded to some of your points but your not looking at mine even with what Bioware said backing me up. I will help those who are willing to listen and if I need to contradict you guys again and show you the error of your ways again, then the person who needs help will need to make up their own minds.

Have fun kids.

KyiMin wrote...

Hopefully a beta or whql nvidia driver will be released on the 24th.

Indeed now that the 590 has been pushed back.

Modifié par Kayden SiNafey, 23 mars 2011 - 05:46 .

[woloif]

will you two please stop your not making any sense anymore

[TallBearNC]

Kayden SiNafey wrote...

I guess you can't argue with crazy even with the proof right in front of your eyes. I should have knowen better but thanks guys for further killing the hope that I have that ppl can be better or admit when their wrong.

EDIT: You guys are focusing on one detail between all of my statements when it isn't the whole of what I said. I said the game was running DX11 only features on DX10 cards, granted I was wrong about Tess and I have admited to this because of the API here I'll say it again you were RIGHT. Now the game was supposed to have DX11 features not accesable for DX10 cards but you can trigger them to turn on. It wasn't perfect and NO WHERE did I say it was but you guys weren't 100% right either. You guys ego's need to get in check because your just pointing out one thing and not the whole truth of what I was saying and now what Bioware is telling you.

See above in bold? wrong.. wrong .. and WRONG....

Again, you can set whatever you like in the ini file,  but DX11 *specific* effects have NO EFFECT on the DX10 cards. ONLY DX10 effects can run on DX10 cards. It dont care what the game is set to do... Windows/DX11 will just ignore any settings by the game for DX11 effects if a DX11  card is not present. Personally, I don't even think it gets that far. From what I can see, the game itself will ignore them as the game is checking for DX10 and DX11 hardware
 
DX 11 will NOT use dx11 specific effects on a dx10 card no matter what you set the game at... end of story.. it's not possible unless the game used the CPU to "software emulate" those features - which is does not. So the game can NOT provide any features "normally not accessable by DX10 cards" as you stated above. 

However if you have a DX11 card, you can trigger DX10/11 effects at ANY detail level of the game if you set them up in the ini file

Kayden.. feel free to point this EXACT post out to Luke or another BW dev, and they will 100% confirm what I am telling you

this isn't about ego.. it's about your fundimental lack of knowledge and confusion.. the performance issues are simple..

1) game needs patching
2) ati and nvidia need better drivers
3) the game needs a CUSTOM detail setting where we can manually toggle on/off each DX9,10,and 11 effect vs just basic detail levels... example: maybe someoen wants every DX11 effects but no shadows what so ever because they have a lower end DX11 card.. and shadows take quite a big slice of GPU time. And the disable shadows in the ini file has no effect

The end.

Modifié par TallBearNC, 23 mars 2011 - 06:15 .

[MaxPayne37]

Kayden SiNafey wrote...

Well I guess the referee or dad just needs to step in because you know what I see it like this now because now were just bickering and I've conceded to some of your points but your not looking at mine even with what Bioware said backing me up. I will help those who are willing to listen and if I need to contradict you guys again and show you the error of your ways again, then the person who needs help will need to make up their own minds.

Have fun kids.

Doesn't look like you read the rest of my post, and the actual PROOF presented.

You go ahead and have fun, just please stop giving other people false information is all.

TallBearNC wrote...

this isn't about ego.. it's about your fundimental lack of knowledge and confusion

QFT, but it seems like he doesn't read our posts, or process the information given. He has nobody else that supports his point of view, but lots of others that support ours with proof that he refuses to acknowledge. I don't know what else to say...

Modifié par MaxPayne37, 23 mars 2011 - 06:18 .

[Sandyman]

Dragon age was working fine for a bit. No problems, everything ran great on ultra.

Yesterday I had to rollback my ATI drivers to 10.8, because of a problem with Total War Shogun 2. Shogun 2 now runs like a charm, but Dragon age 2 now crashes during cutscenes. The screen would freeze, I would still hear the characters talking, screen would go black(and brown once), and then I would have to alt tab out. I would get the windows "programs has stopped working" error as soon as I hit desktop.

I also recently got the 1gb Texture pack, but the crashing started after I reinstalled my ATI graphics(which at the time, I never had the texture pack).

My Specs:
Processor: Quad Core 2 Q6600 @ 2.40 GHz
RAM: 4 GB DDR 2
System: Win 7 64 bit
Graphics Card: ATI Radeon 5870

Is there no other way to fix this without having to use the latest drivers for ATI? It's Bloody well sophie's choice, I want to play both games(dragon age 2 and Shogun 2), Am I really damned if I do, and damned if I don't???

I have also brought this up with Creative Assembly, the creators of shogun 2.

[TallBearNC]

Sandyman wrote...

Dragon age was working fine for a bit. No problems, everything ran great on ultra.

Yesterday I had to rollback my ATI drivers to 10.8, because of a problem with Total War Shogun 2. Shogun 2 now runs like a charm, but Dragon age 2 now crashes during cutscenes. The screen would freeze, I would still hear the characters talking, screen would go black(and brown once), and then I would have to alt tab out. I would get the windows "programs has stopped working" error as soon as I hit desktop.

I also recently got the 1gb Texture pack, but the crashing started after I reinstalled my ATI graphics(which at the time, I never had the texture pack).

My Specs:
Processor: Quad Core 2 Q6600 @ 2.40 GHz
RAM: 4 GB DDR 2
System: Win 7 64 bit
Graphics Card: ATI Radeon 5870

Is there no other way to fix this without having to use the latest drivers for ATI? It's Bloody well sophie's choice, I want to play both games(dragon age 2 and Shogun 2), Am I really damned if I do, and damned if I don't???

I have also brought this up with Creative Assembly, the creators of shogun 2.

You need the latest nvidia and/or ati drivers to properly play DA2. Hopefully both nvidia and ATI will soon release a decent driver set so one version works best with all the game in the meantime, I'd pick with a game and stick with it... then alter your drivers to fit the game you're playing

[TallBearNC]

Quite an odd thing has happened.. and it's really too late tonight for me to look into it (it is 3:40am my time right now)... I applied a mod that lets you run 2Xs as fast out of combat... suddenly I noticed my FPS was a LOT higher.

Normally I run on VERY high, No AA, AFx16, No SSAO, No Diffusion DOF, No Blur @ 2560x1600 and I avg about 30-35fps with my rig.. once I applied this mod, I'm now getting 50-55fps out of combat and about 30-35fps combat... I'm too sleep to look into the possible causes as to why a mod to speed run speed would give me such a huge jump in FPS... I did remove the mod... and my fps dropped back to what it was before.. I put it back in.. and boom major fps boost

I have no idea what the mod does to speed up the runspeed.. but everything seems sped up.. moving the camera, turning, etc are all accellerated. The mod goes back to normal speed during combat for "balance issues"

Here is a link to the mod:

www.dragonagenexus.com/downloads/file.php

it would be great if some people could test this and reproduce what I am seeing here. If this really does boost out of combat FPS, then that would suggest a lot of the performance issues has to do with the game itself.

I'm litterally about to fall asleep so I can't look into this further tonight

Modifié par TallBearNC, 23 mars 2011 - 07:56 .

[Sandyman]

Thanks for the reply TallBear. I suppose Im gonna stick with shogun for now since I did the rollback, would be a waste to change the drivers again, guess I will jsut have to beat Shogun, then reinstall latest drivers so I can finish Dragon Age 2.

On another note, I am interested to see if that MOD does increase frame rate, anything to boost framerate would be good(plus double speed outside of combat makes me hard lol). I would test it out, but seeing as I am having driver problems at the moment, I will have to wait and see what other people experience from it.