search

terrymacdonald / DisplayMagician

DisplayMagician is an open source tool for automatically configuring your displays and sound for a game or application from a single Windows Shortcut.
https://displaymagician.littlebitbig.com
GNU General Public License v3.0
452 stars 19 forks source link

Possible issue within multiple graphic adapters #44

Closed dev1981 closed 2 years ago

dev1981 commented 3 years ago

Latest Version of DisplayMagigcan does not show the displays connected within a second display adapter. (in my case DisplayLink USB Graphics within USB docker).

Expected behaviour All displays are shown

Screenshots 1.1.4: https://www.dropbox.com/s/jpe9j683n726j2y/magic-1_1_4.jpg

latest: https://www.dropbox.com/s/oi3bj7r7j2oruvq/magic-latest.jpg

terrymacdonald commented 3 years ago

@dev1981 This is the issue I was dreading :). And it's not going to be quick fix.

The new video display libraries used in DisplayMagician v2.0.1 are completely different to the ones used in DisplayMagician v1.1.4. The earlier DisplayMagician used a combination of NvAPIWrapper and WindowsDisplayAPI (which are both great software) but it also restricted the amount of information available within DisplayMagician. This meant that things like HDR, primary displays, bezel sizes and similar weren't properly recorded by DisplayMagician, and weren't stored. Additionally, AMD devices weren't supported at all.

Now, in DisplayMagician v2.0.1, I've created my own custom video display libraries. This was done to ensure that I would have full control over the codebase, so that I could update and fix any issues that were found. I created the NVIDIALibrary, AMDLibrary and WinLibrary components, and they operate in the following fashion:

This is how the video card detection logic works, and it seems to work ok for single cards. I took the design decision that each type of video card detected would result in the relevant 'video mode' being applied, e.g. if an NVIDIA video card was detected then DisplayMagician would be in 'NVIDIA' mode, and the NVIDIA driver would be used.

Your problem is because that assumption I had early on in the design process is wrong :(.

So what to do? I'm going to need some time to figure this out. This is a huge and complex set of changes, and I'm going to need to be bang on with any changes I make. I also need to be aware of ensuring any changes don't impact the general array of users (those with a single video card or from a single manufacturer).

I think I'll end up restructuring the video detection logic and the video manipulation logic to handle working with multiple brands of video cards, but that in turn opens up a raft of additional issues e.g. which ones take priority, how does the WinLibrary know which screens are handled by the NVIDIA driver. This is not going to be a simple fix :(.

On that note, are you happy to do some testing for me for a future release @dev1981? This will potentially be a month long odyssey testing multiple builds and attempts to fix the issues. You'll also need to run some tests for me and provide configurations until I'm sure I fully understand what's going on. Are you willing to provide that help?

I really hope so, as it's my mission to make sure that DisplayMagician works for as many people as possible, and is as simple to use as possible. I get a real kick out of that.

As a first step, can you please perform the following:

I'll review the data you've provided, and that will help me get a handle on what's happening.

Thanks Terry

dev1981 commented 3 years ago

Hi Terry, Thx for ur quick answer. Sure i will try to help u testing. as far as i can . I attached the logs and my profiles. The profile folder does contain as well my old profiles from the previous version. DisplayMagician.zip .

Best Regards

Adrian

terrymacdonald commented 3 years ago

Woah @dev1981, this just got stranger.... DisplayMagician asks windows for a list of PCI video cards, and uses that list of PCI vendor IDs to figure out what's in the system. And Windows is saying that DisplayLink USB Graphic is NOT in the list.

I'm going to have to first fix the USB device detection logic, even before I can start the video library updates to be able to use all three drivers at once (NVIDIA, AMD and Windows CCD). This is definitely a BIG piece of work that will last a few weeks, and will probably result in a 2.1.0 'minor' release version bump.

So for confirmation, is this the product you're using?: https://www.synaptics.com/products/displaylink-graphics/downloads/windows

I need to know so I can start to piece together some idea of what's happening, and figure out a fix for it. My git feel is that I need to add a USB based video card detection process as well as the existing PCI one, and then move on to combining video card driver use after that. But getting confirmation of product is a good start.

Oh , can you also tell me how you configure the device? Is that device plugged into the NVIDIA card at all or is it completely standalone video device that generates it's own picture?

Thanks Terry

terrymacdonald commented 3 years ago

@dev1981 So, some of the other changes in the upcoming DisplayMagician v2.1.0 that I've made should hopefully provide you with something that works. I'm not 100% sure it will help, but I'd really like you to test for me please....

Can you please give this version a test to see if it will work for your problem?

IMPORTANT: You will need to manually uninstall this test version when the proper DisplayMagician v2.1.0 is released, as it will not automatically upgrade from this test version.

DisplayMagicianSetup-v2.1.0.1.zip

Thanks Terry

terrymacdonald commented 3 years ago

As part of this video card code review, I've been looking to see if we can support video cards connected via different mechanisms (e.g. USB-C rather than PCI) and if I can enable multiple drivers at once (e.g. AMD drivers at the same time of NVIDIA so you could get NVIDIA Surround and AMD Eyefinity at the same time).

At the moment, after half a day testing and programming, I've shelved this idea for at least the 2.1.x versions. It is going to be quite a bit of work for supporting these less common situations, and it will take a lot of testing and troubleshooting to get it to work. I am therefore adding this bit of work to my programming backlog, and I'll take a look at it again when I can spend more time learning exactly what's needed.

This shouldn't affect this particular issue logged here though, as the new GDI Windows support should detect the USB based driver as it is a software-based connection via the GDI API, and DisplayMagician v2.1.0 now stores that information. This should work now.

Thanks Terry

terrymacdonald commented 3 years ago

@dev1981 I've found a problem with the setup in that build of DM. I've updated it with a newer one that works after install. I'd forgotten to add the new library dlls to the setup installer :(. Fixed now:

DisplayMagicianSetup-v2.1.0.7.zip

terrymacdonald commented 3 years ago

@dev1981 I've managed to find and solve a WHOLE BOAT LOAD of issues over this last week. And I'm now at a point that I think the video library stuff is working. I'm confident enough to provide you with test version 2.1.0.35 for you to test. It should handle cloned windows, NVIDIA surround, weird layouts (even a combined surround with extra single display works!) and it works after multiple reboots.

@dev1981 There is a chance that this will even work with your DisplayLink USB adapter (but please don't be surprised if it doesn't).

I'd really love you to install this version, and to test the different displays. I really want you to try and break it :D.

DisplayMagicianSetup-v2.1.0.35-test.zip

One important thing to note - it will require you to create new Display Profiles as part of the upgrade. It turns out I needed a bit more information than was available in the DisplayProfiles_2.0.json format I created earlier. So this new 2.1 version creates a DisplayProfiles_2.1.json instead.

Hopefully everything works, and then I can release a new DisplayMagician version and move on to adding other features!

Thanks Terry

terrymacdonald commented 3 years ago

@dev1981 Please install this new build when you do testing instead, and see if it now works ok with your DisplayLink.

DisplayMagicianSetup-v2.1.0.79.zip

Thanks Terry

dev1981 commented 3 years ago

Hi Terry, sry answering so late, diddn´t hat the notifications switched on for the comments...

this is the product i am using: https://www.fujitsu.com/de/products/computing/peripheral/accessories/connectivity/port-replicator-pr08.html

HWIDS USB\VID_17E9&PID_430C&REV_3106&MI_00 USB\VID_17E9&PID_430C&MI_00

https://www.dropbox.com/s/0mtoi792xjgmfsz/adapters.png https://www.dropbox.com/s/moquf5l6wue17e7/pr08.png

the driver: https://www.synaptics.com/products/displaylink-graphics/downloads/windows

its a complete standalone device which is plugged in within USB.

i tested the new binary and still the application can not see the displays which are not connected to my primary NVidia card. https://www.dropbox.com/s/ccwth2njfuq1985/DPM_test.png https://www.dropbox.com/s/wyrcxigy642pyk0/Logs.zip

i have 5 displays attached to the NV card. for that i have always to disable minimum 1 display when i switch over to my SimRig because NVcard only allows 4 displays active at once.

Dual setup https://www.dropbox.com/s/78zwunhw8g771k5/dual.png

Sim setup https://www.dropbox.com/s/7dnpl0o8fm0thrp/Sim.png

grz

adrian

terrymacdonald commented 3 years ago

Hi @dev1981

I did spend a while looking at this last weekend, and I realised I'd have to add a whole class of detection logic (USB) as well as figure out how USB displays interface with the Windows Display Model and then of course extended the WinLibrary to handle that device type. All in all it's going to be a massive amount of work. This is of course made even harder because I don't have a USB device to test with.

At some stage I'm going to need to add this functionality as there are many USB-C displays coming along now, and I will need to add support, but I'm going to delay adding this for a while until I can clear out the backlog of tickets I have, as well as wait until I find myself with a USB device to test with.

I'm really sorry about this, but if anyone has an older USB device that they want to ship to me then I might look at this, but for now it's just too difficult to do. I'm therefore going to assign this to the 'Future' milestone.

Thanks Terry

matthex commented 3 years ago

I have the same issue as dev1981 but with displays connected to the graphics chip of my Intel CPU. So, DisplayMagician recognizes only the displays connected to the NVIDIA card, but not the ones connected to the CPU's graphics chip.

I have read the previous replies and understood, that it the issue is difficult to solve. I can still use the older version of DisplayMagician, so it is all fine. However, I just thought to ask if it makes sense to also send you any logs, since my setup is slightly different? If not, no worries :-)

