video Ram stuck at 4MB, what now?

[NoobforVM]

VMware workstation1 6 player
windows 10 pro host
windows 10 pro guest
gpu 2080ti
ram 128gb
cpu 8700k

I changed the vrram size in the vmx file, nothing.. machine still uses 4mb.

it says shared memory around 3000mb but Display memory VRAM only 4mb.

Photoshop does not work, chrome display badly.

What now?

PLease help...

[scott28tt]

@NoobforVM 

Moderator: Please create threads in the area for the product used - moved to Workstation Player Discussions

[banackm]

I'm not sure exactly where you're seeing that reported, but there's different kinds of graphics memory.

Physical graphics cards have memory as part of the card, that's commonly called "on-board" or "Dedicated" graphics memory, and then they can also access system memory for some graphics operations, which is commonly referred to in Windows as "Shared Memory".

For new, modern VMs, VMware's virtual graphics device functions more like an integrated graphics card, in that it primarily uses shared system memory, rather than on-board dedicated memory.

So if you turned up the "Graphics Memory" on the VM in the Workstation UI, the "4MB" value you're seeing is probably the dedicated memory in the virtual PCI-card of our graphics device, which isn't actually used for anything after the guest has finished booting and the graphics driver is loaded.

Whereas the "3000MB" value is probably the amount of system-memory that your guest applications are allowed to use for graphics operations, which is actually the amount of graphics resources the application can create.

So that sounds correct to me.

I'm not sure why you're having Chrome/Photoshop problems though... Can you post a vmware.log file for us to look at?

[NoobforVM]

on one of my host machines VRAM says  11048 and that is  exactly what this GPU can give me.

On my virtual machine it says 4 mb at the same spot.

As you can see in dxdiag it says vram as display memory and below that there is something called "shared memory" which is !? I have no clue what.



So now for sure I know display memory Vram stands for what GB my graphics card has.

Right?

The same value on my virtual machine is literally 4 mb. For sure that is the reason why Photoshop fails. This has to be addressed somehow but how!?

[Ebrithil]

Hi everyone,

I would like to revive this thread as there are many of us who are experiencing this problem. Instead of starting a new thread I thought we could pursue the resolution here.

I am also having this issue where my dedicated video memory is at 4mb and will not budge. The tools are installed and updated, I have accelerate 3D graphics checked and working fine as shown below:

VM settings:

Properties in Advanced Display Settings - Here you can see the 4 MB:

Below is what's included within the .vmx configuration file:

