I don't know if this will make any difference with your situation with the Arch Linux VM. But you could try switching to OpenGL rendering. Shut down the VM and add the following lines to the VM vmx configuration file.
mks.enableDX11Renderer = "FALSE"
mks.enableGLRenderer = "TRUE"
This is on the assumption that 3D Acceleration is already enabled for the VM, virtual hardware version 12 or 14 and the Windows 10 host has a discrete graphics card either from Nvidia or AMD with OpenGL 4.x drivers. These two lines are not recommended if you only have Intel integrated graphics.
For a Windows 10 host with Nvidia, there are some key differences as seen from the vmware.log and in the Windows 10 guest VM supersampling capability as reported by OpenGL Viewer.
Using GL Rendering
| vmx| I125: SVGA3dCaps: guest, compatibility level: No-Clamping
| vmx| I125: cap[ 73]: 0x00000001 (SUPERSAMPLE)
| vmx| I125: cap[ 87]: 0x00000001 (LINE_AA)
| vmx| I125: cap[ 88]: 0x00000001 (LINE_STIPPLE)
| vmx| I125: cap[ 89]: 10.000000 (MAX_LINE_WIDTH)
| vmx| I125: cap[ 90]: 10.000000 (MAX_AA_LINE_WIDTH)
Using DX11 Rendering
| vmx| I125: SVGA3dCaps: guest, compatibility level: No-Clamping
| vmx| I125: cap[ 73]: 0x00000000 (SUPERSAMPLE)
| vmx| I125: cap[ 87]: 0x00000000 (LINE_AA)
| vmx| I125: cap[ 88]: 0x00000000 (LINE_STIPPLE)
| vmx| I125: cap[ 89]: 1.000000 (MAX_LINE_WIDTH)
| vmx| I125: cap[ 90]: 0.000000 (MAX_AA_LINE_WIDTH)