terrymacdonald commented 3 years ago

Hi @matthex

Yes, please send through some logs. You can generate a support zip file by going into the DisplayMagician settings window from the main DisplayMagician screen and clicking on the create support zip button. Please generate one of those and then upload the zip file to this issue.

I'm not sure if it will be the same problem, as the Display Link device is a USB based display connection. Can you please confirm your system specifications and how your displays are connected?

Operating system: Motherboard: CPU: Video card: Displays make and model: How each display is connected (including the port type e.g. HDMI, USB-C, DP)

That information will help me get an idea of what could be wrong.

Thanks Terry

On Sun, 28 Nov 2021, 06:17 matthex, @.***> wrote:

I have the same issue as dev1981 but with displays connected to the graphics chip of my Intel CPU. So, DisplayMagician recognizes only the displays connected to the NVIDIA card, but not the ones connected to the CPU's graphics chip.

I have read the previous replies and understood, that it the issue is difficult to solve. I can still use the older version of DisplayMagician, so it is all fine. However, I just thought to ask if it makes sense to also send you any logs, since my setup is slightly different? If not, no worries :-)

— You are receiving this because you were assigned. Reply to this email directly, view it on GitHub https://github.com/terrymacdonald/DisplayMagician/issues/44#issuecomment-980725169, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLU5LDNVHHJRVLPLZOSD2DUOEHDFANCNFSM5FIW77VQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

matthex commented 2 years ago

Hello @terrymacdonald

I attached the support file and here is the additional information about my system:

Operating system: Windows 10 Pro (Version 21H1) Motherboard: MSI Z370 SLI Plus (MS-7B46) CPU: Intel Core i7-8700K CPU @ 3.70GHz with Intel UHD Graphics 360 Video card: NVIDIA GeForce GTX 1080 Ti Displays make and model:

I also add a screenshot which might help to see, what the issue is: image Display number 6 is the Fujitsu display that is connected to the CPU and is not recognized by Display Magician.

Thank you!

DisplayMagician-Support-20211128-1523.zip

terrymacdonald commented 2 years ago

@matthex I think this is a different issue to the original one in this issue, so I've created a new issue (#60). Can you please set yourself to that issue so that you get notifications when I pay something to it?

I'll reply in #60 when I get time to look at the log file.

Thanks Terry

terrymacdonald commented 2 years ago

@dev1981 Thanks to some help from @matthex I think we've found a bug that might help with your particular situation. Please keep an eye on issues #60 and when you see a DisplayMagician test build dropped there feel free to give it a go.

Thanks Terry

dev1981 commented 2 years ago

hi yes, i am following the #60 a few days. as soon u drop a relase there i ll test it again. Thank u very much for ur efforts, keep it going.

terrymacdonald commented 2 years ago

Hey @dev1981 I found a couple of errors under windows with @matthex help a couple of days ago. One error was a logic error that prevented more than one display adapter from being used. That may be part of the issue affecting your situation, so it's at least worth it for you to download the test version and see if it works for you.

DisplayMagician v2.1.1.40 test version: DisplayMagicianSetup-v2.1.1.40.zip

I'm not confident it will allow your DisplayLink USB to work, but it might, so it's at least worth testing!

Good luck 🤞

Terry

dev1981 commented 2 years ago

Hi Terry, sadly it is still not working. I can see in the logfile that it is detecting the displays (as far as i understood it) ->

2021-12-13 10:09:13.8469|TRACE|DisplayMagician.Program|WinLibrary/GetWindowsDisplayConfig: Found adapter name \?\USB#VID_17E9&PID_430C&MI_00#8&d6f23a6&1&0000#{5b45201d-f2f2-4f3b-85bb-30ff1f953599} for adapter 557374185.

but i see as well this informations ->

2021-12-13 10:09:13.8469|TRACE|DisplayMagician.Program|WinLibrary/GetWindowsDisplayConfig: Getting the current Display Settings for \.\DISPLAY3 2021-12-13 10:09:13.8469|TRACE|DisplayMagician.Program|WinLibrary/GetWindowsDisplayConfig: The display \.\DISPLAY3 is either not attached to the desktop, or is not a mirroring driver. Skipping this display device as we cannot use it. 2021-12-13 10:09:13.8469|TRACE|DisplayMagician.Program|WinLibrary/GetWindowsDisplayConfig: Getting the current Display Settings for \.\DISPLAY4 2021-12-13 10:09:13.8469|TRACE|DisplayMagician.Program|WinLibrary/GetWindowsDisplayConfig: The display \.\DISPLAY4 is either not attached to the desktop, or is not a mirroring driver. Skipping this display device as we cannot use it.

Display3 is my surround display i configured with NV ctrl panel. Display4 is one of the small LCDs connected within my DisplayLink Device.

In the DPM application the monitort detection looks different to that what i see in the windows control panel. https://www.dropbox.com/s/kee5c3s2n620nvf/DPM1.png

The error message occured as i have try to just save the "Racing Profile" ignoring the fact that the configuration was not shown correctely.

Logfiles: https://www.dropbox.com/s/pc2s2qlnl2gb7xi/DisplayMagician-Support-20211213-1013.zip

an additional finding is, that after closing the DPM app ther is still an open file handle which prevents me from renaming the DPM folder.

greetings and thank you for ur efforts.#

terrymacdonald commented 2 years ago

@dev1981 I've had a chance to go through your logs in more detail, and thanks to your log data I found that the format of USB cards in the PCI device list is different to the ones from PCI cards. Thanks to your data I've been able to update my regex matching to handle the USB format. For reference I've included the two different format examples below in case anyone else on the Internet has the same problem:

PCI Card format:  "\\?\PCI#VEN_10DE&DEV_2482&SUBSYS_408E1458&REV_A1#4&2283f625&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}" 
USB Card format:  "\\?\USB#VID_17E9&PID_430C&MI_00#8&d6f23a6&1&0000#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}"

