mjkrol's Posts

You need to upgrade to WS 17 and enable DX12Renderer. To enable DX12Renderer, please add the following lines to your VM's .vmx file. mks.enableDX11Renderer=FALSE mks.enableDX12Renderer=TRUE
 FabiMarshbb, I don't see any crash report in the attached log files. Can you reproduce the crash with WS 17.0.2 and attach vmware.log + mksSandbox.log?
Your NVIDIA GPU is lacking features that are required to enable 3D inside the guest, that's why Intel, being more capable, is being picked instead.
Can you try and change your VM's CPU configuration (VM --> Settings... -> Hardware --> Processors) from 4 processors/3 cores to 1 processor/1 core?
david58, You could try reinstalling the drivers for your GPU using a clean install option, if available. If that does not help, try disabling DX11Renderer and enabling DX12Renderer. On AMD hosts, t... See more...
david58, You could try reinstalling the drivers for your GPU using a clean install option, if available. If that does not help, try disabling DX11Renderer and enabling DX12Renderer. On AMD hosts, this requires setting three vmx config options: mks.enableDX11Renderer = FALSE mks.enableDX12Renderer = TRUE mks.dx12.allowUnsupportedDevices = TRUE If enabling DX12Renderer does not work, please attach new mksSandbox.log and vmware.log.
> If you require special keyboard settings for this to work please advise. The recording start/stop hotkey is independent from your Workstation preferences. You should still use (Ctrl) (Alt) (-) eve... See more...
> If you require special keyboard settings for this to work please advise. The recording start/stop hotkey is independent from your Workstation preferences. You should still use (Ctrl) (Alt) (-) even when the VMware hot key is (Ctrl) (Shift) (Alt). When you say the hotkey did not trigger recording, do you mean you could not find "mks-replay.gz" in the VM directory? Can you please do a system-wide search for the file?
BadOmen, Can you attach a vmware.log and mksSandbox.log?
I'm happy things are working for you. I can confirm that the problems you were seeing were fixed in WS 17, but the VMs have to be upgraded to HW version 20 for the fixes to kick in.
I'm trying to reproduce the crash with AutoCAD 2024 but no luck so far. Since I'm not familiar with AutoCAD, I'm probably doing something wrong. Can you provide baby-steps after AutoCAD is launched ... See more...
I'm trying to reproduce the crash with AutoCAD 2024 but no luck so far. Since I'm not familiar with AutoCAD, I'm probably doing something wrong. Can you provide baby-steps after AutoCAD is launched that reproduce the crash?
Open "C:\ProgramData\VMware\VMware Workstation\config.ini" in a text editor and add the following line. mks.enableDX12Renderer = "FALSE"
lurulf, What is your host operating system? Also, can you please collect support information (or get at least vmware.log + mksSandbox.log) and attach it?
Can you please try and upgrade to Workstation Player 17.0.1? It has a fix for systems with HD 4600 GPUs, so there are high chances upgrading will fix your problem.
> This is the SimCity version in the screenshot below. > The crash occurs when I press play on the screen in the screenshot below and the game starts to render 3D while it is running. Yes, this is ... See more...
> This is the SimCity version in the screenshot below. > The crash occurs when I press play on the screen in the screenshot below and the game starts to render 3D while it is running. Yes, this is the game I tried to reproduce the crash with. Since it did not crash for me with WS 17 and the dump file indicates a bug in the game, can you see if there's an update to the game available? Mine was a freshly installed version from the EA App.
> There are several types of SimCity, but it is the last version of SimCity that came out after the Society, not the past version. I tried SimCity published by EA in 2013. If it's not that, please l... See more...
> There are several types of SimCity, but it is the last version of SimCity that came out after the Society, not the past version. I tried SimCity published by EA in 2013. If it's not that, please let me know what is the full title of the game or the publish year. Also, it would be great if you provided the steps in the game to cause the crash.
You can find it here: C:\Users\kdaek\AppData\Local\Temp\vmware-kdaek\mkssandbox.dmp I also ran SimCity in a Win10 guest and the game did not crash.
> Is there a difference depending on the OS of the guest or the program that uses DirectX (D3D) to run? Yes, the crash you are seeing is application-specific and switching off DX12Renderer will not ... See more...
> Is there a difference depending on the OS of the guest or the program that uses DirectX (D3D) to run? Yes, the crash you are seeing is application-specific and switching off DX12Renderer will not help. Can you please attach mksSandbox.dmp from the so we can work on the fix?
> However I'm not sure why OP is having this issue as well, as OP is having a decent GPU. My best guess is the OP has a problem when running a specific 3D application, whereas you were seeing it whe... See more...
> However I'm not sure why OP is having this issue as well, as OP is having a decent GPU. My best guess is the OP has a problem when running a specific 3D application, whereas you were seeing it when booting the guest OS.
Yes, at some point in the future you will need to upgrade the GPU to retain 3D support in the VMs.
xphilz2, It looks like the config option was not applied since the VM is encrypted. Can you try adding the configuration option to "C:\ProgramData\VMware\VMware Workstation\config.ini" instead?
xphilz2, Please try adding the following line to the VM's vmx file: mks.enableDX12Renderer=FALSE This is a workaround that is needed for systems with HD 4600 GPUs.