.encoding = "windows-1252"
config.version = "8"
virtualHW.version = "19"
pciBridge0.present = "TRUE"
pciBridge4.present = "TRUE"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge4.functions = "8"
pciBridge5.present = "TRUE"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge5.functions = "8"
pciBridge6.present = "TRUE"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge6.functions = "8"
pciBridge7.present = "TRUE"
pciBridge7.virtualDev = "pcieRootPort"
pciBridge7.functions = "8"
vmci0.present = "TRUE"
hpet0.present = "TRUE"
nvram = "Windows 10 Pro x64.nvram"
virtualHW.productCompatibility = "hosted"
gui.exitOnCLIHLT = "FALSE"
powerType.powerOff = "soft"
powerType.powerOn = "soft"
powerType.suspend = "soft"
powerType.reset = "soft"
displayName = "Windows 10 Pro x64"
usb.vbluetooth.startConnected = "TRUE"
firmware = "efi"
usb.restrictions.defaultAllow = "FALSE"
sensor.location = "pass-through"
guestOS = "windows9-64"
tools.syncTime = "TRUE"
sound.autoDetect = "TRUE"
sound.virtualDev = "hdaudio"
sound.fileName = "-1"
sound.present = "TRUE"
numvcpus = "4"
memsize = "16384"
mem.hotadd = "TRUE"
sata0.present = "TRUE"
nvme0.present = "TRUE"
nvme0:0.fileName = "Windows 10 Pro x64.vmdk"
nvme0:0.present = "TRUE"
sata0:1.deviceType = "cdrom-image"
sata0:1.fileName = "C:\Users\seb1l\Documents\Windows ISO.iso"
sata0:1.present = "TRUE"
usb.present = "TRUE"
ehci.present = "TRUE"
usb_xhci.present = "TRUE"
usb.generic.allowHID = "TRUE"
svga.graphicsMemoryKB = "4194304"
ethernet0.connectionType = "nat"
ethernet0.addressType = "generated"
ethernet0.virtualDev = "e1000e"
serial0.fileType = "thinprint"
serial0.fileName = "thinprint"
ethernet0.present = "TRUE"
serial0.present = "TRUE"
extendedConfigFile = "Windows 10 Pro x64.vmxf"
floppy0.present = "FALSE"
numa.autosize.cookie = "40012"
numa.autosize.vcpu.maxPerVirtualNode = "4"
uuid.bios = "56 4d db 02 da 4e a7 c4-62 e1 b4 47 9a d7 9d ab"
uuid.location = "56 4d db 02 da 4e a7 c4-62 e1 b4 47 9a d7 9d ab"
vm.genid = "1695637510790237380"
vm.genidX = "-3445632076046162160"
nvme0:0.redo = ""
pciBridge0.pciSlotNumber = "17"
pciBridge4.pciSlotNumber = "21"
pciBridge5.pciSlotNumber = "22"
pciBridge6.pciSlotNumber = "23"
pciBridge7.pciSlotNumber = "24"
usb.pciSlotNumber = "32"
ethernet0.pciSlotNumber = "160"
sound.pciSlotNumber = "33"
ehci.pciSlotNumber = "34"
usb_xhci.pciSlotNumber = "192"
sata0.pciSlotNumber = "35"
nvme0.pciSlotNumber = "224"
svga.vramSize = "268435456"
vmotion.checkpointFBSize = "4194304"
vmotion.checkpointSVGAPrimarySize = "268435456"
vmotion.svga.mobMaxSize = "1073741824"
vmotion.svga.graphicsMemoryKB = "4194304"
vmotion.svga.supports3D = "1"
vmotion.svga.baseCapsLevel = "9"
vmotion.svga.maxPointSize = "1"
vmotion.svga.maxTextureSize = "16384"
vmotion.svga.maxVolumeExtent = "2048"
vmotion.svga.maxTextureAnisotropy = "16"
vmotion.svga.lineStipple = "0"
vmotion.svga.dxMaxConstantBuffers = "14"
vmotion.svga.dxProvokingVertex = "0"
vmotion.svga.sm41 = "1"
vmotion.svga.multisample2x = "1"
vmotion.svga.multisample4x = "1"
vmotion.svga.msFullQuality = "1"
vmotion.svga.logicOps = "1"
vmotion.svga.bc67 = "9"
vmotion.svga.sm5 = "1"
vmotion.svga.multisample8x = "1"
vmotion.svga.logicBlendOps = "1"
ethernet0.generatedAddress = "00:0c:29:d7:9d:ab"
ethernet0.generatedAddressOffset = "0"
vmci0.id = "-1697145429"
monitor.phys_bits_used = "45"
cleanShutdown = "FALSE"
softPowerOff = "FALSE"
checkpoint.vmState = ""
sata0:1.startConnected = "TRUE"
toolsInstallManager.lastInstallError = "0"
tools.remindInstall = "FALSE"
toolsInstallManager.updateCounter = "2"
svga.guestBackedPrimaryAware = "TRUE"
guestInfo.detailed.data = "architecture='X86' bitness='64' buildNumber='19043' distroName='Windows' distroVersion='10.0' familyName='Windows' kernelVersion='19043.1288' prettyName='Windows 10 Pro, 64-bit (Build 19043.1288)'"
tools.upgrade.policy = "upgradeAtPowerCycle"
mks.dx11.vendorID = "0x10de"
workingDir = "."
mks.enable3d = "TRUE"
usb_xhci:4.present = "TRUE"
usb_xhci:4.deviceType = "hid"
usb_xhci:4.port = "4"
usb_xhci:4.parent = "-1"
unity.wasCapable = "TRUE"

