Fusion display choppy if larger than 1024x768 - Macbook

[retro83]

After installing OSX 10.5.2 and the graphics update, the display on Fusion has been very choppy for instance when scrolling documents or moving windows around (in fullscreen or windowed mode). By choppy I mean that it feels almost like running a VNC session rather than interacting with a local machine.

I've noticed now that if I run the display in 1024x768 or less, then the graphics go back to how they were pre-10.5.2 - perfectly smooth.

Has anybody else noticed this or is it just me? The rest of OSX is now much smoother than before, it is just Fusion which is now choppy.

Also should I report this as a bug somewhere?

Thanks.

R.

PS. This is a Macbook SR 2.2GHz C2D with 2GB RAM and X3100 graphics.

[retro83]

Can confirm 100% this is related to 10.5.2's graphics update.

I did a fresh install of OSX and Fusion, then installed the 10.5.2 combo update. The VM was fast and smooth until I installed the graphics update, then it became slow and jerky.

My graphics card details follow:

Intel GMA X3100:

Chipset Model: GMA X3100

Type: Display

Bus: Built-In

VRAM (Total): 144 MB

Vendor: Intel (0x8086)

Device ID: 0x2a02

Revision ID: 0x0003

Displays:

Color LCD:

Display Type: LCD

Resolution: 1280 x 800

Depth: 32-bit Color

Built-In: Yes

Core Image: Hardware Accelerated

Main Display: Yes

Mirror: Off

Online: Yes

Quartz Extreme: Supported

Display Connector:

Status: No display connected

Hope this gets resolved soon!

Regards,

R. 83

[danfairs]

Yup - I'm seeing this too (I've got an eval copy of Fusion, Version 1.1 (62573) - my full copy is on the way from Amazon!

I've just updated to10.5.2 with the subsequent Leopard Graphics Update. Unfortunately I didn't run VMWare before the graphics update, so I can't say which caused it.

Here's my sytem info:Hardware Overview:

Model Name: MacBook

Model Identifier: MacBook3,1

Processor Name: Intel Core 2 Duo

Processor Speed: 2.2 GHz

Number Of Processors: 1

Total Number Of Cores: 2

L2 Cache: 4 MB

Memory: 4 GB

Bus Speed: 800 MHz

Boot ROM Version: MB31.008E.B01

Chipset Model: GMA X3100

Type: Display

Bus: Built-In

VRAM (Total): 144 MB

Vendor: Intel (0x8086)

Device ID: 0x2a02

Revision ID: 0x0003

Displays:

Color LCD:

Display Type: LCD

Resolution: 1280 x 800

Depth: 32-bit Color

Built-In: Yes

Core Image: Hardware Accelerated

Mirror: Off

Online: Yes

Quartz Extreme: Supported

DELL 2005FPW:

Resolution: 1680 x 1050 @ 60 Hz

Depth: 32-bit Color

Core Image: Hardware Accelerated

Main Display: Yes

Mirror: Off

Online: Yes

Quartz Extreme: Supported

Rotation: Supported

Note that I'm using VMware on the larger of the two screens. Moving to the smaller one doesn't make any difference - even dropping below 1024x768 as the OP suggested.

Basically, moving windows around is choppy.

Guest OS is Windows XP MCE SP2, with 1.5GB of RAM allocated to it.

Any pointers gratefully received - even if they involve software updates, as hopefully my copy of Fusion will turn up tomorrow!

[retro83]

I'm so glad that somebody else is experiencing this issue!

My solution for now is to avoid the graphics update It certainly seems to be caused by the new X3100 drivers.

I have submitted a bug report to Apple, under the number #5737987. I do not know where to submit a bug to VMWare, but hopefully between them they will fix this quickly!

Please reply if you make any progress...

[admin]

I filed this internally as bug 239210.

If anyone else sees this after applying the Leopard Graphics Update, or has a similar machine (MacBook with X3100 graphics) but does not see it after applying the update, that would be useful to know.

[retro83]

Thank you Etung!

[pds2208]

I don't know what caused this but after updating to 10.5.2. & the graphics update, I find vmware to be unusable for some applications. Specifically I use the arkadin conference service, which uses Java, in windows xp and you can wait a long time while the screen redraws.

[admin]

...and what type of Mac do you have, and what version of Fusion?

[pds2208]

Macbook pro 2.4ghz / 4gb ram Fusion 1.1.1

[kd7290]

I can confirm on the graphics tearing after updating OS X with 10.5.2 and Graphics update. Running Fusion 1.1.1 Trial on MacBook Pro, 2.16GHz, 2GB RAM, ATI x1600

[Tentative]

I have the same problem.

I use the trial version of Fusion to play some little games like Worms on my MacBook. Everything was smooth until the 10.5.2 upgrade.

I was thinking about adding some ram (I have currently 1go ram).

But it seems not to be the problem finally.

I hope this will quickly be fixed, in the meanwhile, I think I'm going to reinstall leopard 10.5.1 or 10.5.2 without the graphics update.

[admin]

Macbook pro 2.4ghz / 4gb ram Fusion 1.1.1

What graphics card?

For what it's worth, I have a MacBook Pro (GeForce 8600), 10.5.2+Leopard Graphics Update, Fusion 1.1.1, and don't see any tearing or slowness.

[iCV]

I've the same problem on my MacBook C2D Santa Rosa 2,2GhZ X3100 Graphics

OSX 10.5.2 with LGU and Fusion 1.1.1

[danfairs]

Just to update - I'm now running a fully licensed VMWare Fusion, and have upgraded to 1.1.1 - problem still occurring.

[retro83]

Sorry to bump this but I wondered if anybody had made any progress on the issue yet?

Surely it must be affecting quite a few users..? :_|

Thanks!

[iCV]

any news about this issue?

[danfairs]

@Tentative: Did you do the reinstall without the graphics update? Did the problem recur without it, or do you still see it?

[retro83]

I reinstalled with all updates except the Graphics Update, and the issue was gone. After installing LGU 1.0 it was back

[danfairs]

Thanks for trying that.

@etung - this would seem to confirm that it's the graphics update that's responsible, and from reading the thread that MacBooks and MacBook Pros that don't use an nVidia chipset (etung, yours is the only report where this problem isn't happening, and that's with an nVidia card) are all affected, including Intel graphics and ATI graphics. Any update on this issue from VMWare?

[admin]

We've tried to reproduce this internally with an appropriate MacBook, but there might be something else going on because the result was "slightly choppier, but not terrible"