Search results

The new v1.11.2 version is almost ready. You will now see this message during startup:

Hi Clement, Yes, please write/contact Nvidia. We will also contact them but from our experience they respond faster when they get feedback from multiple sources. They'll also see this crash in their logs from Microsoft when BSOD crash occurs but God knows how long it will take for them to...

I have managed to start Remotly without crash on the Hyper-V VM running with Nvidia. To do so you need to rename this file (on the VMs file system): C:\Windows\SysWOW64\nvencodeapi.dll to another name for example: C:\Windows\SysWOW64\nvencodeapi.dll_ This way Remotly won't find it and will not...

I give up :( The crash is in nvencodeapi.dll. The same dll is used in non-VM (physical) system and it works fine there. If AMD will work then this is Nvidia's bug. BTW All Nvidia HW video decoders work fine from the Hyper-V VM.

I know more now. As expected the crash happens during querying GPU encoder capabilities. It might be something with HDR.

I will start by disabling GPU initialization of various modules. I hope I can find what is causing this in less than 2 hours ;/ Anyway, I think this should be reported to Nvidia. Imagine a server with shared GPUs in a datacenter and someone runs this... This is surely a bug in Nvidia drivers...

Ok have the same problem on RTX 2080. The entire PC crashes (SYSTEM_THREAD_EXCEPTION_NOT_HANDLED).

Hi Clement, I'm still setting up Hyper-V on a dual Nvidia RTX system. In the meantime please find how I have made it work on the Intel GPU system: 1. Install git if you do not have it 2. Clone the Easy-GPU-PV repository - run PowerShell with admin rights, go to the directory where you want...

Theres is another one for GPU memory. I will paste it here soon.

I'm wondering why does parsec need this virtual driver installed on a VM... These drivers have poor performance. They must use it for setting up virtual displays I guess. I'm sure we will fix these problems soon Clement. Thanks again for your cooperation regarding this! I will later write a...

Did you disable "parsec virtual display driver" or uninstall it completly? (Is it still on the list)

Did you use 2 Easy-GPU-PV scripts? One was for installing drivers and the other one for GPU memory? I will send how I used the scripts soon. I'm setting up Hyper-V on Nvidia and AMD now.

Funny thing... It only works properly when running Remotly with admin rights :) BTW do you have the "Enhanced session" enabled? Remotly works ok in current 1.11.1 version but only when "Enhanced session" is disabled. In the new 1.11.2 version it works with and without "Enhanced session".

I have no idea why but it works! Now I can use HEVC low power GPU encoder on the Intel UHD 630 in the Hyper-V VM with GPU acceleration. But now I do not see the "Microsoft Remote Display Adapter" in the Device Manager under "Display Adapters". Can you let me know which devices do you see in the...

First bug fixed. Remotly will now work (from v1.11.2) properly in Hyper-V non-GPU accelerated mode both with and without admin rights.

I'm removing parts of the DXGI/D3D/Encoder code step by step until the crash is gone. This way we will find what causes the crash. There are some old D3D9 related parts of the code that might be problematic (Intel developers are no longer testing D3D9 in their driver releases ;/ ) I hope that...

OK. I have managed to start the VM with Easy-GPU-PV. I have this crappy UHD 630 mounted in this PC. As soon as I start Remotly (even without admin rights) I get a BSOD ;/ But the BSOD crash is only in the VM. The physical PC is working OK.

I have ended up using Easy-GPU-PV scripts...

I will also try to set "GPU passthrough setup with Hyper-V".

Hi Clement, I have just started a simple VM with MS Hyper-V Manager. It uses Microsoft Hyper-V Video as a display adapter... It seems to work without problems but only without admin rights. When Remotly is installed and run with admin rights I see the login/lock screen, but on my local display...