NVIDIAInfo v1.3.6 now includes those changes, so can you please test them for me?https://github.com/terrymacdonald/NVIDIAInfo/releases/tag/v1.3.6

Please download NVIDIAInfo v1.3.6, then extract the zip file to a new folder, and open a powershell window in that same folder.

IMPORTANT - These instructions are likely to fail, so I need you to save/rename the NVIDIAInfo.log file as shown below. Each run of NVIDIAInfo overwrites the previous NVIDIAInfo.log, so I need you to rename it each time so it doesn't get overwritten. I need to see the log file entries to know what is broken.

After that, please complete the following instructions in this specific order:

Create a first windows display layout with some of your screens:

Next create a second windows display layout (second):

Next swap back to the racing display layout:

Next swap back to the regular display layout:

Once that series of tests are done, please ZIP up the following files into a single zip file, and then drag and drop them onto this github issue (you don't need to put them in dropbox, you can upload here through your browser):

And then I'll be able to see if it worked or not! I'm expecting it to fail, so it will be a nice surprise if it works :).

Thanks Terry

dev1981 commented 2 years ago

(general) The Numbers of the Displays in the WIN settings are changing, i guess as well depends on the POWER state of my displays and DisplayLink device.

All of the states i made a screenshot of the WIN settings. Up on 5th try i made screenshots from the DPM application, too. diddn´t do that before. Because of that i reverted back some of the states later and made some screenshots afterwards of the DPM application.

(First CFG) The list below are the Displays # which are shown in WIN settings ONLY WHEN #1 & 2 HAVE POWER. All other monitors don´t have power and the DisplayLink is switched off. (I have two main switches on my racing rig to completely shut it down from power when not used.)

(WIN Settings)
Display #1; Zowie27 wired within DP cable on NVcard (main display) (connected)
Display #2; Benq24 wired within HDMI cable on NVCard @USBC port using usbC to HDMI adapter (connected)
Display #3; AOC32 wired within HDMI cable on NVCard (disconnected)
Display #4; AOC32 wired within HDMI cable on NVCard (disconnected)
Display #5 which is connected directely within DP port to the NVcard IS NOT SHOWN in WIN settings. ?? MAYBE because my rtx2070 can only use 4 of its 5 ports at the same time (HW limitation) ??

Display #6; china 7' LCD wired within HDMI cable on DisplayLink using HDMI to DP adapter IS NOT SHOWN in WIN settings
Display #7; china 10' Monitor wired within HDMI cable on DisplayLink using HDMI to DVI adapter IS NOT SHOWN in WIN settings

(DPM Settings)
Display #1; Zowie27 wired within DP cable on NVcard (main display) (connected) -> SHOWING
Display #2; Benq24 wired within HDMI cable on NVCard @USBC port using usbC to HDMI adapter (connected) -> SHOWING

Display #3,4,5,6,7 -> NOT SHOWING

I directely noticed, that displays which have the state (disconnected) are not shown in DPM application.

"DisplayIdentifiers": [
    "WINAPI|\\\\?\\PCI#VEN_10DE&DEV_1E84&SUBSYS_87271043&REV_A1#4&2b49caf9&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DISPLAYPORT_EXTERNAL|53513|32517|\\\\?\\DISPLAY#BNQ7F05#5&2bd207a3&1&UID57606#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|BenQ XL2420T",
    "WINAPI|\\\\?\\PCI#VEN_10DE&DEV_1E84&SUBSYS_87271043&REV_A1#4&2b49caf9&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DISPLAYPORT_EXTERNAL|53513|32608|\\\\?\\DISPLAY#BNQ7F60#5&2bd207a3&1&UID57603#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|ZOWIE XL LCD"
    ]

(Second-1 CFG) The list below are the Displays # which are shown in WIN settings WHEN ALL monitors HAVE POWER and DisplayLink is SWITCHED ON. In that state, WIN changes the display #.

(WIN Settings)
Display #2; Zowie27 wired within DP cable on NVcard (primary display) (connected)
Display #3; Benq24 wired within HDMI cable on NVCard @USBC port using usbC to HDMI adapter (connected)

Display #1; AOC32 wired within DP cable on NVCard (disconnected)
Display #4; AOC32 wired within HDMI cable on NVCard (disconnected)
Display #5; AOC32 wired within HDMI cable on NVCard (disconnected)

Display #6; china 7' LCD wired within HDMI cable on DisplayLink using HDMI to DP adapter (disconnected)
Display #7; china 10' Monitor wired within HDMI cable on DisplayLink using HDMI to DVI adapter (disconnected)

(DPM Settings)
Display #1; Zowie27 wired within DP cable on NVcard (primary display) (connected) -> SHOWING
Display #2; Benq24 wired within HDMI cable on NVCard @USBC port using usbC to HDMI adapter (connected) -> SHOWING

Display #3,4,5,6,7 -> NOT SHOWING
Here i noticed directely that between (First CFG) and (Second-1 CFG) in DPM application visibly nothing changed but in the WIN settings it has.
Displays which have the state (disconnected) are not shown in DPM application.
Check the FIRST-SECOND-1-DIFF-.png to see minor differences in .CFG between these states. DisplayIdentifiers stayed the same!!!!

"DisplayIdentifiers": [
    "WINAPI|\\\\?\\PCI#VEN_10DE&DEV_1E84&SUBSYS_87271043&REV_A1#4&2b49caf9&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DISPLAYPORT_EXTERNAL|53513|32517|\\\\?\\DISPLAY#BNQ7F05#5&2bd207a3&1&UID57606#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|BenQ XL2420T",
    "WINAPI|\\\\?\\PCI#VEN_10DE&DEV_1E84&SUBSYS_87271043&REV_A1#4&2b49caf9&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DISPLAYPORT_EXTERNAL|53513|32608|\\\\?\\DISPLAY#BNQ7F60#5&2bd207a3&1&UID57603#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|ZOWIE XL LCD"
    ]

(Second-2 CFG) i used DPM 1.14 to switch over the profile to my Racing setup. (renamed %appdata% folder & binary folder) then loaded Sim racing profile all monitors and DisplayLink Device are powered on.

Display #1; Zowie27 wired within DP cable on NVcard (primary display) (connected)
Display #2; Benq24 wired within HDMI cable on NVCard @USBC port using usbC to HDMI adapter (disconnected)

Displays #1,#4,#5 from (Second-1 CFG) are teamed up as NV surround Display as #3 (connected)

Display #6; china 7' LCD wired within HDMI cable on DisplayLink using HDMI to DP adapter (connected)
Display #7; china 10' Monitor wired within HDMI cable on DisplayLink using HDMI to DVI adapter (connected)

(DPM Settings)
Display #1; Zowie27 wired within DP cable on NVcard (connected)
Display #3; NV Surround (primary display) (connected)

"DisplayIdentifiers": [
    "WINAPI|\\\\?\\PCI#VEN_10DE&DEV_1E84&SUBSYS_87271043&REV_A1#4&2b49caf9&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DISPLAYPORT_EXTERNAL|53513|32608|\\\\?\\DISPLAY#BNQ7F60#5&2bd207a3&1&UID57603#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|ZOWIE XL LCD",
    "WINAPI|\\\\?\\PCI#VEN_10DE&DEV_1E84&SUBSYS_87271043&REV_A1#4&2b49caf9&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DVI|58117|12802|\\\\?\\DISPLAY#AOC3202#5&2bd207a3&1&UID58368#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|NV Surround",
    "WINAPI|\\\\?\\USB#VID_17E9&PID_430C&MI_00#8&d6f23a6&1&0000#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DISPLAYPORT_EXTERNAL|33028|4|\\\\?\\DISPLAY#ADA0004#9&aea1eed&0&UID257#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|",
    "WINAPI|\\\\?\\USB#VID_17E9&PID_430C&MI_00#8&d6f23a6&1&0000#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DVI|36113|0|\\\\?\\DISPLAY#DLM0000#9&aea1eed&0&UID256#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|No Monitor"
]

