GMA X3100 is pretty bad on OS X right now. All of this does not happen on Windows it's just Apple's drivers. cameras that don't occupy whole window sometimes don't clip their rendering results). Some other features don't work and no workaround is known at this time (e.g. My Laptop specs:Intel(R) 82945G Express Chipset Family (Original Drivers) Os: Windows XP home editionIntel(R) Atom (TM) CPU 230 1. Glow) don't work because Apple didn't implement some OpenGL extensions (three way texture combiner modes).
Some random vertex shaders also produce wrong results in built-in shaders we worked around that by writing separate versions of shaders just for that card. To work around crashes or outright wrong rendering, currently (as of April 2008) in Unity we disable all pixel shaders and shadows. Current Apple's drivers for GMA X3100 are totally and horribly broken. Speed-wise, GMA X3100 has slightly less fillrate than GMA 950, so it is slower than it's predecessor! Yay Intel!
#INTEL GMA 950 945G DRIVER MAC OS X#
Mac OS X uses OpenGL, and in OpenGL there's no way of knowing whether anything runs on the graphics card, so it's hard to tell if the card has vertex transformation unit or not. Theoretically, GMA X3100 also has some vertex transformation unit in hardware, but at least on Windows Intel still has to release drivers that do support that (beta drivers exist which expose that feature, so we might guess it's not "just on paper"). What that means is that longer and more complex shaders can be run - but of course you usually don't want Intel card to run long complex shaders.
Technically, GMA X3100 (aka Intel 965 in Windows world) supports shader model 3.0 (as opposed to shader model 2.0 of GMA 950 / Intel 945).