6 Replies Latest reply on Sep 27, 2016 6:19 PM by fenrir0wulf

    Monitor Identity

    fenrir0wulf

      Copied from the Radeon system info

      Radeon Software Version - 16.9.2

      Graphics Chipset - AMD Radeon (TM) R9 380 Series

      Windows Version - Windows 10 (64 bit)

      System Memory - 24 GB

      CPU Type - AMD FX(tm)-8350 Eight-Core Processor

       

      Monitors

      Samsung Syncmaster 2333 - DVI

      LG 24M35 - DP to DVI or HDMI w DVI adapt (Doesn't matter same problem)

      Samsung S22C450 - DVI

       

      So the monitor IDs are inconsistent between the AMD drivers and Windows. Windows reads the GPU ports in the order DP HDMI DVI-D (bottom) DVI-I (top). The advanced Radeon settings read the same. But the normal driver does not. The Radeon interface reads in the order DVI-D DVI-I DP HDMI.

      Screenshot of my destop with all identities shown is provided.screen.png

      In center blue is the advanced interface, in the bottom corner is the windows display and in the top corner is the normal Radeon interface.

      Note: When I took the picture, I had the SyncM on HDMI to make the screenshot make a bit more sense since the actual ID order I run is 2-1-3 as the LG is my main display, being in the center.

       

      Unfortunately, I've only had 3 monitors for a shot time so I cannot say if the problem was present on older versions of the drivers.

      So because the IDs don't match between the driver and windows, this is causing the very few programs that support multiple separate displays that I have to simply get borked, or worse, not even work anymore when trying to use said option. And yes, this issue is what's causing them to not work properly. If I disconnect a monitor to align Windows and the driver IDs they work perfectly fine.

      Now I will admit that I'm pretty much close to just putting a second card to just get done with it but... I shouldn't have to. This is clearly a bug that shouldn't be there. And it's not even the fact that I use adapted cables or adapters that cause the problem (even though the DP or HDMI port are used on the card, the driver will still read DVI because it's the monitor's port. Meaning the driver reads all tree monitors as DVI ports, regardless of the output used). As noted in my screenshot, the cable used were all on their own and the HDMI port was still IDed improperly.

       

      So how would I fix this? Besides a second card.

        • Re: Monitor Identity
          fenrir0wulf

          Well, I connected my second card.

          IT'S EVEN WORSE.

          screen2.png

          None of them match up now.

          Windows and Advanced say the LG is 2 but Radeon says 3.

          Radeon and Advanced say the S22 is 1 but Windows says it's 3.

          And ALL of them say something different for the Syncmaster.

          For the record, my second card is a Sapphire R7 240, my first is an ASUS Strix R9 380.

          Is connected on the cards, in order top to bottom, all on DVI only, without any adapters, LG, Syncmaster and S22C450.

           

          So then, I swap the two top, getting SyncM - LG - S22, which is the order I want.

          screen3.png

          Finally, Radeon and its own advanced settings agree with each other.

          But they still don't match up with Windows.

          This is clearly not something I can fix on my end. At this point I'm literally doing the job AMD should've done before: Testing. Which clearly was not even remotely done. I am just seething with rage at the incredible incompetency on broad display here.

          How do I make a 3 screen setup that works?????

            • Re: Monitor Identity
              Hardwood

              I have 3 monitors 1 2333 like yours on DVI, a Dell ultrasharp on DP and a Samsung tv on HDMI. and they all line up with windows.

              did you hook yours up with the two samsung using dvi-dvi and the LG on HDMI to HDMI i.e no adapters.

              When you've done that uninstall the display driver using DDU, restart and install the latest driver. See what happens.