Request installation option to turn-off hardware acceleration completely

[hhspiny]

even more interesting, with the setup from above

inside remotly session, connecting to the VM. can load the UI fine in normal user account. can also login to admin account, but UI does not show up (although remotly.exe process is active), even if kill the process and re-run it. rebooted multiple times, same.

On the other hand, on the server's consol, connect to VM via hyper-v terminal, loading UI in normal user account or admin account crashes VM.

almost there, game inside VM via remotly.

 

[mirillis]

It works OK in booter mode with hardware acceleration when there is no UI?

There is still one other option. The problem might be with remotly_x86.bin or remotly_x64.bin processes which I think are not used by the booter.

 

[mirillis]

I will prepare remotly_wincore.dll which works the same for full version and booter version (not start .bin helper processes).

 

[hhspiny]

Correct. Works fine as long as UI is not showing. Including booster with hardware encoding in VM

 

[mirillis]

Hi hhspiny,

Sorry it took so long.

Please check the file below:

https://downloads.mirillis.com/files/beta/remotly/remotly_1_32_1_test.zip

Please overwrite files in Remotly installation folder with these new files (all are digitally signed)

It includes files that will be used in 1.32.1 update.
These files include the following changes:

1. Adds support for new test registry "ForceVmWorkaround" (please create just like before and set it to '1')
This registry forces Remotly not to use low-level capture engine. Please make sure to use the virtual display adapter and set it to use the GPU-P.
Additionally it is highly recommended to use Windows->Settings->Display and make Windows use only the virtual display (Show only on 2).
Moreover please go to Windows->Settings->Display and find the "Graphics" option. Please make sure Remotly is started on the GPU-P - High Performance and not Hyper-V).
To make sure ForceVmWorkaround is used you can use Task Manager to check there are no remotly_x86.bin and remotly_x64.bin running.

2. New UI design for Remotly settings
3. Fixed "Share specific monitor" not showing all displays after Remotly Virtual Display initializes virtual display
4. Critical fix for remotly_svc.exe (memory leak)

 

[mirillis]

BTW. There are also log files for these .bin files. They are also located where the previous log files were.
Can you let me know if you see a file named "action_bin_x64_log.txt" in C:\Users\<user name on your hyper-v>\AppData\Local\Mirillis folder?

 

[hhspiny]

the good news is that VM does not crash anymore. the bad news is blank screen. reproducible.
Apply the patch and other suggest setting, reboot VM,

the first problem:
1. remotely client connecting to windows login screen, login to admin fine.
at this point, remotely UI does not show up at all, and no icon in notification area. remotly.exe process is running.
2. run remotely manually, nothing happens.
at this point, can disconnect and reconnect from remotely client fine.
3. login via hyper-v terminal into admin account, the remotely UI loads automatically. close hyper-v terminal
at this point, got two remotely instances now. and remotely client gets blank screen !!!

the second problem: reboot VM again
1. run #1 and #3 above to avoid two instances
at this point, even in hyper-v terminal, no remotely UI at all
2. close hyper-v terminal
at this point, remotely client gets blank screen !!
3. connect hyper-v terminal, without login, terminal shows windows login screen
at this point remotely client gets blank screen !!
4. in hyper-v terminal, login to admin, keep terminal open
!!!remotely works again !!! but no remotely UI, no notification icon.

 

[mirillis]

Thbak you so much!

I will try to replicate these problems running the same test scenarios.

I do not undestand one thing. The new test version should work just like the booter but with UI.

"the bad news is blank screen. reproducible".
By blank do you mean the video on the Hyper-V is not refreshing looking at it locally? Or is it black after connecting remotely?

I also see a blank screen after selecting "show only on 2". But after connecting it works.

 

[mirillis]

BTW. We will prepare new remotly_x86.bin and remotly_x64.bin with more logs. This way we will be able to exactly locate the place where VM crash happens. It would be ideal to make the original version work without any workarounds.

 

[hhspiny]

When I say blank screen it means when connecting remotely client to the server, client has blank screen and after a few seconds says reconnect or disconnect.

In summary... booter works before remotly.exe loads after login. The Remotly.exe can't show UI. Once remotly.exe runs, needs hyper-v terminal connected AND login to avoid blank screen. VM has remotely virtual display driver installed.

VM setting system display does not show multiple monitor option. In fact, most options such as resolution are grayed out.

 

[mirillis]

We are working hard on making booter work with low-level capture engine in Hyper-V with GPU-P and virtual display.

We see similar problems discussed in this thread on a Hyper-V VM running with Intel UHD 630 GPU as GPU-P. Now everything works like a charm with best possible performance and hardware acceleration. We still need to add this to the full version on non-admin account.

I will upload a test version as soon as it is ready and stable.