(Second-3 CFG) i used DPM 1.14 to switch back to DUAL (Second-1 CFG), renamed %appdata% folder & binary folder back to check for DPM application.

(WIN Settings)
Display #2; Zowie27 wired within DP cable on NVcard (primary display) (connected)
Display #3; Benq24 wired within HDMI cable on NVCard @USBC port using usbC to HDMI adapter (connected)

Display #1; AOC32 wired within DP cable on NVCard (disconnected)
Display #4; AOC32 wired within HDMI cable on NVCard (disconnected)
Display #5; AOC32 wired within HDMI cable on NVCard (disconnected)

Display #6; china 7' LCD wired within HDMI cable on DisplayLink using HDMI to DP adapter (disconnected)
Display #7; china 10' Monitor wired within HDMI cable on DisplayLink using HDMI to DVI adapter (disconnected)

(DPM Settings)
Display #1; Zowie27 wired within DP cable on NVcard (primary display) (connected) -> SHOWING
Display #2; Benq24 wired within HDMI cable on NVCard @USBC port using usbC to HDMI adapter (connected) -> SHOWING

Display #3,4,5,6,7 -> NOT SHOWING

"DisplayIdentifiers": [
    "WINAPI|\\\\?\\PCI#VEN_10DE&DEV_1E84&SUBSYS_87271043&REV_A1#4&2b49caf9&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DISPLAYPORT_EXTERNAL|53513|32517|\\\\?\\DISPLAY#BNQ7F05#5&2bd207a3&1&UID57606#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|BenQ XL2420T",
    "WINAPI|\\\\?\\PCI#VEN_10DE&DEV_1E84&SUBSYS_87271043&REV_A1#4&2b49caf9&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DISPLAYPORT_EXTERNAL|53513|32608|\\\\?\\DISPLAY#BNQ7F60#5&2bd207a3&1&UID57603#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|ZOWIE XL LCD"
]

(Second-4 CFG) & (Second-5 CFG) i additionally activated the two displays which are connected to the DisplayLink.

(WIN Settings)
Display #2; Zowie27 wired within DP cable on NVcard (primary display) (connected)
Display #3; Benq24 wired within HDMI cable on NVCard @USBC port using usbC to HDMI adapter (connected)

Display #1; AOC32 wired within DP cable on NVCard (disconnected)
Display #4; AOC32 wired within HDMI cable on NVCard (disconnected)
Display #5; AOC32 wired within HDMI cable on NVCard (disconnected)

Display #6; china 7' LCD wired within HDMI cable on DisplayLink using HDMI to DP adapter (connected)
Display #7; china 10' Monitor wired within HDMI cable on DisplayLink using HDMI to DVI adapter (connected)

(DPM Settings)
Display #2; Zowie27 wired within DP cable on NVcard (primary display) (connected) -> SHOWING
    Display #6; china 7' LCD wired within HDMI cable on DisplayLink using HDMI to DP adapter (connected) -> SHOWING !!!!
Display #1,3,4,5,7 -> NOT SHOWING

This is why (Second-4 CFG) and (Second-5 CFG) on my tests are done twice. It was the FIRST time ever i saw a device which was connected to the DisplayLink in DPM application. (most times i do not open it during daily use because i have created my own bat files to start my sims. I am using the cmdlines of DPM)

Look at the DisplayIdents :) so far so good but the results in the GUI of DPM are not the one i expected. DPM shows display[0] of card[0] and display[1] of card[1] the other two are not showing in the GUI.

"DisplayIdentifiers": [
    "WINAPI|\\\\?\\PCI#VEN_10DE&DEV_1E84&SUBSYS_87271043&REV_A1#4&2b49caf9&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DISPLAYPORT_EXTERNAL|53513|32517|\\\\?\\DISPLAY#BNQ7F05#5&2bd207a3&1&UID57606#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|BenQ XL2420T",
    "WINAPI|\\\\?\\PCI#VEN_10DE&DEV_1E84&SUBSYS_87271043&REV_A1#4&2b49caf9&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DISPLAYPORT_EXTERNAL|53513|32608|\\\\?\\DISPLAY#BNQ7F60#5&2bd207a3&1&UID57603#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|ZOWIE XL LCD",
    "WINAPI|\\\\?\\USB#VID_17E9&PID_430C&MI_00#8&d6f23a6&1&0000#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DISPLAYPORT_EXTERNAL|33028|4|\\\\?\\DISPLAY#ADA0004#9&aea1eed&0&UID257#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|",
    "WINAPI|\\\\?\\USB#VID_17E9&PID_430C&MI_00#8&d6f23a6&1&0000#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DVI|36113|0|\\\\?\\DISPLAY#DLM0000#9&aea1eed&0&UID256#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|No Monitor"
    ]

