We're currently working on multi monitor fitness simulation and require a multi-window configuration for the Windows UWP target platform which unfortunately doesn't support Multi-window natively. Our project relies onmultiple monitors and Bluetooth sensor integration with Bluetooth code that's tailored specifically for Windows UWP, and unfortunately, it doesn't function properly when applied to other target platforms. I've explored Unity's official documentation on multi-display setups (https://docs.unity3d.com/Manual/MultiDisplay.html), but it appears that this method isn't compatible with Windows UWP, as discussed in this forum thread: https://forum.unity.com/threads/how-to-support-multiple-displays-uwp.425926/. According to the responses there, there appear to be three potential solutions and we found 2 more that we're considering: One option is to acquire an asset designed for multi-monitor support in Windows UWP, such as the one available at (https://www.republicofhandball.com/assets/) as posted here. However, this solution raises some concerns since it's not on the asset store and could be a bit shady. (Questionable source.) Another possibility is to create our own secondary monitor functionality using Windows API, a more hands-on approach that would require quite some coding. as described here. (Maintenance Challenge) We're also contemplating the idea of rworking the Bluetooth code to function beyond the limitations of Windows UWP, potentially utilizing resources like https://github.com/adabru/BleWinrtDll or insights from this thread: https://forum.unity.com/threads/bluetooth-low-energy-on-windows-under-unity.509387/. (Strategic Shift) Another approach is using Nvidia Surround alongside viewport rect with dual cameras to simulate a second monitor. Lastly, we're considering the option of developing a separate application specifically designed as a secondary monitor, which could communicate with the main application via UDP or another suitable method. (Communication and Sync Issue) Given that the most of the referenced threads above date back to 2013, there's a possibility that there's now a different, built-in solution available. We need your guidance: Are we overlooking any potential approaches, or is there a recommended solution among these? Your insights would be greatly appreciated.