Crossfire

Yep, need an Crossfire profile in the graphics driver to supplement the game. Can only hope it's coming soon from AMD...
 
Yep, need an Crossfire profile in the graphics driver to supplement the game. Can only hope it's coming soon from AMD...

I haven't got a problem, everything's working fine on my home build PC. Crossfires working perfectly and I'm getting 60fps
 
Oh it works, in that it runs pretty smoothly (and can hit 60fps). But what fps do you get if you disable crossfire? Afterburner shows my GPU utilisation staying between 30% and 40% only, for both processors; I also get more fps in single GPU mode with vsync off. Try it and see.
 
Last edited:
I haven't got a problem, everything's working fine on my home build PC. Crossfires working perfectly and I'm getting 60fps

Snap. I am using two AMD 7970 cards with the new drivers and everything is running fine. Only problem I have is that sometimes the landing pad numbers vanish and I can't land till they show up again. Not sure if this is a Crossfire problem or a bug in the game.
 
Snap. I am using two AMD 7970 cards with the new drivers and everything is running fine. Only problem I have is that sometimes the landing pad numbers vanish and I can't land till they show up again. Not sure if this is a Crossfire problem or a bug in the game.

I'm not running dual GPU and have seen this issue.
 
I'm running an R9 290 Crossfire rig and I when I enable a CCC profile to force Crossfire, I set it to 1:1.

Game runs like crap. Lots of stutter- almost unplayable near stations.

Tried disabling Crossfire altogether (i.e. not just on the system, but for the E:D profile too). Frames jump 20-30% at least (can't see FRAPS in my OR DK2).

Frontier, you design a game that works beautifully with Oculus Rift, knowing that OR requires a mad powerful computer build, and then ... fail to support Crossfire.

I really hope there is a good reason for this. I have seen absolutely nothing whatsoever from anyone at Frontier even mentioning that Crossfire may (again, I am told ... it apparently worked once?) work at one point in the future. No comment either way (i.e. 'we're going to implement it' vs 'we have no plans to implement it').

I have been using dual GPUs now for the better part of ten or twelve years; this is not a new technology.

Not supporting it just ... leaves me speechless.
 
I'm running an R9 290 Crossfire rig and I when I enable a CCC profile to force Crossfire, I set it to 1:1.

Game runs like crap. Lots of stutter- almost unplayable near stations.

Tried disabling Crossfire altogether (i.e. not just on the system, but for the E:D profile too). Frames jump 20-30% at least (can't see FRAPS in my OR DK2).

Frontier, you design a game that works beautifully with Oculus Rift, knowing that OR requires a mad powerful computer build, and then ... fail to support Crossfire.

I really hope there is a good reason for this. I have seen absolutely nothing whatsoever from anyone at Frontier even mentioning that Crossfire may (again, I am told ... it apparently worked once?) work at one point in the future. No comment either way (i.e. 'we're going to implement it' vs 'we have no plans to implement it').

I have been using dual GPUs now for the better part of ten or twelve years; this is not a new technology.

Not supporting it just ... leaves me speechless.
it's supported and working.

triple screen and DK2, no problem here and better scaling now than a few versions back...
 

Yaffle

Volunteer Moderator
Gedemon, what profile are you using for the crossfire mode?

In crossfire I get max 30% use on both cards, but FPS lingers at about 45-50 (bar stations). Never goes above that. Not a cooling issue, I'm a waterboy and the cards are about 27C.
 
All 4 GPU cores are working fine for me around 43% usage on each core. crossfire is working just fine for me. Sorry, quadfire
 
Last edited:
Gedemon, what profile are you using for the crossfire mode?

In crossfire I get max 30% use on both cards, but FPS lingers at about 45-50 (bar stations). Never goes above that. Not a cooling issue, I'm a waterboy and the cards are about 27C.

default profile, frame pacing on, still on 14.10.1006 drivers (catalyst 14.4)

ultra settings@5760x1080 in planetary ring:
CF enabled = ~55-60fps
CF disabled = ~35-40fps

Screenshot_0018.jpgScreenshot_0019.jpg

To answer your question I've also monitored a small session in the asteroid field shown in the screens (long enough for the card to go at full heat), but monitoring seems to create a bit of stuttering (the peaks in frametime) that didn't occurs usually.
Untitled.png

btw CF dosn't work on my computer in any windowed modes or when using a video capturing software like OBS.
 
I'm "Stuck" it seems with a Mac Pro 2013, running in Bootcamp. Apple/AMD have ensured that Catalyst drivers will no longer work with the Pro. So your stuck with their Bootcamp drivers, which seem to be out of step with Catalyst.

I have a 2560x1440 display res, so near top in terms of requirements, but its no 4K...

When I enable Crossfire and use Afterburner to monitor it, I can see that of my 2 GPUs that #1 is idle. Its heat is lower, and it has 0% activity.

GPU2, is running generally between 60% in space and 100% in a spacestation. I've overclocked it slightly, but Im not seeing any real benefit from it.

In space I can get 120fps, but in a spacestation this usually drops to 25-29fps.

You can see that having Crossfire actually work, would bring some benefit in space-stations, though in space the single GPU is doing fine.


BTW, I think the holy grail for me, would be to run my setup with 2x or 4x Supersampling set in the Gfx Options. But I think its actually rendering at 2x resolution and then downsampling. That being the case, even 2x would be rendering at 5120x2880 and thats a tall order. IF however you had decent Crossfire grunt with that, it might be possible to get a decent framerate.
 
Last edited:
Back
Top Bottom