P: brush cursors not working on 2011 Mac/MacBook Air (OS X 10.7.x Lion)

May be it is a problem of the Intel HD 3000 Graphics Driver which is also used in the 2011 13" Macbook Pros. I have the same Problem with my Mac Mini which uses the same integrated graphic chip.

There been no updates on this in a while and I can't seem to find any issues on the Apple support boards. The problem has to be seen in others. I know this message states Macbook Air, but I have it with a Macbook Pro (early 2011 edition).

Anyone heard of anything? It makes working photos a true pain.

I hope that 10.7.2 will fix it. Apple says that developers should test graphics driver in the beta version.

Same issues here... It's very frustrating... You can get the view back by changing brush sizes sometimes, but it's still a pain when you are trying to work.

Adobe can't do anything about the GPU driver. We're all waiting on Apple to fix their driver software.

I'm having the same issues. It makes working with Photoshop very difficult. I hope Adobe and/or Apple fix it soon.

Same Problem on my brand new Mac Mini Server Mid 2011 with Lion preinstalled. I can't use Brushes larger than 500-600px diameter :-(. It uses the same integrated Intel HD 3000 GPU like MacBook Air 2011 or MacBook Pro 13". For me it seems to be Problem of the Intel HD 3000 Videodriver.

Same problem with Photoshop Lightroom 3.4 Brushes

Chris, I think you once again haven't even taken the time to read what I wrote. You missed the entire point.. again. Let me recap.

You stated something like 'everyone agrees' without qualification = true
I stated that companies have strictly adhered to testing procedures - if the procedure is flawed that can create issues finding bugs = true
I stated that may not be the case in this instance = true
I suggested you may want to quantify results rather than speaking in generalities such as 'everyone agreed' - opinion

I made no blame assignment. Your QE most certainly can have something to do with bugs getting through (whether this was an instance or not). You should not appeal to the masses or authority when seeking to explain a position, without further detailing who those cited are.

Hopefully you understand what I am saying this time. Additionally, you seem to enjoy confrontation for some reason.. and antagonizing the people paying for your product, presumably because your being 'right' is more important.. even when you are clearly not paying attention to what is being written. Very very odd mentality.

QE has nothing to do with this (well, except Apple's).

"everyone" in this case would be Apple and Adobe engineers. I would assume that the engineers on other products affected by the same driver bug would also probably agree.

You're still trying to blame the wrong party, despite all evidence that this is indeed an Apple driver bug.

You missed my point. Companies employ QE testing procedures and adhere to them exactly. If that procedure is flawed one cannot then realistically assume said software is sound.

Whilst that may not be the case in this instance it is a real issue. As such statements made like 'everyone agrees' should really be conditioned with who exactly tested and what those findings were - if not detailing the test methodology. Your response would indicate to a casual viewer that third parties had been involved with the diagnosis, which is not the case. I can think of a great many instances where Adobe was/is to blame.. such as the recent flash kerfuffle and loss of ability to select advanced options within Lion.