vmotion.checkpointFBSize = "4194304"
vmotion.checkpointSVGAPrimarySize = "268435456"
vmotion.svga.mobMaxSize = "1073741824"
vmotion.svga.graphicsMemoryKB = "4194304"
vmotion.svga.supports3D = "1"
vmotion.svga.baseCapsLevel = "9"
vmotion.svga.maxPointSize = "1"
vmotion.svga.maxTextureSize = "16384"
vmotion.svga.maxVolumeExtent = "2048"
vmotion.svga.maxTextureAnisotropy = "16"
vmotion.svga.lineStipple = "0"
vmotion.svga.dxMaxConstantBuffers = "14"
vmotion.svga.dxProvokingVertex = "0"
vmotion.svga.sm41 = "1"
vmotion.svga.multisample2x = "1"
vmotion.svga.multisample4x = "1"
vmotion.svga.msFullQuality = "1"
vmotion.svga.logicOps = "1"
vmotion.svga.bc67 = "9"
vmotion.svga.sm5 = "1"
vmotion.svga.multisample8x = "1"
vmotion.svga.logicBlendOps = "1"
ethernet0.generatedAddress = "00:0c:29:d7:9d:ab"
ethernet0.generatedAddressOffset = "0"
vmci0.id = "-1697145429"
monitor.phys_bits_used = "45"
cleanShutdown = "TRUE"
softPowerOff = "TRUE"
checkpoint.vmState = ""
sata0:1.startConnected = "TRUE"
toolsInstallManager.lastInstallError = "0"
tools.remindInstall = "FALSE"
toolsInstallManager.updateCounter = "2"
svga.guestBackedPrimaryAware = "TRUE"
guestInfo.detailed.data = "architecture='X86' bitness='64' buildNumber='19043' distroName='Windows' distroVersion='10.0' familyName='Windows' kernelVersion='19043.1288' prettyName='Windows 10 Pro, 64-bit (Build 19043.1288)'"
tools.upgrade.policy = "upgradeAtPowerCycle"
mks.dx11.vendorID = "0x10de"
workingDir = "."
mks.enable3d = "TRUE"
usb_xhci:4.present = "TRUE"
usb_xhci:4.deviceType = "hid"
usb_xhci:4.port = "4"
usb_xhci:4.parent = "-1"


I really need the 4mb to become 4gb - Please let me know how we can fix this.

Best,

[banackm]

Unfortunately, I wouldn't expect a fix for this from the VMware-side any time soon. 

We are correctly reporting how our virtual graphics card is representing it's memory layout, it just happens to be unusual for high-end graphics cards to not have much Dedicated memory, and so this causes application compatibility issues.  We have to dig into them individually and usually work with the 3rd-party software vendor to resolve them, so we typically can't resolve them quickly.

We're aware of the Photoshop issue, and we've seen issues with Chrome that tend to come and go as they release new versions. If there are other applications that are running into graphics memory problems please let us know the specific applications and we'll see what we can do.

Otherwise the best advice I can offer in general would be to try and contact the other software vendor and see if they have a work-around or a fix they can offer to force their accelerated path on.

[scott28tt]

@Ebrithil 
VMTN has a "spoiler" function which is ideal for your VMX file text, making it easier for everyone to scroll through the thread, this is the toolbar icon to add a spoiler: 

Here's your VMX file:

Spoiler

