Radeon Software Crimson Edition 16.4.2 - Crossfire Profiles available for: Elite Dangerous™
- Thread starter buyback
- Start date
I binned my crossfire setup, seriously, I was so about the experience that I gave one of my R9 290xs away for a birthday gift and bought 2 980tis to replace them. Threw the left over card in my HTPC. GTA V performance was actually worse with crossfire, most other games were a stuttering mess.
Sorry, I'm still a bit jaded by the experience.
Sorry, I'm still a bit jaded by the experience.
Not got a rift yet, but unfortunately the profile in the latest Crimson driver causes repeated crashes on my system (295X2) - not just in Elite - which go away if I disable crossfire.
Using catalyst 15.11 crossfire does work pretty well, if you set optimise 1x1 and disable frame pacing (thanks to the fellow forum user who pointed this out). GPU utilisation sits between 55 and 75% typically, so it does give a boost over 1 GPU. At 4K with 1x super sampling, FXAA and settings on high, I get 60 fps in space, 50-60 fps in and around stations, and typically 40ish in the SRV (although depending on the planet it can drop to 30). Of course I can get more frames if I reduce settings further.
Using catalyst 15.11 crossfire does work pretty well, if you set optimise 1x1 and disable frame pacing (thanks to the fellow forum user who pointed this out). GPU utilisation sits between 55 and 75% typically, so it does give a boost over 1 GPU. At 4K with 1x super sampling, FXAA and settings on high, I get 60 fps in space, 50-60 fps in and around stations, and typically 40ish in the SRV (although depending on the planet it can drop to 30). Of course I can get more frames if I reduce settings further.
Last edited:
I just created a restore point in case it goes south but I am going to install it and test with my 290x CF and CV1 tonight. I'll report back.
CMDR Guineapig
OK, installed the new drivers and tested out a few runs. Very fewif any stutters. Not sure it can be contributed to CF being active. Overall smooth and card # is running about 5c cooler than previous. Good enough for me. Now I need to experiment wit settings to see how far I an push it. Everything pretty much on high now with 1x SS.
I will be watching this with interest, as I am considering getting another AMD Fury card to Crossfire.
Installed the drivers, and they work flawlessly. There was an issue on installation that made me install and reinstall Windows a few times (after display driver installation, screen went black and couldn't use computer even after restart), but turns out that my Vive was the culprit.
Please note, if you update your drivers, and you own the Vive, disconnect the linkbox from your computer. After a whole night of wracking my brain as to why my computer suddenly went to sh*t (even after a new Windows install, as soon as Windows installed the generic video drivers, it happened), I figured out that for whatever reason, the Vive linkbox causes a conflict in the driver when you update drivers with it connected.
So... Disconnect linkbox before updating.
Now that I have everything up and running, the drivers are really, really great. And they even corrected a couple of minor artifacts and issues I was having with the Vive.
I run two 290Xs in Crossfire, and they run amazingly well. These are probably the cards that have lasted the longest before needing an upgrade. SteamVR performance test sits at 11.0 with both.
Also guys, take into account that crossfire in VR might run slightly different than crossfire on a regular monitor. It is believed that in the case of VR, each card is assigned to each eye on the VR headset. That is, one card per eye. So in a way, you are running a single card per side.
Please note, if you update your drivers, and you own the Vive, disconnect the linkbox from your computer. After a whole night of wracking my brain as to why my computer suddenly went to sh*t (even after a new Windows install, as soon as Windows installed the generic video drivers, it happened), I figured out that for whatever reason, the Vive linkbox causes a conflict in the driver when you update drivers with it connected.
So... Disconnect linkbox before updating.
Now that I have everything up and running, the drivers are really, really great. And they even corrected a couple of minor artifacts and issues I was having with the Vive.
I run two 290Xs in Crossfire, and they run amazingly well. These are probably the cards that have lasted the longest before needing an upgrade. SteamVR performance test sits at 11.0 with both.
Also guys, take into account that crossfire in VR might run slightly different than crossfire on a regular monitor. It is believed that in the case of VR, each card is assigned to each eye on the VR headset. That is, one card per eye. So in a way, you are running a single card per side.
Last edited:
I had the same problem - AFAICT during an update the AMD drivers detected the Vive as my primary monitor. Somehow that persisted after rebooting... As you say, generally a complete pain-in-the-ass to diagnose/fix.
![Faster than Jesus [VR]](https://forums-cdn.zaonce.net/data/avatars/m/58/58075.jpg?1553527111){kind=avatar}
I think there was a note with the 16.4.2 drivers to disconnect headsets before performing an update - could be something to do with that. Try uninstalling, safemode, driver cleaner.