6 réponses à ce sujet

[WilderDK]

Definitely having much worse performance with this patch. Stuttering while exploring, pause for 1-2 sec random every 1- 2 min after patch?? why not test the patch before release?? im sick of this gaming industry how the **** people over and over again

 

Did not have any problems before patch now??? hmmmmm its like it have gone allot worse in graphic as well, and its stuttering and something have change in the way things look........wth happen ??

 

way to go for another developer there **** things up.

[KneeTheCap]

I had this problem prior the patch, it was remedied by lowering the mesh setting from ultra to high and lowering the shadowplay's settings from very high to medium (I have no idea if it has a connection to the stutter or not, but it did go away after fiddling with the settings)

 

And if your game looks worse after the patch than before, you need to add a parameter to your game. In Origin, right click the game and choose properties, there add this line to the command section thingamaton

 

-ShaderSystem.ShaderQualityLevel <the same as your ingame mesh setting>

 

so if your mesh setting ingame is set on high, you add this line

-ShaderSystem.ShaderQualityLevel High

 

This should remove the graphics error until they release a hotfix for it.

[Itkovian]

The funny thing is, whenever a patch is released for _any_ game on PC, you'll always get posts like this. Patches fix things for the vast majority of users, but there's always some who messed up, and end up posting on forums saying the patch sucks and wasn't tested.

 

So to be clear: the patch WAS tested. It just happens they didn't test it on your computer. Welcome to PC gaming.

 

Still, I admit it sucks to be the unlucky one (been there in other games, hopefully updating drivers and such will fix your issue).

[finc.loki]

The funny thing is, whenever a patch is released for _any_ game on PC, you'll always get posts like this. Patches fix things for the vast majority of users, but there's always some who messed up, and end up posting on forums saying the patch sucks and wasn't tested.

 

So to be clear: the patch WAS tested. It just happens they didn't test it on your computer. Welcome to PC gaming.

 

Still, I admit it sucks to be the unlucky one (been there in other games, hopefully updating drivers and such will fix your issue).

So the shiny hair and other things that affect literally EVERYONE was not tested then.

[devSin]

I've seen quite a few reports of this. In my brief time with the patch, I haven't experienced anything like it.

I would recommend posting about this at the EA Answers forum (there were actually already several threads when I looked last night). Apparently there are agents that monitor that forum and pass issues along to the developers (sad as it is, it's likely not going to be seen by anybody who can do anything about it if you just post it here).

[Bear43]

The hair thing was something that was overlooked, obviously, and it may have been done for a reason. However, when it comes to something like what the OP stated then there is a big thing to remember: In PC gaming there is an absolutely enormous possibility in hardware configurations. It is absolutely impossible for any company to test something on every single possible configuration. So, for the majority it works okay but then there comes along one oddball configuration that can cause other issues like this.

 

Also, tone it down on the whole "The developer's ****** us again!" crap. I'm a software developer myself and in my company we test everything the best we can but customers can hit things that were never expected. If you think you can do it better, then prove it. Seriously, go into game development and show us all. Until then, quit acting like the developer's primary mission is to make your life miserable. Keep in mind that no one is forcing you to play the damn game, either.

[Captain Wiseass]

So the shiny hair and other things that affect literally EVERYONE was not tested then.

The bit of code causing the shiny hair was originally supposed to fix a problem that happened on low settings. I imagine they tested it on low settings, but not on the higher ones. A pretty big "whoops", but not what some people have made it out to be.