Min-Yu's Posts

I need the complete log files for vmware.log and mksSandbox.log (right after you encountered the crash). BTW, what is the game you played when you encounter this issue? (If possible, also tell me your game options, such as MSAA 4x, screen resolution, d3d version, etc)

I do not think Apple/Intel has fixed this issue. Since this issue is on Intel GPU only, selecting "Always Use High Performance Graphics (Shorter Battery Life)" will make Fusion use AMD GPU to avoid this issue.

Hello David, It took me some days to reproduce the issue and to figure out what was wrong. I found the following: 1) This is a bug in some Intel Metal drivers. As far as I can tell, this issue only happens on Broadwell, Skylake, Kabylake, and Coffeelake. It will NOT happen on Intel Icelake, AMD GPUs, and Apple M1. 2) You will only see the artifacts when you turn on BOTH the dark mode and the transparency effects in Windows 11. (You can also disable 3D for this Windows 11 VM, if you do not need to run 3D applications.) I have already filed a bug to Apple. Hopefully, they can fix it soon.

Thank you very much for uploading the screenshots and log files. So far, I cannot find any useful clue from them. I also could not reproduce the performance regression. On my machine, it has been always 3~5 FPS at the SL HOME location in both Fusion 12.1.2 and 12.2. Next time, I will try to adjust my graphics settings to those you are using and try SL viewer again.

Those two log files should be under your VM's folder. BTW, I tried Second Life Viewer, but I have not seen huge performance difference so far between Fusion 12.1.2 and 12.2. (From data in its built-in STATISTICS window by pressing Ctrl-Shift-1) I do have some questions for you: 1) If your graphics settings in Second Life Viewer is using the default one (i.e., no preset), it's possible that the Viewer will use more OpenGL features introduced by Fusion 12.2 and slows down everything. Could you please provide screen shots of both the following graphics settings in your Second Life Viewer? (Under menu bar, "Me ---> Preferences --> Graphics", and "Me ---> Preferences --> Graphics ---> Advanced Settings") 2) Did you also update VMware Tools in your VM after you update to Fusion 12.2? 3) Did you also upgrade your VM version (from 18 to 19) when you update to Fusion 12.2? If you did, could you please try to change it back to 18 and see if the performance is improved? To change the version back to 18, please do: a) power off your VM (DO NOT suspend) b) In Virtual Machine --> Settings ---> Compatibility ---> Advanced options, change the "Use Hardware Version" to 18. c) power up your VM again

Hello Idontwanttobeab, Those lines in the log file are not important at all, since Fusion is not using OpenGL on Mac anymore. BTW, which Windows version/edition are you using in the VM? If possible, please upload your vmware.log and mksSandbox.log for us to investigate this issue. Thanks!

This seems to be an issue in the Metal driver on Intel GPUs. We filed an "IOAF code 2067" bug to Apple with another game. Not very sure whether/when Apple will fix it. At this time, could you please try it again with MacOS 12 Monterey beta (or the GA/Release when it is out)? The issue may not be fixed in MacOS 12, but it may provide more detailed information for such IOAD code 2067 issue. Thanks!

It seems that this has been fixed in both MacOS Big Sur 11.5 Beta 3 (20G5042c) and MacOS Monterey 12 beta (21A5248p). Please wait for Apple's release announcements for MacOS Big Sur 11.5 GA and/or MacOS Monterey 12 GA.

Please upload the complete mksSandbox.log next time, or it's really difficult to tell what's really wrong here. So far, the only known issue we had that matches your case is "Altium Designer crashes on AMD GPUs with MacOS Big Sur". Is it what you encountered? It's AMD driver issue and we have notified AMD and is waiting for their fix. Meanwhile, you could try to run Fusion on the integrated Intel GPU if you have one.   Regards,

Hello human_v09, Unfortunately, we were unable to reproduce your crashing issue internally at VMware. Nevertheless, we did have some fixes in our latest version of VMware Fusion that should be able to make Fusion more stable. If possible, could you please try again with the latest MacOS 10.15.7 and/or MacOS 11.1 GA and the latest VMware Fusion 12.1.0? Thank you very much!