.encoding = "windows-1252"
config.version = "8"
virtualHW.version = "19"
pciBridge0.present = "TRUE"
pciBridge4.present = "TRUE"
pciBridge4.virtualDev = "pcieRootPort"
pciBridge4.functions = "8"
pciBridge5.present = "TRUE"
pciBridge5.virtualDev = "pcieRootPort"
pciBridge5.functions = "8"
pciBridge6.present = "TRUE"
pciBridge6.virtualDev = "pcieRootPort"
pciBridge6.functions = "8"
pciBridge7.present = "TRUE"
pciBridge7.virtualDev = "pcieRootPort"
pciBridge7.functions = "8"
vmci0.present = "TRUE"
hpet0.present = "TRUE"
nvram = "Windows 10 Pro x64.nvram"
virtualHW.productCompatibility = "hosted"
gui.exitOnCLIHLT = "FALSE"
powerType.powerOff = "soft"
powerType.powerOn = "soft"
powerType.suspend = "soft"
powerType.reset = "soft"
displayName = "Windows 10 Pro x64"
usb.vbluetooth.startConnected = "TRUE"
firmware = "efi"
usb.restrictions.defaultAllow = "FALSE"
sensor.location = "pass-through"
guestOS = "windows9-64"
tools.syncTime = "TRUE"
sound.autoDetect = "TRUE"
sound.virtualDev = "hdaudio"
sound.fileName = "-1"
sound.present = "TRUE"
numvcpus = "4"
memsize = "16384"
mem.hotadd = "TRUE"
sata0.present = "TRUE"
nvme0.present = "TRUE"
nvme0:0.fileName = "Windows 10 Pro x64.vmdk"
nvme0:0.present = "TRUE"
sata0:1.deviceType = "cdrom-image"
sata0:1.fileName = "C:\Users\seb1l\Documents\Windows ISO.iso"
sata0:1.present = "TRUE"
usb.present = "TRUE"
ehci.present = "TRUE"
usb_xhci.present = "TRUE"
usb.generic.allowHID = "TRUE"
svga.graphicsMemoryKB = "4194304"
ethernet0.connectionType = "nat"
ethernet0.addressType = "generated"
ethernet0.virtualDev = "e1000e"
serial0.fileType = "thinprint"
serial0.fileName = "thinprint"
ethernet0.present = "TRUE"
serial0.present = "TRUE"
extendedConfigFile = "Windows 10 Pro x64.vmxf"
floppy0.present = "FALSE"
numa.autosize.cookie = "40012"
numa.autosize.vcpu.maxPerVirtualNode = "4"
uuid.bios = "56 4d db 02 da 4e a7 c4-62 e1 b4 47 9a d7 9d ab"
uuid.location = "56 4d db 02 da 4e a7 c4-62 e1 b4 47 9a d7 9d ab"
vm.genid = "1695637510790237380"
vm.genidX = "-3445632076046162160"
nvme0:0.redo = ""
pciBridge0.pciSlotNumber = "17"
pciBridge4.pciSlotNumber = "21"
pciBridge5.pciSlotNumber = "22"
pciBridge6.pciSlotNumber = "23"
pciBridge7.pciSlotNumber = "24"
usb.pciSlotNumber = "32"
ethernet0.pciSlotNumber = "160"
sound.pciSlotNumber = "33"
ehci.pciSlotNumber = "34"
usb_xhci.pciSlotNumber = "192"
sata0.pciSlotNumber = "35"
nvme0.pciSlotNumber = "224"
svga.vramSize = "268435456"
vmotion.checkpointFBSize = "4194304"
vmotion.checkpointSVGAPrimarySize = "268435456"
vmotion.svga.mobMaxSize = "1073741824"
vmotion.svga.graphicsMemoryKB = "4194304"
vmotion.svga.supports3D = "1"
vmotion.svga.baseCapsLevel = "9"
vmotion.svga.maxPointSize = "1"
vmotion.svga.maxTextureSize = "16384"
vmotion.svga.maxVolumeExtent = "2048"
vmotion.svga.maxTextureAnisotropy = "16"
vmotion.svga.lineStipple = "0"
vmotion.svga.dxMaxConstantBuffers = "14"
vmotion.svga.dxProvokingVertex = "0"
vmotion.svga.sm41 = "1"
vmotion.svga.multisample2x = "1"
vmotion.svga.multisample4x = "1"
vmotion.svga.msFullQuality = "1"
vmotion.svga.logicOps = "1"
vmotion.svga.bc67 = "9"
vmotion.svga.sm5 = "1"
vmotion.svga.multisample8x = "1"
vmotion.svga.logicBlendOps = "1"
ethernet0.generatedAddress = "00:0c:29:d7:9d:ab"
ethernet0.generatedAddressOffset = "0"
vmci0.id = "-1697145429"
monitor.phys_bits_used = "45"
cleanShutdown = "FALSE"
softPowerOff = "FALSE"
checkpoint.vmState = ""
sata0:1.startConnected = "TRUE"
toolsInstallManager.lastInstallError = "0"
tools.remindInstall = "FALSE"
toolsInstallManager.updateCounter = "2"
svga.guestBackedPrimaryAware = "TRUE"
guestInfo.detailed.data = "architecture='X86' bitness='64' buildNumber='19043' distroName='Windows' distroVersion='10.0' familyName='Windows' kernelVersion='19043.1288' prettyName='Windows 10 Pro, 64-bit (Build 19043.1288)'"
tools.upgrade.policy = "upgradeAtPowerCycle"
mks.dx11.vendorID = "0x10de"
workingDir = "."
mks.enable3d = "TRUE"
usb_xhci:4.present = "TRUE"
usb_xhci:4.deviceType = "hid"
usb_xhci:4.port = "4"
usb_xhci:4.parent = "-1"
unity.wasCapable = "TRUE"

