Hello Scream,
1. The multi-GPU fix is for Windows 10 v1903 with latest updates.
If you say it's obvious you're still on the iGPU and not on dGPU despite selecting the dGPU, I believe you are not running Windows 10 v1903. If you were running outdated Windows 10 v1903, the application would crash at startup if selecting the dGPU.
Would you please be able to check?
2. Yes, most likely. We have been able to find a way to reconfigure unused ASIC resource to workaround the monitor issue. It was very complex not to destabilise compliant displays. We have a Predator XB1 we tested this on, successfully.
Initially planned for 9.3 M0, I am not satisfied about the wait it would mean. Therefore I am trying to get an 9.2 M2+ development build (= not a formal release, but based on 9.2 M2 + that fix only as a preview) that I could share privately. I will use the ticket you created for that.
Kind regards,
Alban
Ref 30667 + UV16795
|