((Second-6 CFG) a snapshot to start over, same state as (Second-1 CFG)

"DisplayIdentifiers": [
    "WINAPI|\\\\?\\PCI#VEN_10DE&DEV_1E84&SUBSYS_87271043&REV_A1#4&2b49caf9&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DISPLAYPORT_EXTERNAL|53513|32517|\\\\?\\DISPLAY#BNQ7F05#5&2bd207a3&1&UID57606#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|BenQ XL2420T",
    "WINAPI|\\\\?\\PCI#VEN_10DE&DEV_1E84&SUBSYS_87271043&REV_A1#4&2b49caf9&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DISPLAYPORT_EXTERNAL|53513|32608|\\\\?\\DISPLAY#BNQ7F60#5&2bd207a3&1&UID57603#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|ZOWIE XL LCD"
    ]

(Second-7 CFG) i connected all displays except #2.

(WIN Settings)
Display #2; Zowie27 wired within DP cable on NVcard (primary display) (connected)
Display #3; Benq24 wired within HDMI cable on NVCard @USBC port using usbC to HDMI adapter (disconnected)

Display #1; AOC32 wired within DP cable on NVCard (connected)
Display #4; AOC32 wired within HDMI cable on NVCard (connected)
Display #5; AOC32 wired within HDMI cable on NVCard (connected)
-> NO SURROUND CONFIG

Display #6; china 7' LCD wired within HDMI cable on DisplayLink using HDMI to DP adapter (connected)
Display #7; china 10' Monitor wired within HDMI cable on DisplayLink using HDMI to DVI adapter (connected)

(DPM Settings)
Display #3,1,4,5 -> SHOWING
Display #6,7 -> NOT SHOWING

"DisplayIdentifiers": [
    "WINAPI|\\\\?\\PCI#VEN_10DE&DEV_1E84&SUBSYS_87271043&REV_A1#4&2b49caf9&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DISPLAYPORT_EXTERNAL|53513|32517|\\\\?\\DISPLAY#BNQ7F05#5&2bd207a3&1&UID57606#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|BenQ XL2420T",
    "WINAPI|\\\\?\\PCI#VEN_10DE&DEV_1E84&SUBSYS_87271043&REV_A1#4&2b49caf9&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DISPLAYPORT_EXTERNAL|53513|32608|\\\\?\\DISPLAY#BNQ7F60#5&2bd207a3&1&UID57603#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|ZOWIE XL LCD",
    "WINAPI|\\\\?\\PCI#VEN_10DE&DEV_1E84&SUBSYS_87271043&REV_A1#4&2b49caf9&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DISPLAYPORT_EXTERNAL|58117|12802|\\\\?\\DISPLAY#AOC3202#5&2bd207a3&1&UID57601#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|32G2WG3",
    "WINAPI|\\\\?\\PCI#VEN_10DE&DEV_1E84&SUBSYS_87271043&REV_A1#4&2b49caf9&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_HDMI|58117|12802|\\\\?\\DISPLAY#AOC3202#5&2bd207a3&1&UID57605#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|32G2WG3",
    "WINAPI|\\\\?\\USB#VID_17E9&PID_430C&MI_00#8&d6f23a6&1&0000#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DISPLAYPORT_EXTERNAL|33028|4|\\\\?\\DISPLAY#ADA0004#9&aea1eed&0&UID257#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|",
    "WINAPI|\\\\?\\USB#VID_17E9&PID_430C&MI_00#8&d6f23a6&1&0000#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DVI|36113|0|\\\\?\\DISPLAY#DLM0000#9&aea1eed&0&UID256#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|No Monitor"
    ]

(Second-8 CFG) i connected #2 & #3 and #6

(WIN Settings)
Display #2; Zowie27 wired within DP cable on NVcard (primary display) (connected)
Display #3; Benq24 wired within HDMI cable on NVCard @USBC port using usbC to HDMI adapter (connected)

Display #1; AOC32 wired within DP cable on NVCard (disconnected)
Display #4; AOC32 wired within HDMI cable on NVCard (disconnected)
Display #5; AOC32 wired within HDMI cable on NVCard (disconnected)
-> NO SURROUND CONFIG

Display #6; china 7' LCD wired within HDMI cable on DisplayLink using HDMI to DP adapter (connected)
Display #7; china 10' Monitor wired within HDMI cable on DisplayLink using HDMI to DVI adapter (connected)

(DPM Settings)
Display #2 -> SHOWING
Display #6 -> SHOWING

Display #3,1,4,5,7 -> NOT SHOWING

"DisplayIdentifiers": [
    "WINAPI|\\\\?\\PCI#VEN_10DE&DEV_1E84&SUBSYS_87271043&REV_A1#4&2b49caf9&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DISPLAYPORT_EXTERNAL|53513|32517|\\\\?\\DISPLAY#BNQ7F05#5&2bd207a3&1&UID57606#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|BenQ XL2420T",
    "WINAPI|\\\\?\\PCI#VEN_10DE&DEV_1E84&SUBSYS_87271043&REV_A1#4&2b49caf9&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DISPLAYPORT_EXTERNAL|53513|32608|\\\\?\\DISPLAY#BNQ7F60#5&2bd207a3&1&UID57603#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|ZOWIE XL LCD",
    "WINAPI|\\\\?\\USB#VID_17E9&PID_430C&MI_00#8&d6f23a6&1&0000#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DISPLAYPORT_EXTERNAL|33028|4|\\\\?\\DISPLAY#ADA0004#9&aea1eed&0&UID257#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|"
    ]

(Second-9 CFG) last snapshot, same state as (Second-1 CFG)

"DisplayIdentifiers": [
    "WINAPI|\\\\?\\PCI#VEN_10DE&DEV_1E84&SUBSYS_87271043&REV_A1#4&2b49caf9&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DISPLAYPORT_EXTERNAL|53513|32517|\\\\?\\DISPLAY#BNQ7F05#5&2bd207a3&1&UID57606#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|BenQ XL2420T",
    "WINAPI|\\\\?\\PCI#VEN_10DE&DEV_1E84&SUBSYS_87271043&REV_A1#4&2b49caf9&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DISPLAYPORT_EXTERNAL|53513|32608|\\\\?\\DISPLAY#BNQ7F60#5&2bd207a3&1&UID57603#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|ZOWIE XL LCD"
    ]

so, hopefully u made it up on the end of my summary before falling asleep or inflame urself :D. Sry for generating so much text i just tried to describe everything excately.

Update: what i completely forgot is trying to reload my profiles... (stupid me). So i tried to make this afterwards. Now u have a bunch of logs from different states with connected displays and powerless ones :).

Reloading my saved profiles mainly works, but like the old DPM version i have to execute the "second-2.cfg" 2 times. I guess this has sth. to do with the fact that only 4 active displays are allowed by the NVcard.

So if i run the cmdline: check the reload screenshots u can see after a success apply the DPM app does not show the applied state. But it worked :) This does finally mean, the issue is just in the GUI!!! (as i can say) -> see testcase (Second-4 CFG) & (Second-5 CFG)

E:\downloads\NVIDIAInfo-v1.3.6>NVIDIAInfo.exe load second-2.cfg

NVIDIAInfo v1.3.6
=================
By Terry MacDonald 2021

Attempting to apply NVIDIA display config from second-2.cfg
ERROR - NVIDIAInfo Windows CCD settings were not applied correctly.

E:\downloads\NVIDIAInfo-v1.3.6>NVIDIAInfo.exe load second-2.cfg

NVIDIAInfo v1.3.6
=================
By Terry MacDonald 2021

Attempting to apply NVIDIA display config from second-2.cfg
NVIDIAInfo Display config successfully applied

reverting it back to (second-1.cfg)

    E:\downloads\NVIDIAInfo-v1.3.6>NVIDIAInfo.exe load second-1.cfg

NVIDIAInfo v1.3.6
=================
By Terry MacDonald 2021

Attempting to apply NVIDIA display config from second-1.cfg
NVIDIAInfo Display config successfully applied

what i tried then was to revert back to my first generated profile (first). 1st attempt all devices were still on POWER. 2nd attempt switched off power for DisplayLink and 3 monitors. Result was the same for both attempts.

    E:\downloads\NVIDIAInfo-v1.3.6>NVIDIAInfo.exe load first.cfg

NVIDIAInfo v1.3.6
=================
By Terry MacDonald 2021

The display settings in first.cfg are already installed. No need to install them again. Exiting.

what i did not was to try re-apply all the previous generated CFGs.

Terry, i am so sry that i diddnt have tried this things with the nvidiainfo tool before. i think with ur latest or one of the recent changes to it (or maybe from the beginning) it was working and the issue displaying, creating, saving and applying the profiles within the GUI did not work. What i tried last time already to save a profile ignoring the fact that the layout was not displayed correct in the DPM application but this lead into an error u can see in my last post and uploaded files.

so even if are not able to fix the GUI someday i can use the nvidiainfo cmdline to apply my screen layouts.

Sry not thinking deeper into it until now. took me about 5hrs to go through and writing down all the data and and stuff.

so if u have any questions or u want to have an active conversation we can meet tghter in discord for example. i have holidays until beginning of january so feel free to contact me.

Screenshots, logs and the description above can be found inside of the ZIP. DPM-Analysis.zip

Thank u for ur efforts hopefully my investigations can bring u a step further.

greetings from germany

Adrian

terrymacdonald commented 2 years ago

