Launching Remotly in Hyper-V VM cause the ENTIRE PC to crash

[mirillis]

YES!!! Please disable it! This will use the cloud server for connection (probably the one in Amsterdam which is closest to you as the one in Paris is not running yet).

Please check the screen below with description what to do to force P2P:

Make sure to set "Force Connect Anywhere" to "no". Each connection to different devices has it's own set of settings.
If you have it already set to "no" then there is another problem that the physical machine to VM connection cannot connect in P2P and will switch to Cloud streaming automatically.
BTW. Never use the "Compatibility mode" for gaming... this option is only intended for remote support companies who connect to some old PCs that have drivers outdated and cannot use HW acceleration and performance optimizations.

 

[mirillis]

You should not never see this icon (marked with the red arrow) during P2P connections. When this icon is visible it means that cloud streaming is used.

 

[ClémentRED]

"Force Connect Anywhere" is off and I have this icon. But it seems enabling custom P2P ports without changing anything worked and is really P2P. when disabled, it come back to connect anywhere.

 

[mirillis]

Sometimes using the P2P inbound/outbound ports in Remotly Settings on PC will help. But I also had to set some things on the router to make it work for me.
BTW, You can also set the outbound port on the Remotly for Android app, also in the Settings (I'm using this option from my home to connect to games running in our labs via P2P).

 

[mirillis]

We have just done some tests:
1. Connect from one PC running some old GTX to a PC with AMD RX5700 using P2P.
2. First test was to connect to VM on the PC with RX5700 the lag is minimal but the video is not smooth ;/ It looks around 30-40fps (similar effect is visible without connection just using the desktop on the VM, dragging windows around is jerky and not fluid)
3. The same test to physical machine with RX5700... no lags and smooth video @60fps

 

[ClémentRED]

I tried to connect to my PC having a GTX 1080 Ti with my pretty old laptop and when in "quality mode" i have >1s latency ! even when in performance mode it's unplayable and do a huge visual glitch where everything is some random color every x seconds for a few seconds ...
With Intel quicksync decoder or something ... And I can't send you an image of the bug for some reason

 

[mirillis]

1s in the same network? That's hard to imagine even with SW video decoding. Can you let me know what Intel GPU is in the old laptop?
1s lag could happen when connecting using Connect Anywhere via Singapore or Sydney...

 

[mirillis]

I'm always using an Android phone with Remotly app to double check connection quality if a problem between PC to PC connection is visible.

 

[mirillis]

I think our Game Virtualization Technology will give much better results soon. This technology will allow connecting and controlling any game remotely and use the same PC by another person at the same time.

 

[mirillis]

Nvidia hyper-v vGPU support (BSOD) has been fixed in v1.17.2 for PC:

Download

Download Remotly and start playing and working remotely wherever and whenever you want.

remotly.com

The bug is still in the drivers that do not support asynchronous encoding in Hyper-V mode.
We are now using synchronous mode for Nvidia in Hyper-V.

 

[hhspiny]

I have had success running hyper-v vGPU with remotly in VM and utilizes hardware encoding, with Nvidia 4060 card.

changed to AMD 9845HS and only use the iGPU. now remotly crashes the VM (not the host) upon starting remotly . tried to turn off hardware encoding, still crashes. if disable the vGPU in VM, remotly runs fine.
however, for a couple of times (of uninstall/reinstall), it actually worked for a bit until the next reboot. not sure if it is from hardware encoding (which was not actually turned off).

BTW, it would be nice to have the remotly detecting crashing when hardware encoding is on and next time of reboot, disable it. otherwise, there is no way of turning hardware encoding off to avoid crashing.

 

[mirillis]

We experience serious problems on the VM with Nvidia 4060 after updating to 24H2 Win11. There are some strange artifacts visible on screen (this does not happen in compatibility mode and also on VM with AMD iGPU which is also present on this PC).

We will add crash monitoring on the VM when hardware acceleration is available/used.

 

[mirillis]

Hi hhspiny,

I'm not sure if this will be OK but for start after detecting that Remotly has started on a VM and it did not finish initialization properly we will disable initialization of the vGPU which did not initialize properly during the previous crash.

BTW. We have our own vGPU installation scripts almost ready (after starting Remotly you will get a message that a Hyper-V VM was detected and which physical physical GPU should Remotly use as vGPU for the VM). This (+ the Remotly Virtual Audio Adapter) will remove usage of any external scripts or drivers. Remotly will support everything out of the box.