Before when using version 16 3D acceleration was working no problem but after updating to version 17 it no longer works and gives me the following message:
My host is running Windows 10 22h2 and has a GTX 770 gpu.
I have tried the following but none helped:
mks.gl.allowBlacklistedDrivers = "TRUE"
mks.requireISBRenderer = "FALSE"
mks.enableISBRenderer = "FALSE"
Anything I can do to fix it?
I have attached my DxDiag output.
same here, have here a NVIDIA Quadro K4100M; latest driver is installed (R418 U9 (426.78) WHQL, Release Date: 2020.6.24 ). this graphics card support directx 11 (minimum requirement); directx function levels: 11_0, 10_1, 10_0, 9_3, 9_2 and 9_1 (dxdiag); so whats wrong; can we have a official statement from vmware please?
Please try this vmx option instead:
If possible, I would appreciate it if you attached "mksSandbox.log" for the VM session that reported no 3D support.
Both Quadro K4100M and GTX 770 do not support feature level 11_1 (they are only feature level 11_0) that is the minimum level required by WS 17.
During installation, you should see a warning message saying that 3D will not be supported on such systems.
sorry, no; i had get no warning; offical documentation has no info for minimum dx level required; it says only directx 11; any cause, why feature level 11_1 is needed?
I don't remember getting any such warning.
Any way to override it so one can run it using 11_0 at one own's risk? Or disable whatever feature that requires 11_1?
Newer versions of windows 11 doesn't work on vmware 16 so I sadly don't have the option to simply downgrade vmware.
In order to support OpenGL 4.3 in the VMs we had to start requiring DirectX feature level 11.1 on the host. I'm sorry but there is no vmx config option to override that requirement.
I would appreciate it if you attached vmware*.log and mksSandbox*.log files from a problematic session.
As a workaround, if GLRenderer worked for you, these are the vmx config options to enable GLRenderer in WS 17:
Can you double check that and send me the *.log files as you are getting different beahviour from your original post?
I have an i5-4310M with the same HD 4600 and with the below configuration the VM will not start:
But with the below configuration everything works:
I do 3 tests in a Windows Server 2022 VM:
Doesn't modify anything.