Issues with Mosaic

[pressRtowin]

I posted the issue a while back about mosaic support, and it looks like there is indeed an issue with mosaic now. My friend and I have the exact same system, except he has a Quadro P3000 and I have a GTX 1080 Ti. I've been using Helios just fine with surround on my system, but when I cloned his mosaic profile and took a look at the JSON, i could instantly tell it looked off (does't have the individual displays listed under it). Trying to apply the configuration fails with a message that the display configuration has changed since the profile was created, and to remake it.

I also tried manually adding the surround topology by grabbing the display IDs as was mentioned in one of the previous bugs, and I still could not enable mosaic using Helios after it was disabled.

[falahati]

Hello again @pressRtowin,

Well, from what I know, the code to apply and to retrieve topology of a Mosaic setup is same as Nvidia Surround setups. In fact, they retired their Nvidia Surround API in favour of already established Mosaic API.

However, it is possible and quite likely that my implementation is not compatible with extra information or formatting of real Mosaic topologies.

For me to have some idea about this, however, I need at least the JSON file created with his setup and some basic information about his configuration that can be extracted with the following steps:

1. Download the HeliosDisplayManagement.Reporting.zip file.
2. Extract it to the desktop. (or somewhere with write access for your user account)
3. Execute the program and wait for it to end, then press Enter to exit.
4. This will generate a log file right next to the program, rename this newly created log file from "HeliosDisplayManagement.Reporting.XXXXX.log" to a meaningful name, for example: "DisabledSurround.log" or "AllMonitorsExtended.log" so I know what the log is about.
5. Switch to other modes (using Windows Control Panel and NVidia Control Panel) and repeat these steps.

At the end of this process, you should have multiple ".log" files each generated while your system was in a correct mode. I need this information as I need to follow the program's logic based on your system while you are in a specific mode. Send these log files to me. Feel free to check the log files for any information you might not want to share with the public.

[pressRtowin]

I don't have access to everything right now but I can tell you some of what you need off the top of my head.

• the surround topology field simply read "null" with none of the subfields listed.
• all the other fields looked correct, compared to my surround profile, with one difference. Mosaic does not rename the display name as surround does to "NV Surround". It just used the same display name as the displays. (I confirmed this was correct in device manager while mosaic was active.)
  When I get a chance, I'll follow your instructions above and send you the logs.

[falahati]

Thanks, these two changes was kinda expected. But to know why the topology field is null I really need the log files both with extended and Mosaic enabled. thanks

[pressRtowin]

Just got them! here you go.

AllMonitorsExtended.log
3xMosaic160BezelCorrection.log

[falahati]

Please try the latest version (9.5.0) and report back.

[pressRtowin]

0.9.5.0 seems to have fixed the mosaic issue. What did you end up needing to change? We're now able to switch back and forth between multiple mosaic layouts and extended properly. Thanks! Mosaic is so much more of a pain to work with than surround since it doesn't let you swap between bezel corrected/non bezel corrected and multiple resolutions without going through the whole setup again, and this tool is making it much more manageable. I'll be sure to let you know if we run into any unexpected behavior.

[falahati]

Happy to hear that.

I just found another way to detect the surround display instead of checking the name for "NV Surround" or manufacture for "NVS" by checking the Device's Instance Id. Don't know how much this method is reliable; especially if there are more than one Mosaic topology (unline Nvidia Surround, Mosaic allows for multiple topologies to be active at once). So feel free to report problems here again.

In the meantime, I am going to close this issue.