WinUAE 3.1.0, Win10, RTG and DirectX grayed out

[PeterK]

Hi Toni,

I've installed WinUAE 3.1.0 on my Mini-PC (Intel j2900 with Intel HD Graphics DX 11.2) together with DirectXJun2010Redist.

It works so far, but all the WinUAE GUI fields for RTG settings and for Direct3D or DirectDraw are grayed out. What's missing or wrong?

[Toni Wilen]

The usual, install DX9 redistributable. (No, Windows has never come with full DX, not even 7, 8, 8.1 or even 10. It is stupid.)

[PeterK]

Yes, that's what I did: first installed DX9 Nov2007 Redist and then Jun2010 Redist. There is no requester from WinUAE anymore asking for the DX9 files.

Update:

42-161 [0 000=000]: Direct3D: Pixel shader 2.0+ support detected, shader filters enabled.
42-168 [0 000=000]: Device name: 'Intel(R) HD Graphics' a0012000a109c.e
42-484 [0 000=000]: D3D9Ex: 00000056 ALPHA DYNAMIC SCANLINE
42-484 [0 000=000]: D3D9Ex: PS=3.0 VS=3.0 800*600*0p FS VS=0 B=2WE 32-bit 0
42-562 [0 000=000]: D3D9Ex: pixelshader filter 'M:\WinUAE\_winuae.fx':-1 enabled
42-567 [0 000=000]: D3D9Ex: 752*576 main texture, depth 32

I don't have this filter installed: _winuae.fx

How do I have to install Filtershaders.zip correctly ?? Where should plugins go to?

Update2:
OK, I've copied the plugins dir into the WinUAE install dir and WinUAE has generated the _winuae.fx file automatically now. But all the RTG and DirectX fields are still grayed out in the GUI.

Could this problem be caused by the missing VDD and Mini VDD display driver files?

[Toni Wilen]

All looks fine. You didn't include your config but make sure filter is at least null, not none.

[PeterK]

Even with the Null filters it's still the same as shown on the screenshots above. Btw, DSound is also grayed out.

[AMIGASYSTEM]

On Windows 10 You've tried to install everything DirectX etc.. and start WinUAE by privileged user administrator !

[Toni Wilen]

Originally Posted by AMIGASYSTEM

You've tried to install everything DirectX etc.. and start WinUAE by privileged user administrator !

Lets keep doing proper debugging and not doing random things until something expected or unexpected happens!

EDIT: Direct3D is obviously working by checking logs.

EDIT2: Actually testing with admin may be good idea if current user has really weird permissions... (normal privilege user still should work)

[Toni Wilen]

Originally Posted by PeterK

Even with the Null filters it's still the same as shown on the screenshots above. Btw, DSound is also grayed out.

What do you mean by DSound being grayed out?

Do you have C:\Windows\System32\D3DX9_43.dll ?

[PeterK]

I've just checked out the same WinUAE settings and config on the same PC with Windows 7. And the main difference compared to Windows 10 and XP is the way how the GUI elements (buttons, selectors) and their colors are displayed.

The problem in Windows 10 is the simplified color schema. The vertical color fades for the selectors like in Windows 7 are simply replaced by light gray backgrounds, but this doesn't mean that these fields are grayed out as I thought. Only the dark gray GUI elements are inactive.

Unfortunately, some GUI elements in WinUAE have just white backgrounds and others have these vertical color fades under Windows 7. What is the reason for their different appearance? Under XP all the active selectors are only white and comparing the XP GUI with Windows 10 has caused the confusion.

[Toni Wilen]

Could you attach screenshot comparison? I have Windows 10 with default settings and disabled elements are darker. (I don't even remember how it looked under 7..)

Anyway, WinUAE uses pure Windows GUI elements, no customizations.

[PeterK]

All 9 images from XP, W7 and W10 are in the 7z package. W10 is in post #3, W7 files are also attached here;