FoxtrotIndia's Posts

Guest has 12 GB / 6 cores, so there is no issue with memory trashing. Given that the issue is not there with VS2019, or when turning off 3D acceleration, I suspect this has to do with support for the new accelerated GDI calls.

I still see this problem with Fusion 11.5.1 and macOS 10.15.2. It only happens when I show the virtual machine on an external 1x monitor in full screen mode (Resolution is 3840x1600). Both resize and centered use the full resolution 3840x1600 inside the guest system (Windows). My impression is that in resize to fit mode, VMWare attempts to do some scaling to an output resolution just 1 pixel off. This is most noticeable with text, as the ClearType anti aliasing gets into the wrong places, and text is now ugly to look at. I do not see the problem with resize to fit when using Single Window mode. The resize option gives the display: And the centered option the display:

I have now done some additional testing, and the cursor issues are clearly related to Retina scaling. When I set the external monitor to 2x resolution, and the virtual machine to "Use full resolution for Retina Display", I see also the 20 to 30 pixel offset between cursor and point on the display. Setting the external monitor to use 1x resolution, and my cursor problems disappear.

I also have issues with the cursor on my Windows machines. This is for a virtual machine that uses 1x resolution, and is then scaled to the builtin retina monitor on my MacBook. For me, it seems to  depend on the cursor in use. A standard mouse cursor is accurate, having it change to another shape, like a resizer, it suddenly jumps about a cursor size to the left and up. Really irritating, and should be fixed soon. My suspicion is that Fusion generates does something with the cursor handling, and that during that translation the anchor point is wrongly placed, and so the cursor shown at the wrong position.

Disappointed that this is still the case with Fusion 5.01. Even when I have all my VMs suspended, it still does not switch back to integrated graphics. And on the Retina MacBook, it will not work when discrete graphics are turned off, even with 3D acceleration turned off, the only thing you get is a black screen. I really would like to see an option per virtual machine to tell it whether it needs the discrete graphics support (maybe even dependent on whether you are on batteries or not).

I miss the old way as well, because I now no longer can have xScope active on top of a full screen virtual machine. Quite annoying to have to switch over to windowed mode every time, as the tool is invaluable to make sure that your user interfaces can still be used with (partial) color blindness. Maybe you could allow us to have two virtual monitors with one physical display, each one getting its own window on the Mac? That way I could have the main machine full screen, and a separate window for the testing, where I could also have access to xScope.

Thanks for the answers. I now had the opportunity to view the MacBook in the local store, but they did not yet had the chance to put VMWare onto it to check it out, so it is until next week before I can check things out myself. As for the text, in Windows XP you could use ClearTweak ( http://www.ioisland.com/cleartweak/ ) to adjust how the much contrast the text would have. This might help with the scaling, but I have no idea whether it will still work with Windows 7, probably not.

I have now let this test run for while (Invoked Check for Updates twice on a freshly started Fusion instance, without any VMs running), I have now points at 2.8% utililisation, 9.0% an hour later and 30% another hour later, with it stabilising at around 50% to 60% in the end. Process samples at several points are attached. What I find interesting is that VMWare seems to consume more and more time sorting (CFQSortArray) as time passes, as if it is filling a list, but not removing items from it once done with them.

This is interesting. With my installation as well, when I do a few manual check updates in quick succesion, the CPU load starts to grow, and continues to grow afterwards. I did two test, one with about 20 checks, then the cpu load rose to 100% pretty quickly, and one with 5 checks, then the cpu load rose much slower, after a few minutes it was at 17%, finally rising to over 50%. Strangely I had the impression that if I did only one update check, the cpu load would not rise, staying constant at 0.1%. A second update check 4 minutes later raised the load to 0.9%, and it keeps rising from then on, after a good 5 minutes it is at 1.5%. I will let it run a bit to see where it stops (100%?). In all of this I have started Fusion, it loaded the windows of a few suspended VMs, and I did not start any VMs, I just invoked the check for updates command with the mouse. I had automatic update checking disabled. Given how repeatable this problem is, I hope VMWare will soon be able to fix this annoying issue. Maybe one should disable automatic update checking in the hope that this will prevent VMWare from triggering this bug.

VMWare does not send characters to the Windows running in the virtual machine, but keystrokes for an emulated keyboard. So all keyboard layout settings have to be done in the virtual machine itself. What you can do for Windows is to use the " Microsoft Keyboard Layout Creator " to import your existing keyboard, and package it into its own installer. That should enable you to remove the bootcamp drivers again.