@dev1981 I'm sorry but that's all quite difficult to follow. I am really confused as to what you tested and what you didn't test. I really do appreciate the effort you put in, but I don't know the exact order in which you performed the tests, and what left over settings were from the previous failures or successes, I can't really make use of much of those tests at all as the prior tests may have affected the subsequent tests :(. This means the tests are invalid and I'll need you to do more testing :(.

It's not all bad news though. I did manage to work out that the USB devices are being detected, and they are being saved in the cfg files when they are in use, which is great news.

    "DisplayIdentifiers": [
      "WINAPI|\\\\?\\PCI#VEN_10DE&DEV_1E84&SUBSYS_87271043&REV_A1#4&2b49caf9&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DISPLAYPORT_EXTERNAL|53513|32608|\\\\?\\DISPLAY#BNQ7F60#5&2bd207a3&1&UID57603#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|ZOWIE XL LCD",
      "WINAPI|\\\\?\\PCI#VEN_10DE&DEV_1E84&SUBSYS_87271043&REV_A1#4&2b49caf9&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DVI|58117|12802|\\\\?\\DISPLAY#AOC3202#5&2bd207a3&1&UID58368#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|NV Surround",
      "WINAPI|\\\\?\\USB#VID_17E9&PID_430C&MI_00#8&d6f23a6&1&0000#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DISPLAYPORT_EXTERNAL|33028|4|\\\\?\\DISPLAY#ADA0004#9&aea1eed&0&UID257#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|",
      "WINAPI|\\\\?\\USB#VID_17E9&PID_430C&MI_00#8&d6f23a6&1&0000#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}|DISPLAYCONFIG_OUTPUT_TECHNOLOGY_DVI|36113|0|\\\\?\\DISPLAY#DLM0000#9&aea1eed&0&UID256#{e6f07b5f-ee97-4a90-b076-33f57bf4eaa7}|No Monitor"
    ]

I did also note that the second-2.cfg (which seems to have the USB DisplayLink displays in there) failed to apply the config the first time with this error, but I don't know what didn't change as you didn't follow my instructions exactly, and that meant I can't see the difference between the initial saved config, and the one after the attempted load:

2021-12-14 14:44:46.4659|ERROR|DisplayMagicianShared.SharedLogger|WinLibrary/SetActiveConfig: An unspecified error occurred. Display configuration not applied.

On a positive note I can see that the saved USB adapter ID is being patched with the new USB adapter ID, so that should mean once we solve this issue it should work even after the PC has been restarted:

2021-12-14 14:44:46.4439|TRACE|DisplayMagicianShared.SharedLogger|WinLibrary/PatchAdapterIDs: Going through the list of adapters we stored in the config to figure out the old adapterIDs
2021-12-14 14:44:46.4439|TRACE|DisplayMagicianShared.SharedLogger|WinLibrary/PatchAdapterIDs: Checking if saved adapter 71244 (AdapterName is \\?\PCI#VEN_10DE&DEV_1E84&SUBSYS_87271043&REV_A1#4&2b49caf9&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}) is equal to current adapter id 71244 (AdapterName is \\?\PCI#VEN_10DE&DEV_1E84&SUBSYS_87271043&REV_A1#4&2b49caf9&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599})
2021-12-14 14:44:46.4439|TRACE|DisplayMagicianShared.SharedLogger|WinLibrary/PatchAdapterIDs: We found that saved adapter 71244 has now been assigned adapter id 71244 (AdapterName is \\?\PCI#VEN_10DE&DEV_1E84&SUBSYS_87271043&REV_A1#4&2b49caf9&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599})
2021-12-14 14:44:46.4439|TRACE|DisplayMagicianShared.SharedLogger|WinLibrary/PatchAdapterIDs: Checking if saved adapter 71244 (AdapterName is \\?\PCI#VEN_10DE&DEV_1E84&SUBSYS_87271043&REV_A1#4&2b49caf9&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}) is equal to current adapter id 752202168 (AdapterName is \\?\USB#VID_17E9&PID_430C&MI_00#8&d6f23a6&1&0000#{5b45201d-f2f2-4f3b-85bb-30ff1f953599})
2021-12-14 14:44:46.4439|TRACE|DisplayMagicianShared.SharedLogger|WinLibrary/PatchAdapterIDs: Checking if saved adapter 684362038 (AdapterName is \\?\USB#VID_17E9&PID_430C&MI_00#8&d6f23a6&1&0000#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}) is equal to current adapter id 71244 (AdapterName is \\?\PCI#VEN_10DE&DEV_1E84&SUBSYS_87271043&REV_A1#4&2b49caf9&0&0019#{5b45201d-f2f2-4f3b-85bb-30ff1f953599})
2021-12-14 14:44:46.4439|TRACE|DisplayMagicianShared.SharedLogger|WinLibrary/PatchAdapterIDs: Checking if saved adapter 684362038 (AdapterName is \\?\USB#VID_17E9&PID_430C&MI_00#8&d6f23a6&1&0000#{5b45201d-f2f2-4f3b-85bb-30ff1f953599}) is equal to current adapter id 752202168 (AdapterName is \\?\USB#VID_17E9&PID_430C&MI_00#8&d6f23a6&1&0000#{5b45201d-f2f2-4f3b-85bb-30ff1f953599})
2021-12-14 14:44:46.4439|TRACE|DisplayMagicianShared.SharedLogger|WinLibrary/PatchAdapterIDs: We found that saved adapter 684362038 has now been assigned adapter id 752202168 (AdapterName is \\?\USB#VID_17E9&PID_430C&MI_00#8&d6f23a6&1&0000#{5b45201d-f2f2-4f3b-85bb-30ff1f953599})
2021-12-14 14:44:46.4439|TRACE|DisplayMagicianShared.SharedLogger|WinLibrary/PatchAdapterIDs: Going through the display config paths to update the adapter id
2021-12-14 14:44:46.4439|TRACE|DisplayMagicianShared.SharedLogger|WinLibrary/PatchAdapterIDs: Going through the display config modes to update the adapter id
2021-12-14 14:44:46.4439|TRACE|DisplayMagicianShared.SharedLogger|WinLibrary/PatchAdapterIDs: Going through the display config HDR info to update the adapter id

So, I'm going to need you to perform the tests listed below EXACTLY as they are typed below and IN THIS EXACT ORDER, so that I know the data in the log files is accurate and is useful. I am very impressed with the effort you put in with the tests, but its really, really, really important that the exact commands I've provided below are followed in the exact order so that I can get the results I need.

Please do not use DisplayMagician at all during these tests. Shut it down so that we know it is not interfering in the tests.

Only use NVIDIAInfo v1.3.6 in these tests.

INSTRUCTIONS

Firstly, please delete all the CFG, OPNG and LOG files from teh NVidiaInfo folder. I want to start again from the beginning with no configs.

Next, create a first windows display layout with some of your screens (do NOT use any DisplayLink USB attached screens):

Next create a second windows display layout which DOES use the USB DisplayLink in some way:

Next swap back to the first display layout:

Next swap back to the second display layout:

Once that series of tests are done, please ZIP up the following files into a single zip file, and then attach them to this Github issue via your web browser (DO NOT UPLOAD THEM TO DROPBOX):

The tests shown above will give me enough information to know what to try next. Please make sure you perform the test I've provided above exactly in order.

Thanks Terry

dev1981 commented 2 years ago

hi terry, ok, i´ll do it again.

Just to explain, i created first 9 different CFGs, for all of them screenshots from WIN and DPM GUI and described the connection states in WIN and DPM GUI. The description is chronological, so just from top to bottom.

CFG "first" is the first i created CFG (Second-1 CFG) is the second i created and so on... Between this creations i diddnt reload any CFG, i ll just created new ones. Just to compare what NVinfo is detecting when i switch the layouts and active monitors in the WIN settings.

Every time i switched the layout in WIN, i opened the DPM as well and checked if the layouts are equal to windows, which i noticed that this is not the case.

I documented this every time for every created CFG within the screenshots and a description. Also every time renamed the logfile. (all in the ZIP)

DPM-Analysis.zip

After that CREATION procedures I tried FIRST time to reload only the CFG (Second-2 CFG) which i have created before with NVIDIA info. This is my Target Layout for SimRacing. (i used DPM 1.14 to arrange the layout because i am a lazy guy :)) Everytime NVinfo was executed, DPM was shut down completely!

It required 2 attemps directely executed each after another to be applied with success. So as i have written. In general generating CFGs and applying / reloading them using NvidiaInfo IS WORKING, but the DPM GUI is not displaying the applied layouts correctely.

finally i have reloaded (Second-1 CFG) -> Worked 1st attempt. The "FIRST" CFG -> worked or simpler said, it was telling thats already applied. The only difference between these two CFG was the powerstate of the monitors and the DisplayLink device. The Logs are for the reloads have sth with reload in the file name. And again every time a screenshot from win settings and DPM application.

So give me a few mins, i ll make the requested tests again.

greetings

dev1981 commented 2 years ago

hi Terry,

tests are done. NVIDIAInfo-v1.3.6-test.zip

Nvinfo is working as it should as far i can say. Only DPM GUI layout is wrong.

replaced the dropbox links in my previous posts.

And here are the logs when i try to apply the SimRacing config and it fails on 1st attempt but works on 2nd attempt directely each after another. In between nothing is changed. Just cmd line exec.

this issue i have as well when i am using the DPM 1.14 cmdline. D:\Spiele\DisplayMagician\DisplayMagician.exe ChangeProfile "50709593-bf03-43ab-a22f-1edce6f8510b" i have to exec it twice that the traget config is applied within success. As i said before this might refer to the fact that NV only allow 4 active disaplays on my card which has 5 ports :) One has always to be disabled. 5 monitors are attached.

NVIDIAInfo-reload -SimRacing-1st-attempt-FAILED.log

NVIDIAInfo-reload -SimRacing-st-2nd-attempt-SUCCESS.log

grz

terrymacdonald commented 2 years ago

@dev1981 awesome thanks. I'll have a look at what the simracing config issue is.

I've not heard of NVIDIA surround having a limit of 5 displays anywhere else (the driver has a limit of 32 screens IIRC) but it could be a limit with what your card supports. If it's a limitation with NVIDIA driver then as long as you've saved different valid configurations then the NVIDIALibrary used by NVIDIAInfo should apply the config that will disable the relevant monitor to keep under that limit.

The DisplayMagician GUI is the next fix once I'm sure that the WinLibrary is working properly. At the moment I'm trying to get USB devices, SuperDisplay and multiple adapters all working reliably at the same time, so that's the main focus at the moment. Once we get the WinLibrary working reliably then I can start on getting it integrated into DisplayMagician, and then work on the GUI part :).

OK! So next step is to make sure that NVIDIAInfo works after a reboot. Windows changes the display adapter numbering, and so WinLibrary has to patch the display adapter IDs so that it works.

Please do not use DisplayMagician at all during these tests. Shut it down so that we know it is not interfering in the tests.

Only use NVIDIAInfo v1.3.6 in these tests.

NEW INSTRUCTIONS

Next, create a cloned windows display layout with some of your screens (please use a DisplayLink USB attached screen if you can clone it):

Next swap back to the first display layout:

Next swap back to the second display layout:

Next swap back to the cloned display layout:

Once that series of tests are done, please ZIP up the following files into a single zip file, and then attach them to this Github issue via your web browser (DO NOT UPLOAD THEM TO DROPBOX):

All of that should enable me to confirm that NVIDIAInfo works after a restart, and that it works with a cloned display!

Thank you again for all your hard work troubleshooting this. Unfortunately with a device like a DisplayLink USB it's only with help from people such as yourself that we can troubleshoot and fix these errors.

Thanks Terry

terrymacdonald commented 2 years ago

@dev1981 DisplayMagician v1.1.4 uses a completely different display library. It was the original NVAPIWrapper library by Soroush Falahati (the original Helios Display Management author that DisplayMagician is based on) . I wouldn't recommend using DisplayMagician at the moment to configure or test any other display layouts, as it will probably setup an invalid config that won't work properly.

DisplayMagician v2 uses 3 brand new custom display libraries that I created - NVIDIALibrary, AMDLibrary and WinLibrary. I've been working for about 6 months now to iron out all the bugs from them and add new features, and we're so nearly there. But even these libraries are not perfect enough to use to setup the config files for NVIDIAInfo testing.

If you have any new profile that you want to create (e.g. SimRacing.cfg), then I strongly recommend using NVIDIA Control Panel, Windows Display Setup or what ever the DisplayLink USB uses, to set up the display layout. The reason is that those programs are designed to do the original setup and layout correctly. They each know how to pick a valid display configuration that will work with the display drivers. They each will pick a config that works.

DisplayMagician is just a display configuration recorder... it is used to store a display configuration for later, and then reapply it at a later date. DisplayMagician does no real validation to check if a display configuration is missing any settings. DisplayMagician has no idea if a configuration is invalid or valid. It simply tries to config what it stored before.

That is why it is so important to do all your setup using NVIDIA Control Panel, Windows Display Setup (or in the DisplayLink program if it has some settings?). Those programs all know what a valid config is.

Does that make sense?

Thanks Terry

dev1981 commented 2 years ago

hi Terry, first of all i resatrted my machine and just tested if my two CFGs (Simracing and DUAL) are still appliable. That was the case. NVIDIAInfo_Reboot-Reload-dual.log NVIDIAInfo_Reboot-Reload-SimRacing.log

Then i started the requested tests. I created a clone layout, saved it, checked it. Then the request was to change back to the first layout -> Which first layout?! -> i used my DUAL as first CFG -> loaded it

followed the advices further until;

Next swap back to the second display layout:

Load the second windows display as NVIDIAInfo load second.cfg ??!! -> which second? cloned? second? -> there i used recently created RANDOM CFG as second.

Then i followed further until i got an error at

Next swap back to the cloned display layout:

Load the second windows display as NVIDIAInfo load cloned.cfg

but continued with the tests until the end.

So i think there might be an issue understanding ur advices correctely. Anyways, i have created a ps1 script which is in the zip which shows what i have done. the first.cfg and second.cfg i copied over from another location because regarding to ur advice they have not been created during that test cycle.

NVIDIAInfo-v1.3.6-test-2.zip

so maybe u can tell me if its messed up. or what went wrong in the test sequence, then i ll do it again.

Maybe it will be easier to meet me here https://discord.gg/pcuUfUwc

grz

Adrian

dev1981 commented 2 years ago

@dev1981 DisplayMagician v1.1.4 uses a completely different display library. It was the original NVAPIWrapper library by Soroush Falahati (the original Helios Display Management author that DisplayMagician is based on) . I wouldn't recommend using DisplayMagician at the moment to configure or test any other display layouts, as it will probably setup an invalid config that won't work properly.

DisplayMagician v2 uses 3 brand new custom display libraries that I created - NVIDIALibrary, AMDLibrary and WinLibrary. I've been working for about 6 months now to iron out all the bugs from them and add new features, and we're so nearly there. But even these libraries are not perfect enough to use to setup the config files for NVIDIAInfo testing.

If you have any new profile that you want to create (e.g. SimRacing.cfg), then I strongly recommend using NVIDIA Control Panel, Windows Display Setup or what ever the DisplayLink USB uses, to set up the display layout. The reason is that those programs are designed to do the original setup and layout correctly. They each know how to pick a valid display configuration that will work with the display drivers. They each will pick a config that works.

DisplayMagician is just a display configuration recorder... it is used to store a display configuration for later, and then reapply it at a later date. DisplayMagician does no real validation to check if a display configuration is missing any settings. DisplayMagician has no idea if a configuration is invalid or valid. It simply tries to config what it stored before.

That is why it is so important to do all your setup using NVIDIA Control Panel, Windows Display Setup (or in the DisplayLink program if it has some settings?). Those programs all know what a valid config is.

Does that make sense?

Thanks Terry

hi

i ALWAYS used Windows and NV control panel to setup my displays. I used 1st Helios and then DPM to save and load the profiles within CMD lines in batchfiles when i start my racing games. So for now, i am only using ur NVinfoTool because i can save&apply the desired profiles. When i have time, i will completely start over making my layouts and save the CFGs again with the info tool, but i have the strange feeling, that in the depths of WINDOWS registry might be some left overs. Cleaning this up to start at day 0 might be tricky. DisplayLink has no special config tool, it handeld completely within th eWIN settings.

grz

terrymacdonald commented 2 years ago

Hi Adrian,

I'm based in New Zealand, which is about as far away from Germany as I can get 🙂. I can't really get onto discord at the same time as you I'm sorry, due to the massive time difference.

I'll have a look at the logs you sent, and see if I can figure out what's happening. I'll go through your logs in the morning when I wake up, and I'll see what I find.

Thanks for all your testing!

Terry

On Wed, 15 Dec 2021, 22:46 dev1981, @.***> wrote:

hi Terry, first of all i resatrted my machine and just tested if my two CFGs (Simracing and DUAL) are still appliable. That was the case. NVIDIAInfo_Reboot-Reload-dual.log https://github.com/terrymacdonald/DisplayMagician/files/7718021/NVIDIAInfo_Reboot-Reload-dual.log NVIDIAInfo_Reboot-Reload-SimRacing.log https://github.com/terrymacdonald/DisplayMagician/files/7718022/NVIDIAInfo_Reboot-Reload-SimRacing.log

Then i started the requested tests. I created a clone layout, saved it, checked it. Then the request was to change back to the first layout -> Which first layout?! -> i used my DUAL as first CFG -> loaded it

followed the advices further until;

Next swap back to the second display layout:

Load the second windows display as NVIDIAInfo load second.cfg ??!! ->

which second? cloned? second? -> there i used recently created RANDOM CFG as second.

Then i followed further until i got an error at

Next swap back to the cloned display layout:

Load the second windows display as NVIDIAInfo load cloned.cfg

but continued with the tests until the end.

So i think there might be an issue understanding ur advices correctely. Anyways, i have created a ps1 script which is in the zip which shows what i have done. the first.cfg and second.cfg i copied over from another location because regarding to ur advice they have not been created during that test cycle.

NVIDIAInfo-v1.3.6-test-2.zip https://github.com/terrymacdonald/DisplayMagician/files/7718118/NVIDIAInfo-v1.3.6-test-2.zip

so maybe u can tell me if its messed up. or what went wrong in the test sequence, then i ll do it again.

Maybe it will be easier to meet me here https://discord.gg/pcuUfUwc

grz

Adrian

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/terrymacdonald/DisplayMagician/issues/44#issuecomment-994584931, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLU5LF6BO66ZMMRKWCWXE3URBPXVANCNFSM5FIW77VQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

dev1981 commented 2 years ago

Hi Adrian, I'm based in New Zealand, which is about as far away from Germany as I can get 🙂. I can't really get onto discord at the same time as you I'm sorry, due to the massive time difference. I'll have a look at the logs you sent, and see if I can figure out what's happening. I'll go through your logs in the morning when I wake up, and I'll see what I find. Thanks for all your testing! Terry … On Wed, 15 Dec 2021, 22:46 dev1981, @.***> wrote: hi Terry, first of all i resatrted my machine and just tested if my two CFGs (Simracing and DUAL) are still appliable. That was the case. NVIDIAInfo_Reboot-Reload-dual.log https://github.com/terrymacdonald/DisplayMagician/files/7718021/NVIDIAInfo_Reboot-Reload-dual.log NVIDIAInfo_Reboot-Reload-SimRacing.log https://github.com/terrymacdonald/DisplayMagician/files/7718022/NVIDIAInfo_Reboot-Reload-SimRacing.log Then i started the requested tests. I created a clone layout, saved it, checked it. Then the request was to change back to the first layout -> Which first layout?! -> i used my DUAL as first CFG -> loaded it followed the advices further until; #Next swap back to the second display layout: #Load the second windows display as NVIDIAInfo load second.cfg ??!! -> which second? cloned? second? -> there i used recently created RANDOM CFG as second. Then i followed further until i got an error at #Next swap back to the cloned display layout: #Load the second windows display as NVIDIAInfo load cloned.cfg but continued with the tests until the end. So i think there might be an issue understanding ur advices correctely. Anyways, i have created a ps1 script which is in the zip which shows what i have done. the first.cfg and second.cfg i copied over from another location because regarding to ur advice they have not been created during that test cycle. NVIDIAInfo-v1.3.6-test-2.zip https://github.com/terrymacdonald/DisplayMagician/files/7718118/NVIDIAInfo-v1.3.6-test-2.zip so maybe u can tell me if its messed up. or what went wrong in the test sequence, then i ll do it again. Maybe it will be easier to meet me here https://discord.gg/pcuUfUwc grz Adrian — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#44 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABLU5LF6BO66ZMMRKWCWXE3URBPXVANCNFSM5FIW77VQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

no problem, i am often awake very long. timzone diff is 12 hrs :) so sleep well i ll go to lunch now :D

terrymacdonald commented 2 years ago

Hi @dev1981

Please try and use this new test version of DisplayMagician. It includes the improvements we've made over the last few weeks.

DisplayMagicianSetup-v2.1.1.42.zip

If you get any strange behaviour with a DisplayMagician display profile, please delete the Display Profile and create it again. Then update the Game Shortcuts using that Display Profile so that the use the replacement Display Profile

Please test the following things:

If you can reply back in this issue with information about if it worked or not that would be great!

Thanks Terry

terrymacdonald commented 2 years ago

@dev1981 I've just fixed the GUI display for multiple adapters in DisplayMagician v2.1.1.49 test version. I tested it on another computer with multiple adapters and it worked! So please install this new version and test this to make sure that it shows all your displays correctly: DisplayMagicianSetup-v2.1.1.49.zip

Thanks Terry

terrymacdonald commented 2 years ago

@dev1981 Other people have said that I've now fixed their issues and that the multiple adapters works, even with USB devices. I'm really interested in whether your problem is now solved. Can you please test this new version of DisplayMagician for me?

Please delete all your old DisplayMagician Display Profiles, and then recreate them. Then update your game shortcuts to use the newly created Display Profiles.

DisplayMagicianSetup-v2.1.1.64.zip

If everything is fixed, then I'll close this issue, and prepare for a new version of DisplayMagician!

Thanks Terry

terrymacdonald commented 2 years ago

@dev1981 I couldn't wait any longer, so I released DisplayMagician v2.1.2.3 earlier today. I just got too excited :).

Your DisplayMagician should automatically update, so please see if the issue has gone away once you've upgraded. I'll keep this issue open until I hear back that everything is working, or if it's still broken :(.

Thanks Terry

dev1981 commented 2 years ago

hi terry, no worries, i was a little short of time the last 3 days. i ll check on the release asap. Thank you very much for ur efforts.

dev1981 commented 2 years ago

seems to work fine for me. Displays which are connected to my USB device are shown. Displays which have the state disconnected, are not shown. A soon u enable them in WIN settings they´re present.

terrymacdonald commented 2 years ago

Awesome! I'll close this issue. Thanks for all your help @dev1981.

terrymacdonald commented 1 year ago

@dev1981 I have recently added code so that DisplayMagician knows the rotation of screens on an AMD card, and shows the rotation properly in the UI. I do not have an AMD card, so I need one of my AMD users to test that it works before I am able to release the updated DisplayMagician version to everyone.

I have created a test version of DisplayMagician and have linked to it below. Can you please download, unzip and install this version to make sure it works? Please report back here in this issue so I know even if it works fine, so I know.

DisplayMagicianSetup-v2.5.0.337.zip

Thanks Terry