Ce sujet est fermé
They're waiting for the console validation most likely.
And how long can that take?
Wouldn't be too surprised if they are just being spiteful and holding it back...right now, I am starting to expect that kind of behaviour. I think it's time we take this to twitter...
Considering that this fandom includes a bunch of very huge ****s I probably would do too.
Nah, i believe this is clearly a case where they were unprepared for this kind of reaction. If there were still zero rumor of a patch, I'd agree with you that something drastic were necessary.Wouldn't be too surprised if they are just being spiteful and holding it back...right now, I am starting to expect that kind of behaviour. I think it's time we take this to twitter...
Nah, i believe this is clearly a case where they were unprepared for this kind of reaction. If there were still zero rumor of a patch, I'd agree with you that something drastic were necessary.
Hopefully, some uber-nerd with an 'I told you so' mentality already had a proper pc control scheme saved on his laptop and they are implementing it in the first patch.
Wishful thinking, my friend....but I like it!
Have to say though, nothing is more aggravating than this silent treatment we are getting. Think I've wasted enough time with this.
Peace out.
Nah, i believe this is clearly a case where they were unprepared for this kind of reaction. If there were still zero rumor of a patch, I'd agree with you that something drastic were necessary.
Hopefully, some uber-nerd with an 'I told you so' mentality already had a proper pc control scheme saved on his laptop and they are implementing it in the first patch.
You sure they don't just try to implement the controls from that PC twitch stream, because that sure was different enough from now. Makes you wonder if they were already experimenting with it at the time.
And how long can that take?
Anything between a week and never.
Anything between a week and never.
How very reassuring. Optimism is dead I see.
Of course they were.You sure they don't just try to implement the controls from that PC twitch stream, because that sure was different enough from now. Makes you wonder if they were already experimenting with it at the time.
How very reassuring. Optimism is dead I see.
It's how console validation works. They have to submit their patches for validation and if sony or microsoft are not happy with something it's back to square one, and since there is a crapton of games to fix validation takes time. The other problem though, is why the fùck do we have to wait for consoles, there is no validation on PC, for no good reason whatsoever bioware wants to patch every platform at the same time.
Interesting, I have that screen disturbance too once in a while, but only in DA:I. I'm using Mantle Crossfire.The screen flicker was due to my faulty DVI cable it seems, I bought a new DisplayPort cable, have been playing the game without a single screen flicker or tear for 4 hours straight… never thought a cable could give me all those problems.
Of course they were.
If there's one thing that should be painfully obvious to anyone who has played pc games before, it's that the PC control scheme for DAI was allotted the smallest amount of time and resources possible this summer. It was clearly a secondary priority.
It was NOT designed on the PC as the lead platform, and it's difficult to dispute that it was obviously the most cost beneficial. They released on 5 platforms, and 4 of them use the console interface.
Problem is they spent so much time testing and programming with controllers, when time got short, they cut corners. There's no other explanation, because the current scheme is clearly not "better".
One could argue that EA is also at fault here, they are the ones who decide when the game has to come out. Didn't Bioware have to beg EA to give them more time during the developement?
With maybe a little bit more time they could have done better.
2014 Microsoft and Sony still aren't capable of releasing content in a day that is not Tuesday. And of course we PC players have to suffer for their asinine policies.
So, the same engine that crashes for so many people in case of DAI also works better in case of BF4 with win8 than with win7 - and it's not about fps, it's about some kind of "stuttering", ie poor coding.
Maybe some devs just should test their games on more than 1 pc, eh?
Both BF4 and DAI use the Frostbite 3.0 engine. Frostbite 3.0 supports DX 11.1 optimizations but the problem is DX 11.1 is not (and will never be) fully backported to Windows 7. This is the main reason the game runs better in Windows 8.x systems. The same is mostly true for Battlefield too. There is no magic here.
One could argue that EA is also at fault here, they are the ones who decide when the game has to come out. Didn't Bioware have to beg EA to give them more time during the developement?
With maybe a little bit more time they could have done better.
Well, in terms of the gamebreaking bugs, quest bugs, campaign related issues, etc, those are things they should have expected, as should we, because in a game this complex and big, there's no way they could have found everything in house. Or tested on all possible pc configurations, with all possible software people have running.
This is where a beta would have helped, however, how do you let people play a beta of a story-based game? That's not cost effective either.
No, the fault in terms of the pc control scheme lies, IMHO with the design team. They made a conscious decision to leave it till after getting the console controls in place. They painted themselves into a corner, and that's why you see things like poorly designed menus, no native mouse support, etc.
Both BF4 and DAI use the Frostbite 3.0 engine. Frostbite 3.0 supports DX 11.1 optimizations but the problem is DX 11.1 is not (and will never be) fully backported to Windows 7. This is the main reason the game runs better in Windows 8.x systems. The same is mostly true for Battlefield too. There is no magic here.
Yea, but you're talking percentage points better. 1-2 fps better.
Definitely not worth upgrading an entire OS.
I'll wait for Windows10.
Both BF4 and DAI use the Frostbite 3.0 engine. Frostbite 3.0 supports DX 11.1 optimizations but the problem is DX 11.1 is not (and will never be) fully backported to Windows 7. This is the main reason the game runs better in Windows 8.x systems. The same is mostly true for Battlefield too. There is no magic here.
Funnily enough I only had the game crash once and stuttering also isn't much of an issue in cutscenes (well 30fps aside). And I'm running this on a i7-4710MQ with a GeForce GTX 860M.
Also Windows 7 Ultimate.
Well, in terms of the gamebreaking bugs, quest bugs, campaign related issues, etc, those are things they should have expected, as should we, because in a game this complex and big, there's no way they could have found everything in house. Or tested on all possible pc configurations, with all possible software people have running.
This is where a beta would have helped, however, how do you let people play a beta of a story-based game? That's not cost effective either.
No, the fault in terms of the pc control scheme lies, IMHO with the design team. They made a conscious decision to leave it till after getting the console controls in place. They painted themselves into a corner, and that's why you see things like poorly designed menus, no native mouse support, etc.
Yeah I guess that's true too.
Anyone tweeted Darah on the status of the current patch?
So what do I do about it?
Change the display cable?
The thing is, this does not happen in any other game, mantle or non-mantle game, is that normal if it's a dp 1.2 cable?
These are my pc-specs:
Operating System: Windows 8.1 64-bit
ASUS Crosshair V Formula-Z, Socket-AM3+
ATX, 990FX+SB950, DDR3, 4xG2-PCIe-x16, SLI/CFX, US
Processor: AMD FX™-8350 Eight-Core Processor. (8 CPUs), ~4.0GHz watercooled.
Kingston DDR3 HyperX Beast 32GB
2400MHz 4x8GB KIT CL11 HyperX Beast
Sapphire Radeon TRI-X R9 290X 4GB "OC" ß Two of these cards in crossfire and watercooled!
SATA 6 Gb/s (SATA3.0), 500MB/400MB/s read/write, w
WD VelociRaptor 1TB
10000RPM, 64MB, 3.5", SATA 6GB/s (SATA 3.0)
Cooler Master V1200, 1200W PSU
ATX 12V V2.31, 80 Plus Platinum, Modular, 12x 6+2p
Asus 24" LED VG248QE 144Mhz monitor
Nah, your cable is probably fine. Go into MSI Afterburner and make sure ULPS is turned off, and turn power limit all the way up to 50% (if you don't have afterburner, here is the link http://www.guru3d.co...download.html). You can do that in Sapphire Trixx as well if you are using that, but Afterburner is a better way to go.
If you still get that flicker, lower your voltage, memory, and clock speeds down to their stock (leaving power limit maxed out and ULPS off).
If that doesn't work, then start looking at the cable, making sure it's under 6' long and a certified display port cable.
My rig is almost identical to yours with two 290x cards under water with a DP 1.2 cable and every game has a different limit for what I can overclock my cards to before I start having issues with the flickering like that. Some games will let me run at 1100 mhz at +25 mV while others will flicker and pop all over the place at those settings. Dragon Age was particularly nasty about it for me and I ended up having to leave the voltage at stock and only running a 1060 mhz clock speed.
It's an issue with the Display Port technology, the signal strength from the GPU's (both AMD and Nvidia) have problems sometimes, and they really hate overclocking. It's a growing pain of new tech no one seems to know how to fix. The only way to eliminate it is to use an HDMI cable which doesn't mess up no matter the overclock on the cards, but then you lose the extra bandwidth and gimp the hell out of your monitor.
Funnily enough I only had the game crash once and stuttering also isn't much of an issue in cutscenes (well 30fps aside). And I'm running this on a i7-4710MQ with a GeForce GTX 860M.
Also Windows 7 Ultimate.
Yeah I guess that's true too.
Anyone tweeted Darah on the status of the current patch?
November 27ths seems the most recent. His response:
https://twitter.com/...339072117207040
.@LebowSarah trying to get one out as fast as possible and follow up as we fix / add other things.
Interesting, I have that screen disturbance too once in a while, but only in DA:I. I'm using Mantle Crossfire.
I'm going to test my DVI-cable to see if that's indeed the cause.
By the way did you find a fix yet for that flickering moon?
I experience that too. But for some reason when I played it yesterday it was a 'stable' moon for once. The next time I loaded up the game it was flickering again... Don't know what I did differently...
We'll know right away from his feed as well as @dragonage
Yea, but you're talking percentage points better. 1-2 fps better.
Definitely not worth upgrading an entire OS.
I'll wait for Windows10.
I never implied it's worth upgrading an entire OS over 1-2 games, I was merely trying to explain why some people on certain configurations (especially multi-GPU ones) are getting a better experience with much less issues on Windows 8. Just because you and me and X other people aren't having problems, it doesn't mean it won't affect other systems. Anyway the game is extremely GPU limited and badly optimized at that, especially for Nvidia owners.
More to the point of the patch, console validation is really the worst excuse ever. Ubisoft released AC:Unity a week prior to DA:I (another trainwreck of mostly technical issues) and the game has already received not one or two but three patches already and a 4th one is in the works. Bioware has released zero.
Nah, your cable is probably fine. Go into MSI Afterburner and make sure ULPS is turned off, and turn power limit all the way up to 50% (if you don't have afterburner, here is the link http://www.guru3d.co...download.html). You can do that in Sapphire Trixx as well if you are using that, but Afterburner is a better way to go.
If you still get that flicker, lower your voltage, memory, and clock speeds down to their stock (leaving power limit maxed out and ULPS off).
If that doesn't work, then start looking at the cable, making sure it's under 6' long and a certified display port cable.
My rig is almost identical to yours with two 290x cards under water with a DP 1.2 cable and every game has a different limit for what I can overclock my cards to before I start having issues with the flickering like that. Some games will let me run at 1100 mhz at +25 mV while others will flicker and pop all over the place at those settings. Dragon Age was particularly nasty about it for me and I ended up having to leave the voltage at stock and only running a 1060 mhz clock speed.
It's an issue with the Display Port technology, the signal strength from the GPU's (both AMD and Nvidia) have problems sometimes, and they really hate overclocking. It's a growing pain of new tech no one seems to know how to fix. The only way to eliminate it is to use an HDMI cable which doesn't mess up no matter the overclock on the cards, but then you lose the extra bandwidth and gimp the hell out of your monitor.
We'll know right away from his feed as well as @dragonage
I honestly don't follow Twitter at all. That why I was asking anyway.
More to the point of the patch, console validation is really the worst excuse ever. Ubisoft released AC:Unity a week prior to DA:I (another trainwreck of mostly technical issues) and the game has already received not one or two but three patches already and a 4th one is in the works. Bioware has released zero.
Users are also experiencing alot of new crashes and freezes with those patches. Rushing them out ain't a good option IMO
I never implied it's worth upgrading an entire OS over 1-2 games, I was merely trying to explain why some people on certain configurations (especially multi-GPU ones) are getting a better experience with much less issues on Windows 8. Just because you and me and X other people aren't having problems, it doesn't mean it won't affect other systems. Anyway the game is extremely GPU limited and badly optimized at that, especially for Nvidia owners.
More to the point of the patch, console validation is really the worst excuse ever. Ubisoft released AC:Unity a week prior to DA:I (another trainwreck of mostly technical issues) and the game has already received not one or two but three patches already and a 4th one is in the works. Bioware has released zero.
DX11 has issues with some flickering surfaces in crossfire mode. I quote from the 14.11.2 beta driver release notes:It was actually the cable. I bought a new displayport cable and switched to it from my dvi cable, and now the game works like a charm, except in mantle mode though, so I'm playing in directx 11 mode with everything on max!
Never overclocked anything
AMD is currently working with BioWare to resolve the following issues:
◾Flickering is sometimes observed in Dragon Age: Inquisition on a limited number of surfaces in AMD CrossFire™ configurations.
Retour en haut