AMD Crimson Drivers

[Damian]

Hi everyone,

I just went ahead with the update to Radeon Crimson 2015.1118.123.2413.
My system has a Radeon 280X and I'm using Windows 10 x64 latest release version.

Beta 1.5 works with DK2 and Oculus Rift SDK 0.5 installed. I've only had time to have a quick look and it would be interesting to see if this release has any impact on the supercruise issues.

Good luck to anyone else who decides to give the new drivers a shot.

 

[callezetter]

I quick test didnt get 0.5 running for me with the crimson drivers. But I have to test more.

And you did the TH2 update on win10 right?

 

[Damian]

Yes - I have TH2 installed. It initially broke everything but I was able to fix it by removing all monitor related entries from the registry and restarting.

 

[callezetter]

I dont mind working in the registry. Wich monitor data are you talking about?

 

[Damian]

Prior to update, I had the system set up so that turning on the DK2 would turn off my primary monitor and set the refresh rate to 75Hz. After updating, I was never able to get the system to detect the DK2 at all, either through the Oculus runtime or the multi-monitor display options. After wading through some old oculus forum entries relating to SDK 0.5, it looked like windows was automatically assigning a default monitor driver to the DK2. This driver would then fail and the DK2 would never start up.

So, I made up this procedure to clear up the registry. Please bear in mind that interfering with the registry as a system level user is extremely risky. I backed up my system before going through with this and had to restore it on my first attempt at the process. So please note that I most likely won't be able to help if you toast your Windows install. I did this on a backup machine that literally has only Elite, the DK2 and some other games installed on it.

