Quadro Mosaic Support?

[pressRtowin]

I didn't have much hope, but I tried this tool on my ZBook 17 G4 with a Quadro P5000 but (as I expected) it does not successfully switch to a Mosaic profile. Is there any chance of implementing this in the future, or is the implementation of Mosaic too different from Surround? I really wish the Nvidia Control Panel saved profiles for Mosaic, rather than making me go through the setup every time.

[falahati]

In fact, they are same. NVidia ditched Surround API in favor of Mosaic a while ago. However, this project is by no means complete and bug-free. You can try suggestions provided by other users on other issues and see if you can find a solution to your problem in there.

Also if you are familiar with programming, you can always dig deeper and use the underlying library I wrote for this application available here: https://github.com/falahati/NvAPIWrapper

I have yet to find some time to fix problems with the mechanism in which this application applies the profile and detecting devices to solve a lot of these possible problems and shortcomings.

Can you describe your display arrangement and what you get in the application while the arrangement is active? What is your problem exactly?

[pressRtowin]

I'm able to save both an extended layout as well as the Mosaic setup in Helios. If I'm already in Mosaic, activating the extended layout works fine, but from extended, activating the Mosaic profile goes through the entire countdown process, but then does nothing. If I first go in to edit the Mosaic profile, then click save and apply, it says something along the lines that the profile is not valid.

My current setup is 3x 144Hz 2560x1440 displays in a landscape configuration (1x3). Two displays are DisplayPort 1.2. The third is HDMI 2.0.

[falahati]

Right. This seems like the description other users provide about the bug which results in an incorrect profile structure saved to the disk in #2 and #5.

The solution to this at this moments seems to be about editing the profile file and making sure device paths and device names are correct.

@amasover wrote a simple tutorial about how to do so here: https://gist.github.com/amasover/f7de08f8f247203725cc12c1de449300

And based on the feedback from @Zenairo, it seems that you can use NVAPIWrapper (https://github.com/falahati/NvAPIWrapper) sample project instead of OSVR as mentioned in the tutorial.

If you failed to solve the problem using the information provided above, then you should wait for a new version and honestly there is no clear deadline for that. Unless someone else considers contributing to the project, finds the bug and solves it. Its open source after all for the same reason.

[pressRtowin]

Thanks for the info! I'll check those out

Kinda relevant question. I have a bug on my system where if I reboot the system while Mosaic is enabled, upon booting, it remains configured with the correct layout and resolutions, but locked to 59Hz. This happens even if I edit and/or remove all the 59/60 Hz resolutions using CRU so that only 144Hz is able to be selected when originally configuring and enabling Mosaic (before the reboot). Once it is in this state, I cannot edit the Mosaic configuration (edit dialog will open, I can press apply after making changes, but no changes actually apply), or disable it from Nvidia control panel. The only way to disable is to reboot with one display unplugged.

The relevant part: Have you heard of this, and can this tool work around this?

[falahati]

It might. But I am not sure. What you can do now to see if it works is to disable the Mosaic mode, save a profile in the Helios and then enable Mosaic again and try a reboot. Based on what I understood from your description, after the reboot, you should not be able to disable Mosaic using Nvidia control panel. So if you managed to disable the Mosaic using this tool at this stage, then there is hope that it can help you if you also manage to solve the problem with the saved profile.

[pressRtowin]

I regret to report that @amasover's solution does not work for me. I followed everything but it simply won't apply.

I wasn't sure if by "Make sure this virtual montor has a name of NV Surround).", that meant I should just check to make sure this is the name of the surround display (it wasn't. mine used the same display name as my normal displays), or if I was supposed to actually change it. I did it both ways and it made no difference.

[falahati]

Hey @pressRtowin,

Please follow this problem in the #2. I am going to close this one as a duplicate as it probably is.

I just posted some instructions on the other issue, please follow them and report back. Thanks