display profile can't be used as not all displays are connected #348
Comments
|
Hi,
Can you please try creating a couple of brand new display profiles, and try
swapping between them? It could be that there slight tweaks in file formats
in v2.7.2 use causing issues for you.
Creating brand new display profiles let's is test whether it's a problem
with the old configuration files, or it's a problem with the AMDLibrary.
I'm hoping it's the former, as I no longer have the ability to test AMD
graphics cards accurately.
Thanks
Terry
…On Fri, 22 Nov 2024, 11:50 pm StefanS3D, ***@***.***> wrote:
Assigned #348
<#348> to
@terrymacdonald <https://github.com/terrymacdonald>.
—
Reply to this email directly, view it on GitHub
<#348 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABLU5LC3F7GK7WZX4BYXLKT2B4D77AVCNFSM6AAAAABSJCJJZGVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJVGM4TKOBVGQ2TMNY>
.
You are receiving this because you were assigned.Message ID:
***@***.***
com>
|
|
Hello Terry, first of all, thank you so much for the quick response!! but unfortunately that didn't help. That was also the first thing I did in my own troubleshooting. All profiles deleted and recreated. I have now completely uninstalled and reinstalled the program and recreated my profiles again, but without success. the error still exists.greetings Stefan
Gesendet: Freitag, 22. November 2024 um 18:55
Von: terrymacdonald ***@***.***>
An: terrymacdonald/DisplayMagician ***@***.***>
CC: StefanS3D ***@***.***>,Author ***@***.***>
Betreff: Re: [terrymacdonald/DisplayMagician] display profile can't be used as not all displays are connected (Issue #348)
Hi, Can you please try creating a couple of brand new display profiles, and try swapping between them? It could be that there slight tweaks in file formats in v2.7.2 use causing issues for you. Creating brand new display profiles let's is test whether it's a problem with the old configuration files, or it's a problem with the AMDLibrary. I'm hoping it's the former, as I no longer have the ability to test AMD graphics cards accurately. Thanks Terry On Fri, 22 Nov 2024, 11:50 pm StefanS3D, ***@***.***> wrote: > Assigned #348 > <#348> to > @terrymacdonald <https://github.com/terrymacdonald>. > > — > Reply to this email directly, view it on GitHub > <#348 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ABLU5LC3F7GK7WZX4BYXLKT2B4D77AVCNFSM6AAAAABSJCJJZGVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJVGM4TKOBVGQ2TMNY> > . > You are receiving this because you were assigned.Message ID: > ***@***.*** > com> >
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Hello All! I am having the same issue. Everything was working perfectly until the new v2.7.2.1 update. I was wondering if there have been any solutions or updates to this issue? |
|
@KBoose84 can you please provide a description of your hardware/system specs and upload a Support ZIP File for me to compare please? Enviroment (please complete the following information): Windows Version: Thanks |
|
I had the same issue, and disabling the integrated graphics solved it for me. |
|
@styxbe This is a bit worrying as a workaround. This means that there could be an issue with getting settings from a particular integrated GPU. Can you please reply with the environment that you are using where you got the error? Enviroment (please complete the following information): Windows Version: Thanks |
|
Sure, it's a newly built PC so all is latest versions. But I have a special setup with a KVM so that might have an impact: |
|
Was the KVM new, or recently added? Did you update your display profiles after you added in the KVM switch? I ask that because windows tracks the entire path of what devices are connected where, and DM treats ANY difference as being a different profile. It could be as simple as NVIDIA adding a new setting to the list of available settings that can mean the display profiles doesn't match. That's the reason I added the ability to update the display profiles. I have a KVM connected myself and it works ok with DM. So it should be able to work on as long as the KVM isn't doing anything unusual. Thanks |
|
I've had that switch for a while, but this is a new pc build so it was there from the start. Maybe it helps that I did see there was button to update the profiles, but it didn't seem to do anything and the yellow exclamation sign stayed in place. As a test I just deleted both profiles I use, re-enabled the iGPU, and created a new profile for the current config. Which is the 3 displays, nothing is shown for the iGPU which is as expected as there is no diplay connected to it. It immediately got the exclamation sign. The update button does not change it. Then without changing anything or using the switch, I disable the iGPU again, and the exclamation sign disappears, don't even have to push the update button. So in my case it seems to be directly caused by the iGPU. |
|
Ah shoot. @styxbe this isn't good news, as it means there is a bug deep in one of the video libraries, and those are very hard to troubleshoot. Are you willing to help me do some troubleshooting? How technically adept are you at running things in command line? I can put together some instructions for testing that will let me figure out what is wrong, but it is likely to be a pain for you to run the test plan. Are you happy to do this? @StefanS3D Do you have an AMD iGPU as well as a that AMD 7900XTX? I am wondering if the AMDLibrary is at fault here, and is not coping with multiple GPUs. That would explain how it is working in my testing (I have an NVIDIA RTX2070 and an AMD iGPU) and not in anyone elses testing.... @KBoose84 What about you? Do you have an AMD discrete video card as well as an AMD CPU with an integrated GPU? Thanks all for the help figuring this one out. Thanks |
|
Sure, I'll help you out if I can. Have done some coding a long time ago, and used Linux a lot, so command line should be no prob. |
|
Hello @terrymacdonald, unfortunetly i have simmilar issue. I have 2x HP la23006x displays connected via usb and docking station and Samssung g9 display connected via DP to pc. HP displays work fine but with samsung display magician shows "This display profile cant be used as not all displays are connected" Windows Version: Win 11 pro |
|
Hmmm, yet another AMD user. It looks like there is a problem with the AMD
Video Library I wrote. The problem is that I no longer have an AMD video
card, so testing will be a problem. I'm going to have to figure out a way
of getting you all to do some testing and logging for me.
@Lookee94 - Do you have an integrated GPU built intoo your CPU? Or are you
connecting your screens to the discrete GPU only (the AMD Radeon 7800XT)?
Thanks
*Terry*
… Message ID: ***@***.***
com>
|
|
@terrymacdonald samsung screen is connected straight to AMD Radeon 7800XT |
|
@terrymacdonald now i switched samsung to integrated GPU and works okay, so seems descrete GPU is the problem. Sory if i write some nonsene but my IT skills are terribly low :,) |
|
@Lookee94 - I think your issue might be something slightly different. I
think it's best if we move this discussion to a new issue. I'll see if I
can create one later tonight when I finish work.
Thanks
*Terry*
|
|
@terrymacdonald sure, thanks for your support :) |
Describe the bug
Unfortunately, I get the error message for all profiles that the display profile can't be used as not all displays are connected. But all displays are connected.
To Reproduce
Steps to reproduce the behaviour:
Expected behaviour
A clear and concise description of what you expected to happen.
Screenshots
Reporting Logs
DisplayMagician-Support-20241122-1012.zip
If DisplayMagician does not:
C:\Program Files\DisplayMagician\DisplayMagician.exe --traceto create a TRACE-level DisplayMagician.log file.C:\Users\<yourusername>\AppData\Local\DisplayMagician\Logswhich should contain a LOT of detailed TRACE level log entries.C:\Users\<yourusername>\AppData\Local\DisplayMagician\Profiles\DisplayProfiles_2.1.jsonC:\Users\<yourusername>\AppData\Local\DisplayMagician\Shortcuts\Shortcuts_2.0.jsonC:\Users\<yourusername>\AppData\Local\DisplayMagician\Settings_2.0.jsonEnviroment (please complete the following information):
Additional context
Everything was working great until a few weeks ago
The text was updated successfully, but these errors were encountered: