another_commander wrote:Poro wrote:I would be very suprised if that GPU didn't support shaders, so I'm curious about a_c mentioning the hardware/driver combination. Are there situation where a piece of kit can support pixel shaders, yet the drivers are not 'activating' them properly?
Yes. The classic example is the Intel X3100 Core w/ GM965 chipset. The hardware is perfectly (well, almost

) capable of supporting shaders, but actual shader support was only achieved with the introduction of the version 6.14.10.4990 drivers, sometime towards the end of 2008.
Another classic example is the ATI Mobility drivers.
Basically what happened is that, for many years ATI have had their hands tied with laptop manufacturers (OEMS) who request that ATI do not offer support for their device in the Catalyst Driver. This may seem strange, however makers such as Dell have implemented their own support system and they do not want their customers downloading “reference” drivers from ATI’s home page.
AMD (formerly ATI) introduced the concept of Catalyst Mobility which is a generic driver that works decently for most laptops. The only way they are able to do this is through permission by a laptop manufacturer (OEM) to include their device in the Catalyst Mobility. Unfortunately, only a few vendors have given permission for them to do so.
This leaves laptop owners with ATI graphics chips in a bind, as the OEM manufacturers seem to only update their drivers once in a blue moon, and never to the current state-of-the-art.
This is where the
HardwareHeaven (formerly DriverHeaven) Mobility Modder Tool can help. I've used it on my ASUS Pro31J laptop to great effect, after weeks of unsuccessfully trying to use or modify the latest ATI drivers to work with my X2300 GPU. Now my nebulae look like nebulae, instead of fuzzy square blobs, and I have full shader support!
I'll try to post a tutorial on it soon.