Topic on Glossary talk:DirectX
This page shows the changes between two versions of a post by Mirh in the topic "Known backwards compatibility holes" on Glossary talk:DirectX.
You can see other versions of this post at its history page.
| Line 1: | Line 1: | ||
| − | * D3D8 [https://github.com/ | + | * <D3D9 [[User talk:Garrett/Troubleshooting/Windows 8.1|has]] [[User talk:Garrett/Troubleshooting/Windows 10|been]] for a long time getting faker than fake exclusive fullscreen (with all it entails for v-sync, gdi, and gamme adjusements), and [https://www.vogons.org/viewtopic.php?f=8&t=47772&start=20#p732319 since] W10 1809 removed any possible native workaround |
| + | * D3D8 is [https://github.com/elishacloud/dxwrapper/issues/134#issuecomment-1239610767 supposedly] [https://www.vogons.org/viewtopic.php?t=89551#p1096203 getting] thunked to the equivalent d3d9 calls in W10 (which aren't always 1:1 equivalent) | ||
* D3D9 clip planes are [https://cookieplmonster.github.io/2018/07/07/farcry-d3d9-bug/ busted] (Vista+) | * D3D9 clip planes are [https://cookieplmonster.github.io/2018/07/07/farcry-d3d9-bug/ busted] (Vista+) | ||