1. Uninstall all Oculus software.
2. Download a utility called PSEXEC (which can be found on Microsoft's technet).
3. Open a command prompt as an administrator, navigate to the folder where you put psexec and run the command "PSEXEC -i -s -d CMD"
4. In the new command window type "regedit.exe".
5. Look for registry entires containing "OVR0003" and remove them. If a folder contained only references to the OVR0003 display, I also removed that folder.
6. Cross your fingers and restart the system.
7. Install SDK 0.5

After doing this, windows was able to detect the DK2 as a second display and I could configure it as before. I was also able to get windows to automatically switch to the DK2 when it is powered on and return to a monitor when it is switched off. I haven't tried the SDK switcher yet. Elite worked fine after I had set up the desktop to display on the DK2.

Again, good luck if you try this.

 

[buyback]

Sadly still stutters like hell in SC as soon as (NPC) ships start to spawn.

Back to Omega 14.12 again where SC Stutter is much less

 

[Damian]

Darn. Foiled again. I allowed myself a little hope since the SC issue wasn't listed in the release notes this time.

 

[callezetter]

Prior to update, I had the system set up so that turning on the DK2 would turn off my primary monitor and set the refresh rate to 75Hz. After updating, I was never able to get the system to detect the DK2 at all, either through the Oculus runtime or the multi-monitor display options. After wading through some old oculus forum entries relating to SDK 0.5, it looked like windows was automatically assigning a default monitor driver to the DK2. This driver would then fail and the DK2 would never start up.

So, I made up this procedure to clear up the registry. Please bear in mind that interfering with the registry as a system level user is extremely risky. I backed up my system before going through with this and had to restore it on my first attempt at the process. So please note that I most likely won't be able to help if you toast your Windows install. I did this on a backup machine that literally has only Elite, the DK2 and some other games installed on it.

1. Uninstall all Oculus software.
2. Download a utility called PSEXEC (which can be found on Microsoft's technet).
3. Open a command prompt as an administrator, navigate to the folder where you put psexec and run the command "PSEXEC -i -s -d CMD"
4. In the new command window type "regedit.exe".
5. Look for registry entires containing "OVR0003" and remove them. If a folder contained only references to the OVR0003 display, I also removed that folder.
6. Cross your fingers and restart the system.
7. Install SDK 0.5

After doing this, windows was able to detect the DK2 as a second display and I could configure it as before. I was also able to get windows to automatically switch to the DK2 when it is powered on and return to a monitor when it is switched off. I haven't tried the SDK switcher yet. Elite worked fine after I had set up the desktop to display on the DK2.

Again, good luck if you try this.

Thanks a lot for that writeup, ill give it a try. And Im fully aware what dealing with regedit can
do to your pc. No problem.

The worst thing that can happen is that I brick the install, and have to reset it. No big deal. I have learned from numerous other occasions to not have anything of importance on the main drive Win10 also makes it damn easy to reset, rollback or do a complete reinstall these days.

 

[Logical Viking]

In all my years of owning AMD cards I have never had one of the bad experiences we read of so often regarding their drivers. Today I am so angry I will probably jump to team green net time around...

I always uninstall and then sweep the old drivers in safe mode. Today was no different, downloaded the correct new AMD crimson, uninstalled, wiped and attempted to install... Installation locked up. Repeat process, hang again... several bad words and iterations of the process... Download the installer again, triple checking I had the right version... HANG.

Finally went back to the CCC 15.11.1 version... no problems.

Now I know why people complain about AMD so much.

 

[buyback]

In all my years of owning AMD cards I have never had one of the bad experiences we read of so often regarding their drivers. Today I am so angry I will probably jump to team green net time around...

Now I know why people complain about AMD so much.

I give them until next gen from Team green to cough up something or massive price slash on Fury cards but they will lose at least my market share when the CV1 is out and nothing changed. I'l guess its their last chance anyway.

 

[callezetter]

Weird, I had no issues at all installing the crimson drivers on win10 and 290x. Didnt wipe anything tho, just installed right over 15.11.

But i guess thats the problem, installers failing for no good reason on similar systems.

 

[callezetter]

Prior to update, I had the system set up so that turning on the DK2 would turn off my primary monitor and set the refresh rate to 75Hz. After updating, I was never able to get the system to detect the DK2 at all, either through the Oculus runtime or the multi-monitor display options. After wading through some old oculus forum entries relating to SDK 0.5, it looked like windows was automatically assigning a default monitor driver to the DK2. This driver would then fail and the DK2 would never start up.

So, I made up this procedure to clear up the registry. Please bear in mind that interfering with the registry as a system level user is extremely risky. I backed up my system before going through with this and had to restore it on my first attempt at the process. So please note that I most likely won't be able to help if you toast your Windows install. I did this on a backup machine that literally has only Elite, the DK2 and some other games installed on it.

1. Uninstall all Oculus software.
2. Download a utility called PSEXEC (which can be found on Microsoft's technet).
3. Open a command prompt as an administrator, navigate to the folder where you put psexec and run the command "PSEXEC -i -s -d CMD"
4. In the new command window type "regedit.exe".
5. Look for registry entires containing "OVR0003" and remove them. If a folder contained only references to the OVR0003 display, I also removed that folder.
6. Cross your fingers and restart the system.
7. Install SDK 0.5

After doing this, windows was able to detect the DK2 as a second display and I could configure it as before. I was also able to get windows to automatically switch to the DK2 when it is powered on and return to a monitor when it is switched off. I haven't tried the SDK switcher yet. Elite worked fine after I had set up the desktop to display on the DK2.

Again, good luck if you try this.

Ha! It worked I removed maybe 10-15 entries in the registry, rebooted and installed 0.5, and got back the DK2 image.

On the other hand positional tracking is lost atm But thats probably unrelated. Anyway, thanks again. Atleast i see Win10 TH2
in the DK2 again.

 

[xondk]

1. Uninstall all Oculus software.
4. In windows start menu, even windows 10 type: "regedit" without quotes, windows will find this, run that program which is built into windows
5. Look for registry entires containing "OVR0003" and remove them. If a folder contained only references to the OVR0003 display, I also removed that folder.
6. Cross your fingers and restart the system.
7. Install SDK 0.5

Summed it up for people, step 2 and 3 are not needed, PSEXEC is a telnet client if you wanted to do it remotely, CMD is also a built in windows function, opens command line interface. No external programs are needed.

Note to post below: This really shouldn't happen, was something that was left behind with vista, win 7 and above should have had this fix, but yes, this was more meant as a cautionary post since there's a lot of post around the net that point to third party programs to 'fix' something a built in function can fix, leaving many people to get various stuff onto their computers, fixed too many of those. But yes it seems the problem needs your solution in this case.

 

[Damian]

I had to elevate to a system user to remove some of the entries. When I tried to clean up the settings as an administrator I ran into problems on rebooting. It probably varies between installs.

 

[xondk]

I had to elevate to a system user to remove some of the entries. When I tried to clean up the settings as an administrator I ran into problems on rebooting. It probably varies between installs.

Post edited to reflect this.

 

[z4StormShadow]

I noticed that you can make your own resolutions now with the crimson drivers. Has anyone tried to get the DK2 to have 1440p in ED? I tried to type in 2440x1440 but it didn't take. I think I have to do something else. If you click on MORE at the top right of the crimson menu, you'll see a cut down version of CCC and in there are the settings to change.