vmotion.checkpointFBSize = "4194304"
vmotion.checkpointSVGAPrimarySize = "268435456"
vmotion.svga.mobMaxSize = "1073741824"
vmotion.svga.graphicsMemoryKB = "4194304"
vmotion.svga.supports3D = "1"
vmotion.svga.baseCapsLevel = "9"
vmotion.svga.maxPointSize = "1"
vmotion.svga.maxTextureSize = "16384"
vmotion.svga.maxVolumeExtent = "2048"
vmotion.svga.maxTextureAnisotropy = "16"
vmotion.svga.lineStipple = "0"
vmotion.svga.dxMaxConstantBuffers = "14"
vmotion.svga.dxProvokingVertex = "0"
vmotion.svga.sm41 = "1"
vmotion.svga.multisample2x = "1"
vmotion.svga.multisample4x = "1"
vmotion.svga.msFullQuality = "1"
vmotion.svga.logicOps = "1"
vmotion.svga.bc67 = "9"
vmotion.svga.sm5 = "1"
vmotion.svga.multisample8x = "1"
vmotion.svga.logicBlendOps = "1"
ethernet0.generatedAddress = "00:0c:29:d7:9d:ab"
ethernet0.generatedAddressOffset = "0"
vmci0.id = "-1697145429"
monitor.phys_bits_used = "45"
cleanShutdown = "TRUE"
softPowerOff = "TRUE"
checkpoint.vmState = ""
sata0:1.startConnected = "TRUE"
toolsInstallManager.lastInstallError = "0"
tools.remindInstall = "FALSE"
toolsInstallManager.updateCounter = "2"
svga.guestBackedPrimaryAware = "TRUE"
guestInfo.detailed.data = "architecture='X86' bitness='64' buildNumber='19043' distroName='Windows' distroVersion='10.0' familyName='Windows' kernelVersion='19043.1288' prettyName='Windows 10 Pro, 64-bit (Build 19043.1288)'"
tools.upgrade.policy = "upgradeAtPowerCycle"
mks.dx11.vendorID = "0x10de"
workingDir = "."
mks.enable3d = "TRUE"
usb_xhci:4.present = "TRUE"
usb_xhci:4.deviceType = "hid"
usb_xhci:4.port = "4"
usb_xhci:4.parent = "-1"

[Curlyman15]

Hey there!

So is this a "sorry 'bout your luck" scenario or do we have any hope of being able to get Windows to recognize more than the minimal 4mb VRAM size? I need a fix for this if one exists!

[VMHappyUser]

Is there any way to raise those 4MB into something usable? Nothing graphically acceptable can work that way and I remember in old versions we were able to tweak this value!.

Just in case it helps in my case the host computer has a dedicated and an integrated graphics card.

From other side I also remember VMWare having troubles when directx 10 came so I understand directx 11 and 12 was also a bit of effort to add to their graphics adapter. Could this be the reason why it is not possible to tweak it anymore?.

To me being able to raise it up to 4GB would be enough.

Please in case it is possible, help us with a solution.

[VMHappyUser]

So is it there a way to make VMWare use the dedicated memory in a shared way with the host instead of using the integrated graphics card?

[VMHappyUser]

It is really weird that disabling the "Enable 3d acceleration" toggle:

We got the driver inside the virtual machine to show this stats:

Enabling it comes with this 4MB that makes feel indeed the big difference, while we are losing about 4GB of shared memory:

Please, note there is 4MB now instead of 0MB. Hopefully those 4MB are accelerating things quite a lot!

But it doesn't, the performance is nearly the same!. Both are running the same game at an amazing 10 fps!

So I actually don't see the point guys. I would say VMWare Workstation has lost his hegemony where he was the boss. Honestly being able to use the main gpu in a shared way with the host should a mandatory!.

Have you a logic explanation for it?. When did VMWare Workstation lost this absolutely primary capability?

[banackm]

With 3d acceleration disabled, you're using Microsoft's in-guest software renderer for your Direct3D graphics rendering.  So the "12GB" of memory that they display there is really misleading and just notes that their software renderer can use that much memory.

