Checking out old drivers to see if thing is the same as with AMD drivers: old ones are working with the newest version of dgVoodoo. I'll make such a build soon, we'll see, but it's just a guess of mine about this being the "problem". I realized that I could "simplify" a certain thing (resource usage) in the DX11 implementation since I ditched the HLSL compiler and precompiled shaders, so maybe it won't confuse even a dumb driver. If not, then it's something on the driver side (as the WARP renderer works). Checking out if the DX11 debug layer is complaining about something when running those demos at FL10.0 and FL10.1. You may want to check out if older (pre-2.55.x) versions of dgVoodoo works. Btw, Intel HD 2000/4000 were mostly tested with Glide because the DX part of dgVoodoo did not exist at the time. So, that's why I'm not a big fan of having the newest drivers for old GPU's. Later I experienced broken things with newer drivers even with my NV GF 450 GTS. I emphasize "contemporary" because newer drivers interestingly removed FL 10.1 support. I started developing dgVoodoo on a HD 2000 with feature level 10.1 (2012) and things worked with a contemporary driver. Yes, I mentioned Intel HD 20 amongst the tested GPU's. It's Gen9 and this is the oldest Intel I have these days. DX11 FL 10.0 is still supported in dgVoodoo, I just ran 3DMark2000/2001 through that on my Intel HD Graphics 505. TBH, dgVoodoo should work on those chipsets. Haswell and Broadwell users must use newest drivers since they are WDDM 2.x, Ivy Bridge users are out of luck if they are stuck with IGP or Switchable graphics laptops.Thanks for this extensive, well-illustrated report! Since Microsoft anounced Windows 11 and stated an WDDM 2.0 cappable GPU is requeried, it pretty much leaves many old GPUs out of support.Ĭurrently Intel Generation 7.5 (Haswell) and newer GPUs are supported, anything earlier is left out of support.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |