VOGONS


First post, by unmei220

User metadata
Rank Member
Rank
Member

First of all, I'm just assuming that these chipsets should work based on the following part of the dgVoodoo documentation:

Details

I've tested and run different versions of dgVoodoo2 on the following GPU's:

  • Intel HD 2000 (feature level 10.0 only)
  • GeForce 8600 GT (feature level 10.0 only)
  • Intel HD 4000
  • Geforce GT 610
  • AMD HD 6450
  • Intel HD Graphics 530
  • GeForce GTS 450
  • AMD HD 7850
  • GeForce GTX Ti560 (RIP)
  • AMD R7 360
  • GeForce GTX 1060

If this is no longer the case, just let me know, as then this whole post would be irrelevant.

I was just trying to run an old 2D game through dgVoodoo on the HD3000 (said game was known to work on another PC with an nVidia card), and it turns out the game simply did nothing, it just went back to the desktop, no error message nor anything. Switched the output API to MS WARP and then it worked, although painfully slow...
Curious, I installed 3DMark99, 2000 and 2001SE; only to discover that none of them launched, giving these errors:

3DMark_errors.png
Filename
3DMark_errors.png
File size
58.48 KiB
Views
962 views
File license
Public domain

The benchmarks run fine with dgVoodoo disabled, I just used them for reference since they're supposed to work OK with dgVoodoo, according to "DirectX demo gallery and my test results". This is on Win7 x86, using latest Intel HD 3000 drivers and dgVoodoo latest version, 2.77.
------------------------------
Then I switched to another PC with an Intel HD 4000 iGPU, and tried the same benchmarks, with these results:

3DMark99.gif
Filename
3DMark99.gif
File size
1.34 MiB
Views
962 views
File license
Public domain

DX6.1 seems to work OK, no problems or anything, but when I moved to DX7 or higher...

3DMark2000.gif
Filename
3DMark2000.gif
File size
1.44 MiB
Views
962 views
File license
Public domain
3DMark2001SE.gif
Filename
3DMark2001SE.gif
File size
1.36 MiB
Views
962 views
File license
Public domain

This is on Win8.1 x64, using latest Intel HD 4000 drivers and dgVoodoo latest version, 2.77.
------------------------------
Next generation of Intel graphics (Gen8), the same thing as Gen7 happens: DX6.1 works, DX7 is glitchy, and for some reason 3DMark2001SE refused to launch: it just hangs. This was on another Laptop with a Pentium N3710 (Braswell), using Intel HD Graphics with latest drivers installed on Win7 x64. Also using latest dgVoodoo version, 2.77.

Is this the expected behavior with these old chipsets?

ADDENUM: 3DMark03 (DX9) seemed to work OK on Gen8, except for the benchmark loading screens prior to each test, which just displayed as white. Gen6 just errored like usual, with a "Direct3D initialization failed" message. Didn't had time to test on Gen7...

Last edited by unmei220 on 2021-12-13, 21:00. Edited 2 times in total.

Reply 1 of 22, by Dege

User metadata
Rank l33t
Rank
l33t

Thanks for this extensive, well-illustrated report!

TBH, dgVoodoo should work on those chipsets. DX11 FL 10.0 is still supported in dgVoodoo, I just ran 3DMark2000/2001 through that on my Intel HD Graphics 505. It's Gen9 and this is the oldest Intel I have these days. They worked perfectly (Win10).

Yes, I mentioned Intel HD 2000 and 4000 amongst the tested GPU's. I started developing dgVoodoo on a HD 2000 with feature level 10.1 (2012) and things worked with a contemporary driver. I emphasize "contemporary" because newer drivers interestingly removed FL 10.1 support. Later I experienced broken things with newer drivers even with my NV GF 450 GTS. So, that's why I'm not a big fan of having the newest drivers for old GPU's. Btw, Intel HD 2000/4000 were mostly tested with Glide because the DX part of dgVoodoo did not exist at the time.
You may want to check out if older (pre-2.55.x) versions of dgVoodoo works.

So, what I can do on dgVoodoo side are:
- Checking out if the DX11 debug layer is complaining about something when running those demos at FL10.0 and FL10.1. If not, then it's something on the driver side (as the WARP renderer works).
- 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. I'll make such a build soon, we'll see, but it's just a guess of mine about this being the "problem".

Driver side:
- 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.

When the demo doesn't even start and fails with an error message, that means that dgVoodoo cannot even initialize DX11 with the needed objects (you can have a look at dgVoodoo debug logs, but the interesting one would be the DX11 SDK layers). We had a really old AMD chipset (can't remember exactly what) having this problem: it couldn't create a certain DX11 buffer with arbitrary size so dgVoodoo failed. Unfortunately we couldn't figure it out what size it liked so the issue remained unsolved.

Reply 2 of 22, by unmei220

User metadata
Rank Member
Rank
Member

You may want to check out if older (pre-2.55.x) versions of dgVoodoo works.

This was the key. I started with dgVoodoo v2.54, and suddenly everything worked perfectly on Gen7 and Gen8. The reason I didn't test v2.54 on these chips before was that I tested it on the HD 3000 (Gen6) first, and since it gave me the same results as newer versions (can't initialize D3D errors and so on, as mentioned before), I just thought it would be the same with the newer chipsets...
I started moving up from there and found out that the version that "breaks" compatibility with these older iGPUs (at least on Win7 & 8.1 x64) is dgVoodoo v2.76 (ATI TruForm support, specialized vs FF shaders, bugfixes).
Until dgVoodoo v2.75.1, everything worked perfectly.

Driver side:
- 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.

At least with Gen7 & Gen8, regardless of driver version (I tested some really OLD drivers with them), everything works using dgVoodoo v2.75.1, and suddenly breaks starting with dgVoodoo v2.76.

When the demo doesn't even start and fails with an error message, that means that dgVoodoo cannot even initialize DX11 with the needed objects (you can have a look at dgVoodoo debug logs, but the interesting one would be the DX11 SDK layers). We had a really old AMD chipset (can't remember exactly what) having this problem: it couldn't create a certain DX11 buffer with arbitrary size so dgVoodoo failed. Unfortunately we couldn't figure it out what size it liked so the issue remained unsolved.

I'll test the HD 3000 next with some really old drivers, but as I said earlier, at least using v2.54, behavior and errors are exactly the same as with newer versions of dgVoodoo... so probably there's no solution with that one.

Reply 4 of 22, by unmei220

User metadata
Rank Member
Rank
Member
Dege wrote on 2021-12-13, 20:09:

Oh, then it must be the new shader code generator...

What happens if you disable the DirectXExt\EnableSpecializedShaders for 2.76+? (compatibility option)

That did the trick!

God I feel dumb... I should investigate properly next time before posting walls of text...
So, there's no issues neither with Gen7 nor Gen8, while Gen6 refuses to work (old driver test still pending).

Reply 5 of 22, by Dege

User metadata
Rank l33t
Rank
l33t

No, it's not dumbness at all. We now know that the introduced shader generator is not compatible with those old chipsets. It's a pity because I was about to remove that config option. I only introduced it for "emergency cases" like this.
Either I figure it out what those driver don't like or I automatize the choice between the shaders, I don't yet know what to do.

Reply 6 of 22, by unmei220

User metadata
Rank Member
Rank
Member
Dege wrote on 2021-12-12, 16:22:

Driver side:
- 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.

This did the trick for the Intel HD 3000, partially.

After installing an older driver available from Intel's site for it, dated from 2012 (newest is from 2015) and designed for Windows 7 and Windows Vista (newest includes 8 & 8.1 support and discards Vista), dgVoodoo started working!
I had to uncheck "Enable specialized shaders" though, otherwise everything was glitchy, as with Gen7 & Gen8).
It even worked with the game I had problems to begin with, and also worked with all the 3DMark's, except for 99, which didn't launch even without dgVoodoo (always the same "DirectX not installed" message).

Unfortunately, this older driver also introduced errors on some of the titles (old DX5/6 games) I had working perfectly on that PC before the driver downgrade, so in the end I just ended up reverting to the newest driver: its the one that gives the least problems, at least for me...

Reply 7 of 22, by Dege

User metadata
Rank l33t
Rank
l33t

Could you plz test WIP85 with HD 4000? (with DirectXExt\EnableSpecializedShaders set to true)

I looked at the shaders used in the 3DMark 2k helicopter test, and I had a strong guess what the driver didn't like.
I made changes to the code generator, it might help:

Re: dgVodooo 2.7.x and related WIP versions (2)

Reply 8 of 22, by unmei220

User metadata
Rank Member
Rank
Member
Dege wrote on 2022-02-20, 18:56:
Could you plz test WIP85 with HD 4000? (with DirectXExt\EnableSpecializedShaders set to true) […]
Show full quote

Could you plz test WIP85 with HD 4000? (with DirectXExt\EnableSpecializedShaders set to true)

I looked at the shaders used in the 3DMark 2k helicopter test, and I had a strong guess what the driver didn't like.
I made changes to the code generator, it might help:

Re: dgVodooo 2.7.x and related WIP versions (2)

Both 3DMark2000 and 3DMark2001 SE worked without problems, no more glitches of any kind.
BIKŌ also started working smoothly. It takes like a few seconds of pause when switching, but no longer crashes when the resolution changes!

Want me to test anything else on HD3000 (Gen6, with the older drivers that work with DgVoodoo) and/or Gen8?

Reply 9 of 22, by Dege

User metadata
Rank l33t
Rank
l33t

Ok, thanks for the good news!
Then I can remove that option for specialized shaders in a later version.

Gen8: I think if dgv works with older gen then it should do that with Gen8 too.

HD3000:
If you feel like trying to discover the reason of failing dgV init with the new drivers, then you could install the D3D11 debug layer and see the D3D11 debug output, like in this thread:

Re: A newbie problem

(but I don't expect doing it, it's up to you)

Thanks again!

Reply 10 of 22, by unmei220

User metadata
Rank Member
Rank
Member
Dege wrote on 2022-02-21, 19:08:
Ok, thanks for the good news! Then I can remove that option for specialized shaders in a later version. […]
Show full quote

Ok, thanks for the good news!
Then I can remove that option for specialized shaders in a later version.

Gen8: I think if dgv works with older gen then it should do that with Gen8 too.

HD3000:
If you feel like trying to discover the reason of failing dgV init with the new drivers, then you could install the D3D11 debug layer and see the D3D11 debug output, like in this thread:

Re: A newbie problem

(but I don't expect doing it, it's up to you)

Thanks again!

Sounded like fun, so I went ahead with it.
Apparently, I'm getting the same compute shaders error that Bill_Boquet reported on their X3100 in the thread you mentioned? Check #18.
It's something that can't be solved, right? Funny that the older drivers supported it then...

