virtual display driver does not seem working well with booter process only -- FYI only

[hhspiny]

Use booter process only (i.e. remotly does not run in user's account) and remotely virtual display driver installed. when the monitor is turned off, get blank screen and failed to connect msg, most of the time. sometimes, for a short period after rebooting, can connect.

works fine with a dummy HDMI dongle.

not a problem for me. just FYI. as everything else seems to run very well using the booter process only.

 

[mirillis]

Hi hhspiny!

Thank you for reporting this. We will try to fix it in 1.32.0 (it's almost ready and will be released this week).

In 1.32.0 it is possible to send files on other accounts using the booter/service account (currently only using SendTo context menu but at least it is now possible).

Another new feature (there will be a lot of improvements) is that after pressing "next diaplay" you will also see all displays in one video (with remote control of course).
For example when you have two displays A and B the sequence will be A, B, AB...

 

[mirillis]

Problem with Virtual Display and booter service has been fixed.

 

[mirillis]

https://downloads.mirillis.com/files/beta/remotly_pc_1_32_0_setup.exe

It's not public, yet. File transfer from booter/service account should be possible using "Send to" context menu (no progress will be visible on the host but you will see progress under the taskbar icon on client side).
Virtual Display should work in any situation without HDMI dongle.

Full list of changes will be released tomorrow.

 

[hhspiny]

seems to be working now, but the virtual display and file transfer with booter process only. thanks for the update.

will test more and report back. in previous versions, sometimes it worked right after rebooting, but after a while, got blank screen.