Any word yet on when this game is going to get optimized for CrossFire (if at all...) ?

+

Guest

Guest
Any word yet on when this game is going to get optimized for CrossFire (if at all...) ?

As most crossfire users probably know, the game when played in xfire mode is still mostly unplayable due to the extreme stuttering and screen tearing, problems that games which have been properly optimized for xfire don't have at all (e.g. Tomb Raider).

Have CDPR said anything about whether they plan on improving crossfire support, or are they just going to completely ignore this issue ?

Edit: Here is an insightful post taken from The Witcher reddit (not my post) that provides some more information about the problem that I am referring to here.

----
Despite 15.7, crossfire is still a stuttering mess in Withcer 3. Does Nvidia users/other AMD users have the same problem? (frametime analysis inside) (x-post /r/AdvancedMicroDevices)

Thought i would fire up crossfire again after 15.7 patch, but no dice. I specifically bought my second R9 290 card for Witcher 3, but i haven't benefited from it yet, which is annoying. Even with freesync, it is stuttering to an unplayable degree (for me).

Specs:

i5-4670k

12gb DDR1600

2x XFX R9 290

ASROCK z87 extreme4 (running PCI-E 3.0 8x/8x in CF and 3.0 16x in single)

All test are run with 15.7 driver and Freesync enabled (which works with CF now) Let's start with a game that has been criticized for it's optimization; Far Cry 4

Frametimes in Far Cry 4

Single Card http://i.imgur.com/4x0YHc9.png
Crossfire http://i.imgur.com/tfxJ7vn.png

Here we see quite a bit more stuttering (unstable framtimes), but the experience in-game is not THAT noticeable. I would definitely prefer the higher frame rate, over the reduction in stuttering in this case.

Now let's try with a game that actually has decent optimization for AMD; Metro: Last Light. I have to mention here, that i forgot to turn tessellation to "high" on the single card, so the performance difference doesn't look as dramatic as it is with the same settings.

Frametimes in Metro: Last Light

Single Card http://i.imgur.com/4qFjjva.png
Crossfire http://i.imgur.com/nyQyoUl.png

A minor increase in stuttering that is absolutely unnoticeable in-game. I was very surprised there was any difference at all, since it felt completely smooth.

Now let's look at Witcher 3

Frametimes in Witcher 3

Single Card http://i.imgur.com/zhDRiRm.png
Crossfire http://i.imgur.com/Oz61Am9.png

Look at it... LOOK AT IT!! It looks like a fucking seismometer when your mom walks by. It is absolutely unplayable for me.

How does yours look? Here is how you test it:

Download Fraps
Download Fraps Bench Viewer
Open Fraps and navigate to "FPS" and set a benchmarking hotkey, and check ONLY the "Frametime" mark.
Open game
When fully loaded press your benchmark key and fuck around a bit
Press the benchmark key again.
Open Fraps Bech viewer
Drag in the relevant log.
Right-click and save chart.
Post here
----
(end of post)
 
Last edited:
Someone please correct me if I'm wrong, but the vast majority, if not all, Crossfire support comes from the drivers. It's on AMD to improve that with the profiles that are included in the driver packages, not CDPR.
 

Guest

Guest
Well, it's funny that on the AMD sites I get the absolute opposite of your response, that CDPR needs to improve their code to better utilize CrossFire -,- So we're just pushing blame here and not getting anywhere.
 
Its definitely AMDs thing. (and NV when we are talking about SLI)

You have game code, the API, and the hardware. The code tells the API what to make the hardware do.

In all situations this is (supposed to be) the same - standardised code telling standardised APIs what to do, which then executes on standardised hardware. (this is how they can make games that run on the 100 million different system configs out there - standards)

You do not have standardised hardware. AMD is trying to trick the API into thinking its rendering to one target (because thats what the API expects) then doing driver trickery in the BG to make it render on two or more, and that is where problems come in.

It is therefore 100% AMDs lookout to make it work, since it is their non-standard hardware that is causing problems with standard code and APIs.
 

Guest

Guest
alright, it is beginning to make sense. well, in that case all we can do is hope that win 10 brings some noticeable API improvements, and that AMD at some point manage to get their stuff right...-,-
 
Top Bottom