Bypass script for Laptop GPU

[cyberquarks]

When trying to run Precheck:

.\PreChecks.ps1
WARNING: Computer is a laptop. Laptop dedicated GPU's that are partitioned and assigned to VM may not work with Parsec.
WARNING: Thunderbolt 3 or 4 dock based GPU's may work

How do we bypass this check? In the past I have managed to run Parsec on a VM on a machine with GVT-g, the machine is quite old HP EliteDesk 800 g2 mini and Parsec runs fast.

What I am trying now is for a Surface Book 2 laptop with GTX 1060

[jamesstringerparsec]

If you are running Windows 11 you can edit the VMName in copyfilestovm.ps1 script from AUTO to the exact name of your Intel GPU. If you're running Win10 it will only pass the GTX 1060 which won't work with Parsec in this situation.

[cyberquarks]

I'm using Windows 11 host, Intel UHD 620 worked at 40 fps (tested with Surface Book 2); I haven't tried GTX 1060, since I think it needs a cable to be plugged into the display port so it [parsec] would capture the display.

[shinwa]

If you are running Windows 11 you can edit the VMName in copyfilestovm.ps1 script from AUTO to the exact name of your Intel GPU. If you're running Win10 it will only pass the GTX 1060 which won't work with Parsec in this situation.

I am using a AMD + Nvidia 3080 gpu laptop on Windows 11, I've succefully pass GTX 3080 to vm. RDP works fine while parsec doesn't, it keeps saying "Error [-14003] The host could not capture the screen". Same setup worked on Windows 10 with both AMD Raedon and Nvidia 3080 are pass to VM.

My questions are:

1. Will only integrated GPU work under Windows 11?
2. Can I pass both integrated and dedicated GPU to Vm to make Parsec work again?

Any other suggestions that allow me to play games using Nvidia GPU in VM on high performance laptops?

[KarlK0ch]

Same problem here.

Using amd and nvidia 3060 laptop with windows 11. Passed the gpu through by disabling the onboard gcard. VM is running smooth but host is very laagy. Same error on parsec. Would really need some help, too

[javaarchive]

I can confirm @cyberquarks 's suggestion, indeed even with virtual display driver with or without the hyperv display attached the screen will fail to capture with parsec with some D3D11 error and the gpu showing as a render device in dxdiag but when one plugs in a cable in a port known to be directly connected to the dedicated gpu (e.g. not usb c/thunderbolt to display output) all of a sudden parsec will work.

Here is a screenshot of it in action on the lenovo legion 5 pro laptop.

[svx3]

Any luck figuring this out? I'm a Legion 5 pro user with an Nvidia chip as well