Direct3D auto-detect incorrectly finds DirectX 11 for DirectX 9/10 application

[justinstenning]

Can't remember the exact scenario now, but under some circumstances the DirectX 11 library will be loaded for a DirectX 9/10 application.

The current logic will incorrectly choose DirectX 11. Instead we could hook all loaded DirectX versions and then we will be correctly capturing which ever is actually presenting.