DX11 feature level 10.0 is required to run the engine error when starting a game

[brunck]

Every time I try to start a game on the VM I get this error dialog.

• I've already updated the NVIDIA Tesla M60 driver
• I made sure that the Microsoft Hyper-V Video display adapter is enabled.

Here is the relevant display information from dxdiag:

------------------
System Information
------------------
      Time of this report: 6/15/2018, 21:07:13
             Machine name: CloudGaming
               Machine Id: {C8DE2750-4210-4448-9D7B-6345C6C25CC4}
         Operating System: Windows Server 2016 Datacenter 64-bit (10.0, Build 14393) (14393.rs1_release_1.180402-1758)
                 Language: English (Regional Setting: English)
      System Manufacturer: Microsoft Corporation
             System Model: Virtual Machine
                     BIOS: Intel(R) Xeon(R) CPU E5-2690 v3 @ 2.60GHz
                Processor: Intel(R) Xeon(R) CPU E5-2690 v3 @ 2.60GHz (6 CPUs), ~2.6GHz
                   Memory: 57344MB RAM
      Available OS Memory: 57344MB RAM
                Page File: 1959MB used, 63575MB available
              Windows Dir: C:\Windows
          DirectX Version: DirectX 12
      DX Setup Parameters: Not found
         User DPI Setting: Using System DPI
       System DPI Setting: 96 DPI (100 percent)
          DWM DPI Scaling: Disabled
                 Miracast: Not Available
Microsoft Graphics Hybrid: Not Supported
           DxDiag Version: 10.00.14393.0000 64bit Unicode

------------
DxDiag Notes
------------
      Display Tab 1: No problems found.
        Sound Tab 1: No problems found.
          Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D:    0/4 (retail)
DirectDraw:  0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay:  0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow:  0/6 (retail)

---------------
Display Devices
---------------
          Card name: Unknown
       Manufacturer: Unknown
          Chip type: Unknown
           DAC type: Unknown
        Device Type: n/a
         Device Key: Unknown
      Device Status: Unknown
Device Problem Code: Unknown
Driver Problem Code: Unknown
     Display Memory: Unknown
   Dedicated Memory: n/a
      Shared Memory: n/a
       Current Mode: 1920 x 1080 (32 bit) (32Hz)
        Driver Name: Unknown
Driver File Version: Unknown (Unknown)
     Driver Version: Unknown
        DDI Version: 9Ex
     Feature Levels: Unknown
       Driver Model: Unknown
Graphics Preemption: Unknown
 Compute Preemption: Unknown
           Miracast: Unknown
Hybrid Graphics GPU: Unknown
     Power P-states: Unknown
  Driver Attributes: Final Retail
   Driver Date/Size: 6/15/2018 20:37:35 12:00:00 AM, 0 bytes
        WHQL Logo'd: n/a
    WHQL Date Stamp: n/a
  Device Identifier: {D7B71AF4-43CC-11CF-F061-3918AFC2C735}
          Vendor ID: Unknown
          Device ID: Unknown
          SubSys ID: Unknown
        Revision ID: Unknown
 Driver Strong Name: Unknown
     Rank Of Driver: Unknown
        Video Accel: Unknown
        DXVA2 Modes: Unknown
      Deinterlace Caps: n/a
       D3D9 Overlay: Not Supported
            DXVA-HD: Not Supported
       DDraw Status: Not Available
         D3D Status: Enabled
         AGP Status: Not Available
           MPO Caps: Unknown
        MPO Stretch: Unknown
    MPO Media Hints: Unknown
        MPO Formats: Unknown

[brunck]

I was able to fix this problem. The NVIDIA M60 was not connected to the Generic PnP monitor by default.

I had to first disable the Microsoft Hyper-V Video Display adapter. Then I had to run the NVIDIA utility to set that adapter to be in WDDM mode, it was in the default mode of TCC which is for headless configurations, and it disables Windows graphics. Info on this page.

I did this by following the steps given in the answer from "tweakalicious".

[ecalder6]

Nice find! Whenever I can't launch a game, I just reinstall the Nvidia driver and that seems to fix things for me. I'll take a look into this and see if I can add this in the script.

BTW, Hyper-V should be disabled by the setup script

[andrewmd5]

I can confirm it didn't disable once for me. Also I had to run "nvidia-smi"

[brunck]

@ecalder6 yeah I think it did disable the Hyper-V display adapter when I first ran the script, then I enabled it myself as part of my troubleshooting efforts. So I had to make sure I re-disabled it, and that resulted in me mentioning it in my comment.

[ecalder6]

Finally got a chance to fix it: https://github.com/ecalder6/azure-gaming/pull/18 Thanks for the tip!