-
-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Nvidia amount of connected monitors greater than 4 #291
Comments
Hi @dev1981, I have some bad news. The NVIDIA driver NvAPI library calculates the maximum number of displays as:
The NVAPI_ADVANCED_DISPLAY_HEADS is 4, meaning that the total number of screens you can have connected to an NVIDIA card is actually 4 * the number of GPUs you are running.
NVIDIA only support a max of 4 displays with their NVAPI video cards through their NvAPI driver, meaning that with a single RTX GPU you will only have 4 max screens active at once. Some video card manufacturers add in additional connector ports, but each NVIDIA GPU will only be able to drive 4 screens at once. I've read that some AMD cards support 6 screens per GPU, and of course if you have an iGPU then you might be able to add another screen that way. With the recent changes introduced by DM v2.6.0, DisplayMagician should now see any video card GPUs you have in your system, as long as it supports the Windows CCD or GDI APIs. This is pretty much any video card made since 2000. But unfortunately with NVIDIA you're restricted to just having those 4 screens enabled at once. If you've managed to get 5 screens from a single NVIDIA GPU then that's awesome, but based on what I've read that shouldn't happen, and I doubt that NVIDIA would support it. It will likely stop working at any stage as it would be considered a bug by them. I'll close this issue as there is nothing I can do I'm afraid! Terry |
hi Terry, sry maybe this was a little missleading. I know that i only can have 4 active displays at once. I was not able to have 5 active at the same time :) What i do is i try to switch from; but When i switch from "1st pair, 2 active" to "1st pair, 1 active" to "2nd pair 3 active (surround)" it works. But if the NV api does not return a max monitor amount higher then 4 youn won´t be able to know if someone has 5 attached. Reagards |
Hmmmm. This is interesting. I wonder why going via the 1 screen profile
works when going directly doesn't? This sounds like some kind of a 'race
condition' based on your timing sensitive comment.
I wonder if there needs to be a bigger delay after surround is enabled, or
some extra checks for the surround configuration to match before continuing
on? I don't know.
Ate you using the latest test version of DM? I think it's 2.6.0.218 in one
of the other issues. If like you to use that so I know that you're using
the one with the latest fixes.
Can you please try to change between the display profiles in the two ways
that you described in your last update and then create a Support ZIP File
and attach it to this issue? I want to see more details about what
DisplayMagician thinks is going on, and loss are great for that.
These test versions of DisplayMagician have TRACE level of logging enabled,
which is as detailed as they get!
Thanks
Terry
…On Mon, 12 Feb 2024, 13:56 dev1981, ***@***.***> wrote:
hi Terry,
sry maybe this was a little missleading. I know that i only can have 4
active displays at once. I was not able to have 5 active at the same time :)
But i was talking about the switch szenario.
What i do is i try to switch from;
"1st pair, 2 active" to "2nd pair 3 active (surround)". This fails on the
first attempt in most cases. (seems to be timinig sensitive as well)
but
When i switch from "1st pair, 2 active" to "1st pair, 1 active" to "2nd
pair 3 active (surround)" it works.
But if the NV api does not return a max monitor amount higher then 4 youn
won´t be able to know if someone has 5 attached.
Reagards
—
Reply to this email directly, view it on GitHub
<#291 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABLU5LG5JESNOD5KEJFHKG3YTFSEVAVCNFSM6AAAAABDCI472CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMZXHE2DIOJSGE>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
so, today i performed a quick test.
--> so on my site it looks like its always neccessary to trigger the profile switch twice, EXCEPT the very first time. My previous conclusion that it will always work going over a single display profile was therefore wrong.
--> seems to be consistent, first switch after reboot works flawless. Every further attempt requires two triggers. Some side notes during testing;
The logs of 13th should reflect all the actions above. Hope this helps. DisplayMagician-Support-20240213-1118.zip grz adrian |
Ok, this is really useful - thanks Adrian!
In your 2024-02-13 10:10 log file there are a few interesting things going
on. I'll try to talk through each one to see if I can understand it better
myself :).
2024-02-13
10:10:46.4527|TRACE|DisplayMagician.Program|NVIDIALibrary/GetNVIDIADisplayConfig:
NvAPI_EnumPhysicalGPUs returned 1 Physical GPUs|
2024-02-13
10:10:46.4527|TRACE|DisplayMagician.Program|NVIDIALibrary/GetNVIDIADisplayConfig:
NVIDIA Video Card is one from the GeForce range|
2024-02-13
10:10:46.4527|TRACE|DisplayMagician.Program|NVIDIALibrary/GetNVIDIADisplayConfig:
Successfully got Logical GPU Handle from physical GPU.|
2024-02-13
10:10:46.4527|TRACE|DisplayMagician.Program|NVIDIALibrary/GetNVIDIADisplayConfig:
No Logical GPU found so no logicalGPUData available.
NvAPI_GPU_GetLogicalGpuInfo() returned error code NVAPI_INVALID_POINTER|
2024-02-13
10:10:46.5017|TRACE|DisplayMagician.Program|NVIDIALibrary/GetNVIDIADisplayConfig:
Some non standard error occurred while getting Mosaic Topology!
NvAPI_Mosaic_GetCurrentTopo() returned error code NVAPI_DATA_NOT_FOUND|
2024-02-13
10:10:46.5017|WARN|DisplayMagician.Program|NVIDIALibrary/GetNVIDIADisplayConfig:
A miscellaneous error occurred. NvAPI_Mosaic_GetTopoGroup() returned error
code NVAPI_ERROR|
Firstly, when you first started this version, it found the NvAPI DLL ok,
and it found a physical adapter, but it didn't find a logical adapter. That
is very odd as it should always find a logical adapter if there is a
physical one! (see
https://docs.nvidia.com/gameworks/content/gameworkslibrary/coresdk/nvapi/concepts.html).
This line specifically spells it out: *A single GPU will have a single
logical GPU handle and a single physical GPU handle. Two GPUs acting in an
SLI configuration will have a single logical GPU handle and two physical
GPU handles.*
So I have no idea why NvAPI_GPU_GetLogicalGpuInfo() returned an invalid
pointer. That might be an NVIDIA driver error, not a DisplayMagician one.
But I might need to do a bit more testing with you to figure it out.
The other two NvAPI_Mosaic_GetCurrentTopo() and NvAPI_Mosaic_GetTopoGroup()
errors are fine, as they mean that Mosaic (Surround) was not enabled at
this time.
…--
There is an error later on though that is a bit worrying. This one is in
the code that patches the saved windows display adapter IDs in the display
profile with the windows display adapter IDs currently in use. This is
needed because windows assigns new windows display adapter IDs every reboot
(thanks Microsoft!). We have to scan the adapters in use and patch the
saved adapter IDs with the new adapter IDs in order to use the old configs.
This error means that we went too far when checking through an array.
I'lkl have to have a dig about to fix that code.
2024-02-13
10:10:47.0781|ERROR|DisplayMagician.Program|WinLibrary/PatchWindowsDisplayConfig:
Exception while going through the display sources list info to update the
adapter id|EXCEPTION OCCURRED :System.ArgumentOutOfRangeException: Der
Index lag außerhalb des Bereichs. Er darf nicht negativ und kleiner als die
Sammlung sein.
Parametername: index
bei
System.ThrowHelper.ThrowArgumentOutOfRangeException(ExceptionArgument
argument, ExceptionResource resource)
bei System.Collections.Generic.List`1.get_Item(Int32 index)
bei
DisplayMagicianShared.Windows.WinLibrary.PatchWindowsDisplayConfig(WINDOWS_DISPLAY_CONFIG&
savedDisplayConfig) ParamName: index
--
The next error is expected. It's due to my use of an Icon extraction
library that throws exceptions when it cannot get an icon from a place, or
if the file has moved since the game shortcut was made. My guess that the
file D:\Spiele\ACC ServerManager V4\AccServerManager.exe was deleted in the
past but still is in a game shortcut or hasn't been uninstalled.
2024-02-13
10:10:52.0164|WARN|DisplayMagician.ImageUtils|ShortcutItem/GetMeABitmapFromFile:
Exception while trying to extract the icon from an *.exe or *.dll using
TsudaKageyu.IconExtractor for file D:\Spiele\ACC ServerManager
V4\AccServerManager.exe.|EXCEPTION OCCURRED
:System.ComponentModel.Win32Exception (0x80004005): Das System kann die
angegebene Datei nicht finden
bei TsudaKageyu.IconExtractor.Initialize(String fileName)
bei DisplayMagician.ImageUtils.GetMeAllBitmapsFromFile(String
fileNameAndPath) NativeErrorCode: 2;ErrorCode: -2147467259
2024-02-13
10:10:52.0164|TRACE|DisplayMagician.ImageUtils|ShortcutItem/GetMeABitmapFromFile:
Exception while trying to extract the thumbnail from an *.exe or *.dll
using WindowsThumbnailProvider.GetThumbnail. Means the file D:\Spiele\ACC
ServerManager V4\AccServerManager.exe could not be processed so skipping it
with this method|EXCEPTION OCCURRED :System.IO.FileNotFoundException: Das
System kann die angegebene Datei nicht finden. (Ausnahme von HRESULT:
0x80070002)
bei DisplayMagician.WindowsThumbnailProvider.GetHBitmap(String fileName,
Int32 width, Int32 height, ThumbnailOptions options)
bei DisplayMagician.WindowsThumbnailProvider.GetThumbnail(String
fileName, Int32 width, Int32 height, ThumbnailOptions options)
bei DisplayMagician.ImageUtils.GetMeAllBitmapsFromFile(String
fileNameAndPath)
--
The next set of issues is here:
2024-02-13
10:27:35.6923|TRACE|DisplayMagician.Program|WinLibrary/SetActiveConfig:
Attempting to change Display Device settings through GDI API using
ChangeDisplaySettingsEx|
2024-02-13
10:27:35.6923|TRACE|DisplayMagician.Program|WinLibrary/SetActiveConfig:
Trying to change Device Mode for Display
\Registry\Machine\System\CurrentControlSet\Control\Video\{5851258A-C78C-11EE-9294-7085C2BF8837}\0000.|
2024-02-13
10:27:35.6923|TRACE|DisplayMagician.Program|WinLibrary/SetActiveConfig:
Testing whether the GDI Device Mode will work for display
\Registry\Machine\System\CurrentControlSet\Control\Video\{5851258A-C78C-11EE-9294-7085C2BF8837}\0000.|
*2024-02-13
10:27:35.7083|ERROR|DisplayMagician.Program|WinLibrary/SetActiveConfig: The
GDI mode change would be unsuccessful because the graphics mode is not
supported. Display
\Registry\Machine\System\CurrentControlSet\Control\Video\{5851258A-C78C-11EE-9294-7085C2BF8837}\0000
not updated to use the new mode.|*
2024-02-13
10:27:35.7083|TRACE|DisplayMagician.Program|WinLibrary/SetActiveConfig:
Trying to change Device Mode for Display
\Registry\Machine\System\CurrentControlSet\Control\Video\{5851258A-C78C-11EE-9294-7085C2BF8837}\0001.|
2024-02-13
10:27:35.7083|TRACE|DisplayMagician.Program|WinLibrary/SetActiveConfig:
Testing whether the GDI Device Mode will work for display
\Registry\Machine\System\CurrentControlSet\Control\Video\{5851258A-C78C-11EE-9294-7085C2BF8837}\0001.|
*2024-02-13
10:27:35.7083|ERROR|DisplayMagician.Program|WinLibrary/SetActiveConfig: The
GDI mode change would be unsuccessful because the graphics mode is not
supported. Display
\Registry\Machine\System\CurrentControlSet\Control\Video\{5851258A-C78C-11EE-9294-7085C2BF8837}\0001
not updated to use the new mode.|*
2024-02-13
10:27:36.1297|TRACE|DisplayMagician.Program|WinLibrary/SetActiveConfig:
Successfully set the display configuration to the settings supplied!|
2024-02-13
10:27:36.1297|TRACE|DisplayMagician.Program|WinLibrary/SetActiveConfig:
SUCCESS! The display configuration has been successfully applied|
2024-02-13
10:27:36.1297|TRACE|DisplayMagician.Program|WinLibrary/SetActiveConfig:
Waiting 0.1 second to let the display change take place before adjusting
the Windows CCD Source DPI scaling settings|
2024-02-13
10:27:36.2408|TRACE|DisplayMagician.Program|WinLibrary/SetWindowsDisplayConfig:
Attempting to set Windows DPI Scaling setting for display sources.|
2024-02-13
10:27:36.2548|TRACE|DisplayMagician.Program|WinLibrary/SetWindowsDisplayConfig:
Setting DPI value for source 1 to 0.|
2024-02-13
10:27:36.2798|TRACE|DisplayMagician.Program|WinLibrary/SetWindowsDisplayConfig:
Setting DPI value for source 0 to 0.|
2024-02-13
10:27:36.2798|TRACE|DisplayMagician.Program|WinLibrary/SetActiveConfig:
Trying to get information whether HDR color is in use now on Display 45315.|
2024-02-13
10:27:36.2798|TRACE|DisplayMagician.Program|WinLibrary/SetActiveConfig:
Advanced Color Info gathered from Display 45315|
2024-02-13
10:27:36.2798|TRACE|DisplayMagician.Program|WinLibrary/SetActiveConfig:
Skipping setting HDR on Display 45315 as it is already in the correct HDR
mode: False|
2024-02-13
10:27:36.2798|TRACE|DisplayMagician.Program|WinLibrary/SetActiveConfig:
Trying to get information whether HDR color is in use now on Display 45316.|
2024-02-13
10:27:36.2798|TRACE|DisplayMagician.Program|WinLibrary/SetActiveConfig:
Advanced Color Info gathered from Display 45316|
2024-02-13
10:27:36.2798|TRACE|DisplayMagician.Program|WinLibrary/SetActiveConfig:
Skipping setting HDR on Display 45316 as it is already in the correct HDR
mode: False|
2024-02-13
10:27:36.2798|TRACE|DisplayMagician.Program|ProfileItem/SetActive: The
Windows CCD display settings within the profile 01_default were
successfully applied.|
In this part we are unable to use the GDI ChangeDisplaySettingsEx because
the graphics mode isn't supported. Looking around the Internet this could
be caused because I hadn't updated the dmFields field within the
DeviceMode, so this is something I've tweaked in the codebase. *This one I
will need you to test for me after I build a new test version of DM.*
Later on in the same file we can successfully apply the GDI settings here
for a different display profile. This points to something being different
between the two structures and I need to find which parts of the Device
Mode structure can be updated and which ones need to stay the same. This
will require a bit more testing help from you. The goal will be to get all
the messages that are shown in bold in the first section above to actually
be the messages in bold below:
2024-02-13
10:31:43.4453|TRACE|DisplayMagician.Program|WinLibrary/SetActiveConfig:
Attempting to change Display Device settings through GDI API using
ChangeDisplaySettingsEx|
2024-02-13
10:31:43.4453|TRACE|DisplayMagician.Program|WinLibrary/SetActiveConfig:
Trying to change Device Mode for Display
\Registry\Machine\System\CurrentControlSet\Control\Video\{5851258A-C78C-11EE-9294-7085C2BF8837}\0000.|
2024-02-13
10:31:43.4453|TRACE|DisplayMagician.Program|WinLibrary/SetActiveConfig:
Testing whether the GDI Device Mode will work for display
\Registry\Machine\System\CurrentControlSet\Control\Video\{5851258A-C78C-11EE-9294-7085C2BF8837}\0000.|
*2024-02-13
10:31:43.5034|TRACE|DisplayMagician.Program|WinLibrary/SetActiveConfig:
Success. The GDI Device Mode will work for display
\Registry\Machine\System\CurrentControlSet\Control\Video\{5851258A-C78C-11EE-9294-7085C2BF8837}\0000.|*2024-02-13
10:31:43.5034|TRACE|DisplayMagician.Program|WinLibrary/SetActiveConfig:
Actually going to try to set the GDI Device Mode for display
\Registry\Machine\System\CurrentControlSet\Control\Video\{5851258A-C78C-11EE-9294-7085C2BF8837}\0000
now (primary display).|
*2024-02-13
10:31:43.5474|TRACE|DisplayMagician.Program|WinLibrary/SetActiveConfig:
Successfully changed display
\Registry\Machine\System\CurrentControlSet\Control\Video\{5851258A-C78C-11EE-9294-7085C2BF8837}\0000
to use the new mode!|*2024-02-13
10:31:43.5474|ERROR|DisplayMagician.Program|WinLibrary/SetActiveConfig:
Display
\Registry\Machine\System\CurrentControlSet\Control\Video\{99F0C8BE-12A5-11EE-9278-0050B66CFEEE}\0000
is not currently in use, so cannot set it!|
2024-02-13
10:31:43.5474|ERROR|DisplayMagician.Program|WinLibrary/SetActiveConfig:
Display
\Registry\Machine\System\CurrentControlSet\Control\Video\{99F0C8BE-12A5-11EE-9278-0050B66CFEEE}\0001
is not currently in use, so cannot set it!|
2024-02-13
10:31:43.5474|TRACE|DisplayMagician.Program|WinLibrary/SetActiveConfig:
Other display settings were changed, so applying all the changes now.|
2024-02-13
10:31:43.6445|TRACE|DisplayMagician.Program|WinLibrary/SetActiveConfig:
Successfully applied the new GDI modes!|
2024-02-13
10:31:44.0138|TRACE|DisplayMagician.Program|WinLibrary/SetActiveConfig:
Successfully set the display configuration to the settings supplied!|
2024-02-13
10:31:44.0138|TRACE|DisplayMagician.Program|WinLibrary/SetActiveConfig:
SUCCESS! The display configuration has been successfully applied|
2024-02-13
10:31:44.0138|TRACE|DisplayMagician.Program|WinLibrary/SetActiveConfig:
Waiting 0.1 second to let the display change take place before adjusting
the Windows CCD Source DPI scaling settings|
2024-02-13
10:31:44.1169|TRACE|DisplayMagician.Program|WinLibrary/SetWindowsDisplayConfig:
Attempting to set Windows DPI Scaling setting for display sources.|
I'll get you a test version later today.
Thanks
Terry
|
And later today is now! |
--> sry mate i think the link for the release is not working? |
Link updater. Sorry I was so keen I clicked save before the upload had finished 😄. DisplayMagicianSetup-v2.6.0.524-devicemode-fields.zip Terry |
--> besides the fact that nothing changed for the switch szenario, it is still required to trigger the profiles twice except the 1st time, but the behaviour changed. --> after switch the context menu still takes 1:30 min to open when surround is active. Regarding the shortcut finding from last time; StartupTime; Grüße :) |
Well this is odd. It looks as though NVIDIA driver doesn't follow its own documentation. My NVIDIA video card also doesn't return LogicalGPU handle just like your error message. This is completely different to the NVIDIA documentation (and I think it's fairly new behaviour). I'm not sure that's actually an issue, but it is unusual to see. DisplayMagician loads the games from Windows, Steam, Epic and the rest, and that takes some time to do. The amount of time completely depends on how many games you have purchased or installed. If people have a lot of games and apps, then the loading time would be longer. That's why I recommend loading DisplayMagician on startup, and minimising on launch. Then you don't notice the loading time as much. I can't remember if I've gotten you to 'Update' your simracing display profile yet? If not, can you please try that? To do so, please recreate your simracing display layout in NVIDIA Control Panel and Windows Display Settings. Then return to DisplayMagician, change to your Simracing Display Profile, and press the Update button. Click Yes to overwrite the DIsplay Profile with the current display layout. Once that's done, please try to swap display profiles, and do the same tests after a reboot. It will be interesting to see if it's something to do with the age of the Display Profile, or if some settings in the NVIDIA driver have changed. Then please reply here with the updates, and please also create and upload a new Support ZIP FIle. Regarding the old ACC Server Manager files, IIRC DisplayMagician checks windows registry for the list of installed programs, so it's likely an old entry left in there. Its no big deal, it just will error and skip adding the entry to the list of available installed programs it presents to the user. Thanks |
sry took me a while to find time for additional tests. I re-created all my profiles and updated them. It diddn´t changed the behaviour. After reboot 1st attempt always works, every further attempt needs two attempts to switch profile. I created new logs for that. DisplayMagician-Support-20240223-1516.zip Then i was thinking a little further. For better understanding reduced my findings to the following two.
---> conclusion for now, a combination of SURROUNDED monitors AND monitors connected on my USB-docker require two attemps.
during all that profile switching tests i always performed as well the "how fast does the context menu open after switch test" There must be a handle or sth. which prevents the menu from opening. Only two szenarios had a significant opening time after switch. ---> Surround things have in both cases an impact. The second archive contains all the logs for this combination tests DisplayMagician-Support-20240223-1600.zip These are my combinations so far. 04 & 05 have issues i hope this will be usefull :) to make DM even better. At the end its not a problem for me personally :) and maybe i am the only guy which faces that issues. reinstalling windows on a different harddisk and test again might sort out that my machine is somehow tinkered. greetings Adrian |
Thanks @dev1981 This is great stuff! So it looks as though the USB-Card connected monitors is causing the issue. I still don't have any idea why or how, but to start the investigation process can you please reply with the make and model of USB connected screens, and the USB Video Card that they connect into? I don't have any experience with USB connected screens myself as none of my systems have them in use. So if you use any particular software, or any hardware adapters or anything please describe to me how they are connected so I can understand it all. I will then do a bit of a review to see if there are any other issues listed within your Support ZIP File. That will hopefully show up some particular information about where the issue may lie. Regarding the significant opening time issue, this is unfortunately a problem with the NVIDIA driver. Any time that surround is activated or deactivated there is a significant delay (up to 25 seconds on my test system). This is due to the need for the screen layout to be set up/torn down by the driver. If you think about it the driver and windows have to do a lot of work to get everything set correctly - turn on the displays, link them into a single display, install the NVIDIA screen layout shim, recalculate the windows display canvas, change the primary display and recalulate the display coordinates, reapply HDR settings and scaling, align all the windows taskbars then move all the windows to the correct locations. It's quite a bit to do. The upshot is that there is nothing I can do to speed that up. It takes as long as it takes. DisplayMagician does try to compare similarities within the current display profile and the one you want to swap too, and it only changes the things that are different, e.g. if you have HDR already set and you want it set the same in a different display profile then it leaves the HDR settings alone. This helps speed up the settings that don't use Surround, but unfortunately Surround profiles are just so complicated and move so many screens that none of those optimisations work. Hope that explains things a bit clearer? Thanks |
Hello, I had to open a GitHub membership just to make this comment. First of all, thank you for this wonderful software. The reason I wrote this comment is that I use 3 screen surround + 4th monitor in my simulation system and a solo monitor on my desk (that is, I use 1 or 4 monitors at the same time on my graphics card with a total of 5 monitors connected) and I am experiencing the same problem as @Dev198 My monitors do not have a USB connection, I only use HDMI and Display Port, but I have exactly the same problem as written, sometimes a double click is required, sometimes it gives the error that the monitor is not detected and I have to manually switch it myself, sometimes it works without any problems. I hope this problem gets resolved because I'm sure we're not alone. |
Hi,
I recognise this is an issue, and I've been working over the last month or
so to try and fix this issue. I've moved from my NVIDIALibrary code over to
a customised version of NvAPIWrapper in my test code. It currently worked
properly with display configuration, but it now isn't working with surround
display grid setup (NVIDIA surround).
I'm constantly writing on this issue, but it is complicated, as I'm having
to figure out how to make unmanaged structures in memory that work
correctly through p/invoke with the NVIDIA driver. NVIDIA's documentation
is woeful, meaning that I'm having to reverse engineer how it works or copy
similar code from elsewhere.
Thanks
Terry
…On Tue, 7 May 2024, 5:03 am AlpYenigun, ***@***.***> wrote:
Hello, I had to open a GitHub membership just to make this comment. First
of all, thank you for this wonderful software.
The reason I wrote this comment is that I use 3 screen surround + 4th
monitor in my simulation system and a solo monitor on my desk (that is, I
use 1 or 4 monitors at the same time on my graphics card with a total of 5
monitors connected) and I am experiencing the same problem as @Dev198
<https://github.com/Dev198>
My monitors do not have a USB connection, I only use HDMI and Display
Port, but I have exactly the same problem as written, sometimes a double
click is required, sometimes it gives the error that the monitor is not
detected and I have to manually switch it myself, sometimes it works
without any problems.
Here my setup:
Ekran.goruntusu.2024-05-06.200101.png (view on web)
<https://github.com/terrymacdonald/DisplayMagician/assets/107697979/e3265cca-379b-4eab-9faf-2050f10e38f3>
I hope this problem gets resolved because I'm sure we're not alone.
—
Reply to this email directly, view it on GitHub
<#291 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABLU5LGQ4IFI44QS2JCXH4LZA6ZXTAVCNFSM6AAAAABDCI472CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJWGUYTAOBYGE>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
Hi Terry,
maybe you can remember i was telling you some months ago, that i always have to apply my SimRacing Profile twice until it gets loaded.
So for now i guess it is because i have 5 monitors attached to my NV card but NV only allows 4 ACTIVE connections at one time (even if the card has 5 ports). Sometimes the switching was a little bit lazy, that means sometimes it works still with the first attempt to switch.
So by changing from 2 Active to Tripples (Surround) does not work directely in most cases.
But if i switch previousely to 1 active display and then the switch over to tripples, it works. I tried it with the release mentioned in Issue #193.
Maybe you or someone with 5 Monitors attached can confirm this behaviour. Maybe its fixable by dropping one active display which
won´t be in the target profile.
Thank you for your great work on that tool.
Regards
Adrian
The text was updated successfully, but these errors were encountered: