internal/graphicsdriver: use DirectX on Windows

[hajimehoshi]

• Remote desktop doesn't work with OpenGL (on Windows 10 remote desktop not work. #903)
• Windows on ARM doesn't work with OpenGL 2 (https://docs.microsoft.com/en-us/windows/uwp/porting/apps-on-arm-troubleshooting-x86)
  • https://arstechnica.com/gadgets/2018/02/windows-10-on-arm-limits-briefly-confirmed-no-virtualization-no-opengl/
• A mysterious bug with OpenGL might be solved by DirectX (graphics: Strange rendering with Radeon RX 580 #993)
• OpenGL doesn't work on a virtual machine (Test on Windows Server #742)
• G-sync issue (I'm not sure DirectX solves this) (Low FPS in windowed mode when G-Sync is enabled #1467)
• Xbox doesn't support OpenGL (probably)

[beoran]

That's exactly what we do for Allegro as well. There's a lot of code in Allegro 5 that can be used as an example of hop to use Directx 9 (not 12, sorry) on Windows, which you could use as an inspiration.

[hajimehoshi]

Thanks. BTW, I'll adopt Direct X 10, which is the oldest Direct X we don't have to care about device-lost.

[beoran]

That might be a great idea, since DeviceLost extremely annoying, and Allegro5 needed a lot of handling for that as well. And I guess most people can user DirecxtX 10 now. 👍

[hajimehoshi]

As #993 was fixed (probably), I de-prioritize this work.

[hajimehoshi]

https://docs.microsoft.com/en-us/windows/uwp/gaming/porting-your-directx-9-game-to-windows-store DirectX 11 seems better for UWP rather than DirectX 10.

[hajimehoshi]

If Ebiten games are UWP, Ebiten games will work on Xbox. DirectX is necessary for this.

I tend to think I'll go with DirectX 12 rather than 11. Windows 10 should preinstall DirectX 12. I'm not sure about 11. As a fallback, OpenGL implementation will remain.