[dgVoodoo] INFO: Reading config from file C:\Program Files\MadOnion.com\3DMark2000\dgVoodoo.conf.
[dgVoodoo] INFO: INI file based version of config file is successfully read.
[dgVoodoo] INFO: DDraw is successfully loaded: C:\Program Files\MadOnion.com\3DMark2000\DDRAW.dll
[dgVoodoo] INFO: Reading config from file C:\Program Files\MadOnion.com\3DMark2000\dgVoodoo.conf.
[dgVoodoo] INFO: INI file based version of config file is successfully read.
DXGI ERROR: IDXGIOutput::FindClosestMatchingMode: DXGI_FORMAT_UNKNOWN cannot be used width display modes in this configuration. [ MISCELLANEOUS ERROR #72: ]
[dgVoodoo] INFO: Available DirectDraw devices:
[dgVoodoo] INFO: Device 0: Name: "Intel(R) HD Graphics 3000", Description: "\\.\DISPLAY1", Monitor rect: (0, 0, 1366, 768), GUID = {67685559-3106-11d0-b971-00aa00342f9f}, system primary monitor
[dgVoodoo] INFO: DirectDrawEnumerateA: This function enumerates only the primary device with NULL GUID.
D3D11 INFO: Create ID3D11Context: Name="unnamed", Addr=0x01C1CF68, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097225: CREATE_CONTEXT]
D3D11 INFO: Create ID3DDeviceContextState: Name="unnamed", Addr=0x01C26FD0, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #3145735: CREATE_DEVICECONTEXTSTATE]
D3D11 INFO: Create ID3D11BlendState: Name="unnamed", Addr=0x01C05A9C, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097270: CREATE_BLENDSTATE]
D3D11 INFO: Create ID3D11DepthStencilState: Name="unnamed", Addr=0x01C2CEDC, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097273: CREATE_DEPTHSTENCILSTATE]
D3D11 INFO: Create ID3D11RasterizerState: Name="unnamed", Addr=0x01C2D014, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097276: CREATE_RASTERIZERSTATE]
D3D11 INFO: Create ID3D11Sampler: Name="unnamed", Addr=0x01C2D214, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097267: CREATE_SAMPLER]
D3D11 INFO: Create ID3D11Query: Name="unnamed", Addr=0x01C2D34C, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097279: CREATE_QUERY]
D3D11 INFO: Create ID3D11Buffer: Name="unnamed", Addr=0x01C2D8AC, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097228: CREATE_BUFFER]
D3D11 ERROR: ID3D11Device::CreateComputeShader: CreateComputeShader can only be called on devices either (a) with feature level greater or equal to D3D_FEATURE_LEVEL_11_0, or (b) with D3D_FEATURE_LEVEL_10_* for hardware that reports support for the Compute Shader. The current device is not one of these. Use the CheckFeatureSupport() API with D3D11_FEATURE_D3D10_X_HARDWARE_OPTIONS to discover support for Compute Shaders on D3D_FEATURE_LEVEL_10_*. [ STATE_CREATION ERROR #68: CREATEBUFFER_INVALIDMISCFLAGS]
D3D11 INFO: Destroy ID3D11Buffer: Name="unnamed", Addr=0x01C2D8AC [ STATE_CREATION INFO #2097230: DESTROY_BUFFER]
D3D11 INFO: Destroy ID3D11Query: Name="unnamed", Addr=0x01C2D34C [ STATE_CREATION INFO #2097281: DESTROY_QUERY]
D3D11 INFO: Destroy ID3D11RasterizerState: Name="unnamed", Addr=0x01C2D014 [ STATE_CREATION INFO #2097278: DESTROY_RASTERIZERSTATE]
D3D11 INFO: Destroy ID3D11DepthStencilState: Name="unnamed", Addr=0x01C2CEDC [ STATE_CREATION INFO #2097275: DESTROY_DEPTHSTENCILSTATE]
D3D11 INFO: Destroy ID3D11BlendState: Name="unnamed", Addr=0x01C05A9C [ STATE_CREATION INFO #2097272: DESTROY_BLENDSTATE]
D3D11 INFO: Destroy ID3D11Sampler: Name="unnamed", Addr=0x01C2D214 [ STATE_CREATION INFO #2097269: DESTROY_SAMPLER]
D3D11 INFO: Destroy ID3D11Context: Name="unnamed", Addr=0x01C1CF68 [ STATE_CREATION INFO #2097227: DESTROY_CONTEXT]
D3D11 INFO: Destroy ID3DDeviceContextState: Name="unnamed", Addr=0x01C26FD0 [ STATE_CREATION INFO #3145749: DESTROY_DEVICECONTEXTSTATE]
[dgVoodoo] ERROR: DDBase (002B08F8): Cannot initialize the DDI object.
[dgVoodoo] ERROR: DirectDraw (01C07118) Initialization failed: Cannot init device DDI.
[dgVoodoo] ERROR: DirectDrawCreate/DirectDrawCreateEx: creating DirectDraw object has failed.

Reply 11 of 22, by Dege

User metadata
Rank l33t
Rank
l33t

Thanks!!

I forgot about the compute shader thing, but I've just released a new WIP that should address the problem.
Compute shader support is no longer required, in the worst case c64-output falls back to simple 'stretched, keep AR' scaling mode:

Re: dgVodooo 2.7.x and related WIP versions (2)

Reply 12 of 22, by unmei220

User metadata
Rank Member
Rank
Member
Dege wrote on 2022-02-22, 17:47:
Thanks!! […]
Show full quote

Thanks!!

I forgot about the compute shader thing, but I've just released a new WIP that should address the problem.
Compute shader support is no longer required, in the worst case c64-output falls back to simple 'stretched, keep AR' scaling mode:

Re: dgVodooo 2.7.x and related WIP versions (2)

Unfortunately, I had no luck with WIP85.1, 3DMark2000 still crashes on launch, claiming no DX7. The output log is longer this time.
Maybe there's a hint in entry #60?
I tried changing Output API to D3D11 FL10.0, but still the same.

Spoiler
[dgVoodoo] INFO: Reading config from file C:\Program Files\MadOnion.com\3DMark2000\dgVoodoo.conf.
[dgVoodoo] INFO: INI file based version of config file is successfully read.
[dgVoodoo] INFO: DDraw is successfully loaded: C:\Program Files\MadOnion.com\3DMark2000\DDRAW.dll
[dgVoodoo] INFO: Reading config from file C:\Program Files\MadOnion.com\3DMark2000\dgVoodoo.conf.
[dgVoodoo] INFO: INI file based version of config file is successfully read.
DXGI ERROR: IDXGIOutput::FindClosestMatchingMode: DXGI_FORMAT_UNKNOWN cannot be used width display modes in this configuration. [ MISCELLANEOUS ERROR #72: ]
[dgVoodoo] INFO: Available DirectDraw devices:
[dgVoodoo] INFO: Device 0: Name: "Intel(R) HD Graphics 3000", Description: "\\.\DISPLAY1", Monitor rect: (0, 0, 1366, 768), GUID = {67685559-3106-11d0-b971-00aa00342f9f}, system primary monitor
[dgVoodoo] INFO: DirectDrawEnumerateA: This function enumerates only the primary device with NULL GUID.
D3D11 INFO: Create ID3D11Context: Name="unnamed", Addr=0x018BE1D0, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097225: CREATE_CONTEXT]
D3D11 INFO: Create ID3DDeviceContextState: Name="unnamed", Addr=0x018C8238, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #3145735: CREATE_DEVICECONTEXTSTATE]
D3D11 INFO: Create ID3D11BlendState: Name="unnamed", Addr=0x018A6094, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097270: CREATE_BLENDSTATE]
D3D11 INFO: Create ID3D11DepthStencilState: Name="unnamed", Addr=0x018A4FEC, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097273: CREATE_DEPTHSTENCILSTATE]
D3D11 INFO: Create ID3D11RasterizerState: Name="unnamed", Addr=0x018CE144, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097276: CREATE_RASTERIZERSTATE]
D3D11 INFO: Create ID3D11Sampler: Name="unnamed", Addr=0x018CE27C, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097267: CREATE_SAMPLER]
D3D11 INFO: Create ID3D11Query: Name="unnamed", Addr=0x018CE3B4, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097279: CREATE_QUERY]
D3D11 INFO: Create ID3D11Buffer: Name="unnamed", Addr=0x018CE514, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097228: CREATE_BUFFER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018CE9F4, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018CEDDC, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018CF03C, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018CF664, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D1CA4, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018CF29C, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D01BC, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D13E4, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D1644, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D18A4, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018CFBF4, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018CF8C4, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D06DC, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018CFE54, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D093C, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D0B9C, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D29EC, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D2C54, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D2EBC, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D3124, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D338C, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D35F4, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D385C, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D3AC4, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D3D2C, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D3F94, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D41FC, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D4464, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D46CC, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D4934, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D4B9C, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D4E04, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D506C, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D52D4, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D553C, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D57A4, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D5A0C, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D5C74, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D5EDC, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D6144, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D63AC, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 INFO: Create ID3D11PixelShader: Name="unnamed", Addr=0x018D6614, ExtRef=1, IntRef=0 [ STATE_CREATION INFO #2097261: CREATE_PIXELSHADER]
D3D11 ERROR: ID3D11Device::CreatePixelShader: Shader uses features (Raw or Structured Buffers) not supported by this device. Use the CheckFeatureSupport() API with D3D11_FEATURE_D3D10_X_HARDWARE_OPTIONS to discover support for these features if using D3D_FEATURE_LEVEL_10_*. [ STATE_CREATION ERROR #192: CREATEPIXELSHADER_INVALIDSHADERBYTECODE]
Show last 54 lines
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018CE9F4 [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018CEDDC [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018CF03C [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018CF664 [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D1CA4 [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018CF29C [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D01BC [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D13E4 [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D1644 [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D18A4 [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018CFBF4 [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018CF8C4 [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D06DC [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018CFE54 [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D093C [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D0B9C [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D29EC [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D2C54 [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D2EBC [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D3124 [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D338C [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D35F4 [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D385C [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D3AC4 [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D3D2C [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D3F94 [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D41FC [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D4464 [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D46CC [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D4934 [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D4B9C [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D4E04 [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D506C [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D52D4 [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D553C [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D57A4 [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D5A0C [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D5C74 [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D5EDC [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D6144 [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D63AC [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11PixelShader: Name="unnamed", Addr=0x018D6614 [ STATE_CREATION INFO #2097263: DESTROY_PIXELSHADER]
D3D11 INFO: Destroy ID3D11Buffer: Name="unnamed", Addr=0x018CE514 [ STATE_CREATION INFO #2097230: DESTROY_BUFFER]
D3D11 INFO: Destroy ID3D11Query: Name="unnamed", Addr=0x018CE3B4 [ STATE_CREATION INFO #2097281: DESTROY_QUERY]
D3D11 INFO: Destroy ID3D11RasterizerState: Name="unnamed", Addr=0x018CE144 [ STATE_CREATION INFO #2097278: DESTROY_RASTERIZERSTATE]
D3D11 INFO: Destroy ID3D11DepthStencilState: Name="unnamed", Addr=0x018A4FEC [ STATE_CREATION INFO #2097275: DESTROY_DEPTHSTENCILSTATE]
D3D11 INFO: Destroy ID3D11BlendState: Name="unnamed", Addr=0x018A6094 [ STATE_CREATION INFO #2097272: DESTROY_BLENDSTATE]
D3D11 INFO: Destroy ID3D11Sampler: Name="unnamed", Addr=0x018CE27C [ STATE_CREATION INFO #2097269: DESTROY_SAMPLER]
D3D11 INFO: Destroy ID3D11Context: Name="unnamed", Addr=0x018BE1D0 [ STATE_CREATION INFO #2097227: DESTROY_CONTEXT]
D3D11 INFO: Destroy ID3DDeviceContextState: Name="unnamed", Addr=0x018C8238 [ STATE_CREATION INFO #3145749: DESTROY_DEVICECONTEXTSTATE]
[dgVoodoo] ERROR: DDBase (018A8FB8): Cannot initialize the DDI object.
[dgVoodoo] ERROR: DirectDraw (018AA978) Initialization failed: Cannot init device DDI.
[dgVoodoo] ERROR: DirectDrawCreate/DirectDrawCreateEx: creating DirectDraw object has failed.
Last edited by unmei220 on 2022-02-22, 18:59. Edited 1 time in total.

Reply 13 of 22, by Dege

User metadata
Rank l33t
Rank
l33t

Oh, yeah, its' entry #60. Then, there are no more options... 🙁
Structured buffers are essential in Glide and some of my DX shaders so I cannot remove them.
Those Intel drivers are strange because I started coding dgVoodoo2 on an Intel HD2000 and structureds buffers were supported (along with FL10.1) back then. Why did they remove the support for them in later drivers? 🤔

Reply 14 of 22, by unmei220

User metadata
Rank Member
Rank
Member

No idea...
As I said before, the older drivers designed for Vista and Win7 (win7vista_152254.exe/win7vista_64_152254.exe), 15.22.54.2622, dated 1/21/2012, work perfectly fine with DgVoodoo (but has errors in other areas).
Meanwhile, the newer ones designed for Win7, 8 & 8.1 (win32_152824.exe/win64_152824.exe), 15.28.24.4229, dated 6/5/2015... well, you know the rest.🙁 But they're much more robust and compatible than the older ones, specially with old games!
Thank you very much for your efforts! 😀

Reply 15 of 22, by Bill_Boquet

User metadata
Rank Newbie
Rank
Newbie

Thanks to both for this very interesting and informative thread.
As indicated by unmei220, I faced a similar issue on an (very) old Intel X3100 :
A newbie problem
I also experimented the different strategies proposed by Dege, with no luck.
Using the latest WIP offered by Dege, I got a similar log file than unmei220, with the exact same error message : logical as the X3100 is probably same gen 6 than HD3000.
I didn't test with older drivers, as anyhow my investigation was mainly for fun and to further improve the knowledge.
Thanks very much to both for your time and dedication ! 😉

Reply 16 of 22, by Dege

User metadata
Rank l33t
Rank
l33t

Thanks for both of you! At least we know the drill about those old Intel GPU's. 😀
The fact that dgVoodoo does not work with them is maybe not a big practical problem. Their performance wouldn't be satisfactory after all.
Feature level 10.0 was already an afterthought and was introduced for the sake of GF 200 series.

Reply 17 of 22, by yochenhsieh

User metadata
Rank Newbie
Rank
Newbie
Bill_Boquet wrote on 2022-02-23, 09:19:
Thanks to both for this very interesting and informative thread. As indicated by unmei220, I faced a similar issue on an (very) […]
Show full quote

Thanks to both for this very interesting and informative thread.
As indicated by unmei220, I faced a similar issue on an (very) old Intel X3100 :
A newbie problem
I also experimented the different strategies proposed by Dege, with no luck.
Using the latest WIP offered by Dege, I got a similar log file than unmei220, with the exact same error message : logical as the X3100 is probably same gen 6 than HD3000.
I didn't test with older drivers, as anyhow my investigation was mainly for fun and to further improve the knowledge.
Thanks very much to both for your time and dedication ! 😉

Actually, X3100 is older than HD3000:
HD3000 - Gen 6, supports Direct X 10.1
X3100 - Gen 4, supports Direct X 10.0

Reply 18 of 22, by Bill_Boquet

User metadata
Rank Newbie
Rank
Newbie

Thanks @yochenhsieh, I didn't check before, but X3100 is indeed a very old lady from 2007 😉
https://en.wikipedia.org/wiki/List_of_Intel_g … rocessing_units

P.S. In the meantime, I tested with older drivers and no miracle happened 😉

Reply 19 of 22, by esasoft

User metadata
Rank Newbie
Rank
Newbie

Unfortunately, no version, including the newest one, works with the Intel HD3000.
dgVoodoo2 is currently not compatible with this video adapter. At all.
No game or program using DirectX 9 or below will start with it. Either nothing happens, or the program crashes with an error.
It does not depend on the version or bitness of the OS. Installing different versions of the drivers does not change the situation. It also does not depend on the settings of the program itself, including advanced ones.
I've been struggling with this problem for several months now.
This is definitely a bug. It needs to be eliminated.