Screens broken when returning to physical desktop.

[ali_vfx]

Hi I have a z840 with a quadro m4000 gpu - sender and a macbook pro retina 2015 reciever.

To get things to work I had to uncomment "Rgsender.Compatibility.Displays.ForceEdidOnHeadless=1" in the config file on the sender.

This allowed the macbook to connect. However on returning to the z840 physical desktop "human sat in front of two monitors". The screens where black. Powering on and off did not fix this. I had to resort to unplugging both monitors and replugging into different ports on the gpu. Luckily my gpu had 4 ports.

Im in a situation where my workstation monitors are physically powered off when nobody is at the workstation. If this helps.

Great if anyone has a solution to this?

[BeckyN]

Hi Ali_vfx, When the Human sat in front of the screens were you still connected via Remote Boost? RB blanks out the screens when a connection is active for privacy reasons. If a RB connection wasn't active, we'll want some add'l information like exact macOS on Receover and Windows build on Sender and RB versions on each. And: did the Remote Boost connection end normally?

Becky

[ali_vfx]

Hi the session was closed properly on the receiver, app quitted, this has made rgs unusable for us.

Unplugging the monitors from the GPU and plugging into different ports of the m4000 allowed me to get my machine back, but left the displays in a strange state, windows refused to change the resolution etc, I had to use the nvidia software to change my display resolution back, this was far from ideal.

Reciever build = OSX 11.1 Big Sur - Same issues on last versions of os also

ZCentral RB 2020.1.1 MacOS Receiver (M39128-002.tar.gz)

Sender build - Windows 10 pro 20H2 19042.685

ZCentral RB 2020.1.0 Win Sender-Receiver (M39124-001.zip)

[KellyRGS]

When using our headless EDID property in the rgsenderconfig file, to re-attach displays you will need to disable the property, and restart the sender service.  Now as you have figured out, you might be able find ports on the graphic card where the EDID file did not load, and attach a display.  Not sure what display you have, but if they are HP displays, we have a setting that sets them to always active, even when turned off.  This keeps the EDID from the display from disappearing and not getting a black screen when connecting.  If this is not an option, then exporting an EDID file from the displays and loading them using the NVIDIA control panel to go headless.  You should be able to plug in a display without issue using the NVIDIA control panel.  I have attached a document on this.  This document walks you through setting up headless with the HP Z4R, but applies to an NVIDIA Quadro system running Windows.   Let me know if you still have issues.

[ali_vfx]

Hi,

I Shall look into this and report back, however, can I ask why these things are so complex? I have zero issues with, MS rdp, Anydesk, Teamviewer etc, etc, etc. But this solution unlike the rest does not work out of the box for many customers, why is this? 

I wanted to utilize hp's solution, as it is advertised as being superior and much quicker, but when it is so complex to make work, it becomes pointless. I had to edit the EDID config just to make it work as a last resort, I did not want to go messing with config files.

The machine I was testing on has two monitors attached, one is Dell, one is a Asus. Im not sure you need the exact models but please let me know if so?

Are these issues being worked on for a future upgrade? This software seems to be "beta" at best and I would never run it as my sole solution atm, however, it is marketed as outstanding, really strange. Can you explain this?

[KellyRGS]

Remote Boost uses NVIDIA for resolution matching.  If that fails, Remote Boost falls back to the OS to do the resolution matching.  When not using displays on a sender, making it headless, you either need to modify the rgsenderconfig file property to load the EDID that is built into Remote Boost, or attach a display that meets all of the resolutions you want, and then export and load the EDID on the port that the display is attached to.  I have used TeamViewer and RDP, and I think they may load their own driver for viewing headless systems, haven't checked what it actually shows in Device Manager when using those remote protocols.  Unfortunately using the built in Remote Boost EDID file, you have to go back in and disable the property, change it back to 0, do not comment, and then restart the sender service to connect a display again and not get a black screen.  Not sure why your displays were left in a strange state.  When you ended the session, did the you use the red X in the right corner, or sign off from Windows to disconnect?