Hi,
I think your grep is too restrictive as it doesn't show context like what renderer is being used.
Here's an output of one of my throw away debian VM's (haven't used Ubuntu in a long time)
First before enabling 3D:
ploppy@vmplayer-test:~$ glxinfo | grep -i opengl
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: llvmpipe (LLVM 7.0, 256 bits)
OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.3.6
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.1 Mesa 18.3.6
OpenGL shading language version string: 1.40
OpenGL context flags: (none)
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.3.6
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:
ploppy@vmplayer-test:~$ cat /etc/*release
PRETTY_NAME="Debian GNU/Linux 10 (buster)"
NAME="Debian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
Then I shut down the VM and enabled 3D and ran the test again:
ploppy@vmplayer-test:~$ glxinfo | grep -i opengl
OpenGL vendor string: VMware, Inc.
OpenGL renderer string: SVGA3D; build: RELEASE; LLVM;
OpenGL core profile version string: 3.3 (Core Profile) Mesa 18.3.6
OpenGL core profile shading language version string: 3.30
OpenGL core profile context flags: (none)
OpenGL core profile profile mask: core profile
OpenGL core profile extensions:
OpenGL version string: 3.3 (Compatibility Profile) Mesa 18.3.6
OpenGL shading language version string: 3.30
OpenGL context flags: (none)
OpenGL profile mask: compatibility profile
OpenGL extensions:
OpenGL ES profile version string: OpenGL ES 3.0 Mesa 18.3.6
OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00
OpenGL ES profile extensions:
As you can see, first before the 3D enablement we used the llvmpipe software renderer.
After it was enabled the renderer becomes SVGA3D, which is a (virtual) hardware renderer.
edit: Note that one possible reason that your VM is showing a lower openGL version is if your virtual hardware is not set to the latest.
Make sure it is set to the latest virtual hardware under settings -> compatiblity
--
Wil
Hi,
I take it you already installed open-vm-tools-desktop ?
If not run:
sudo apt-get install open-vm-tools-desktop
and reboot the VM, then try again.
Also make sure that your VM's compatibility is set to the latest version (can only change that with the VM shut down)
--
Wil
Hi,
OK.. I see that your model macbook has dual GPU's there's also a intel UHD graphics 630 onboard.
It is possible that VMware Fusion is using the Intel GPU instead of your discrete GPU.
There's this post that suggests how-to switch using undocumented features in the .vmx file.
https://communities.vmware.com/message/2673322#2673322
But.. it's for DirectX and Workstation. You're using Linux on Fusion.
On VMware Fusion you have in the settings for the VM's display on dual GPU hosts an option "Battery Life" where you can suggest if it should use "High Performance" or not.
For your issue you should set that to "Always use High Performance" if not already set.
--
Wil
Yes, I did check the option of "always use high-performance graphics" as shown in the below figure.
Then I'm out of tips, but there are others at this forum that might be able to help.
For them to be able to help you would need to attach log files to your reply here.
These log files can be found in the VM's bundle (right click the VM and select "Show package contents")
The log files needed are: vmware.log and mkssandbox.log
--
Wil