When 3d acceleration is enabled, then Microsoft starts using our Direct3D graphics driver and is subject to the memory capabilities of our virtual graphics device.  But it will really be running on your host's GPU in that case.  I'm comparing us to an integrated graphics card only in terms of the layout of our virtual PCI device.  We will still accelerate your the VMs graphics rendering on your host's graphics card regardless of whether you have an integrated or discrete GPU on your host.

The 4MB that it displays there for "VRAM" is also misleading, because it can only be used for your primary display output, and not for general graphics rendering.

I'm not sure what specific application you're running that isn't seeing a benefit from enabling 3D acceleration in the VM, but possibly it requires a version of Direct3D higher than what we support.  We should be able to support up to Direct3D 11 depending on your host configuration, but if an application requires Direct3D 12 then it may be running on Microsoft's in-guest software renderer.

[lasponger]

Just as a heads up, you're going to start seeing this a lot more going forward, I think.  The latest version of Adobe CC (2022 version) has made a change in the last update a few days ago so that photoshop/illustrator now show a warning every time you launch it saying that the graphics processor is incompatible (OpenCL Unavailable, DirectX Unavailable, Insufficient VRAM, OpenGL).  I've got a vm with 8gb Graphics Memory assigned, 3d Accelerated in the settings and am seeing exactly the same 4mb Display Memory (VRAM) in dxdiag that the previous posters are seeing.  This is with an RTX 3080 ti with 12gb memory on the host machine, so the hardware is fine.

This really needs to be fixed.  VMs in general are becoming more and more ubiquitous and widely used with the expansion of Work from Home jobs, especially outside of the typical Tech Sector users, and with that will come more graphic intensive workloads being run in VMs.  Adobe sure isn't going to be reverting this change anytime soon, and there's no reason why Workstation shouldn't pass this information into the guest vm accurately.  This issue is only going to grow.

[VMHappyUser]

I am using an NVidia Geforce 1080 gtx Ti in the host computer.

To me after using VMWorkstation for more than 18 years it seems like it is a bug.

Willing to help find the issue I would adventure to say that is probably coming from the fact that nowadays most of the motherboards always come with an integrated graphics card apart from the optional dedicated. It could be possible that your driver is not selecting the proper host graphics adapter selecting the integrated instead of the dedicated. Again this is nowadays a common error in some applications where developers, like me, need to properly select the most empowered device available. Being trivial to make it usually by asking for their information.

Please make this specific change and hopefully it will help!

[banackm]

@lasponger 

Yeah, the deeper problem you're running into there is that Adobe requires DirectX 12, and today we only support DirectX 11.  There's no easy fix for that, but it's certainly something we're working towards.  Assuming we could do something about the memory value, I suspect that wouldn't actually help without also supporting the higher DirectX version.

@VMHappyUser 

You can check in your vmware.log to see which host graphics card we started on.  But the memory limitations here are a function of our virtual graphics hardware, and not anything to do with the host graphics card.

There's no way at the moment to increase the Dedicated Display Memory to 1.5 GB for any host/guest configuration, because unfortunately the way that we are doing the graphics virtualization makes that proposition more complicated than it sounds.

That said, we're aware of these issues, and we're certainly open to anything we can do on our end to make Adobe software work better in a VM.  So our development team will do our best to find a solution here.

[VMHappyUser]

@banackmthanks for the reply. I can confirm that the virtual machine is trying  to use the dedicated graphics adapter.

Do you have any ETA to improve the virtual graphics driver so it can accept more vram or accelerate/improve it even further?

Profiling along the virtual machine is quite clear that the bottleneck is the graphics performance.

[banackm]

We can't talk about dates for specific features on the forums other than to quote any official announcement VMware has made.  But we do have a dedicated team working on graphics that tries to deliver performance improvements with every major release.

[seregg]

why in windows 10 - 4mb, and in win 7 128mb? Can't you do it in Win 10 like you did in Win 7?

[VMHappyUser]

@seregg 

I think they already explained this.

VMWare has troubles still with directx 10 and 11 which is what windows 7 uses.

Windows 10 uses directx 12 so I guess their virtual driver has even more issues to  solve there still.

[banackm]

You can get it to read 128MB on older hardware versions, but we were unable to make that number go any higher using our old design.  The newer hardware versions actually allow applications to get access to more memory even though that number reads lower.

We're definitely not happy that applications are explicitly checking that value to determine compatibility, and we don't have any good solutions for that at the moment.  But our actual graphics architecture runs applications better now with our new design.