Photoshop CS4. CS5, CS6: Cursor disappears on Mountain Lion (MacOS 10.8) with AMD/ATI GPUs
this problem +1
This is a known bug in MacOS 10.8 that affects multiple applications.
(it happens to me most often in Safari, with no Photoshop running)
We have notified Apple of the problem, and are waiting for an OS fix from Apple. It is still unfixed as of MacOS 10.8.3.
Unfortunately, this is something that we cannot work around.
This may be a solution. First, some background.
I experienced the disappearing cursor in CS5.5 after upgrading to 10.8 from 10.6. I reverted to Snow Leopard successfully. A couple of weeks ago I decided to give 10.8 another try. But this time I skipped upgrading over a Snow Leopard installation.
I backed up my boot drive, wiped it and then booted my 10.8 test installation from an external disk, restarted, and booted the Recovery partition. I installed 10.8 on my MBP's internal drive from the Recovery partition. I then restored my apps and files, after OS installation, using Migration Assistant.
After an hour of running small to large cursor exercises, Photoshop behaved as it should. No cursor issues. Last Friday I upgraded to CS6. So far so good.
So, upgrading over the 10.6 install may be the culprit, forcing the misalignment of ones and zeros that have caused so much pain and suffering. And if this "solution" continues to work, I'll likely tear everything apart and do a complete virgin install of everything from the ground up.
I fear there will never be a solution for this truky annoying problem. All in all Adobe is constantly fingerpointing towards Apple but sofar nothing has happened. Now in a few weeks we are being more or less forced towards CC. This means for me CS6 has never really worked while I paid for it. Chris can you imagine how willing I am upgrading towards CC if I have no guaruantees that I will receive a fully functional product. Or even that bugs will be taken seriously?
Chris, you obviously have a very good idea what area of the OS and its interaction with third party applications/drivers is causing this issue and I think we all understand that you are not at liberty to describe that directly with us. Would it be possible to list some of the strategies suggested on here that will NOT fix it, it seems that a huge amount of production time is being wasted by users desperate to fix this annoying issue by re-installing OS's, removing Flash, levelling drives etc. Is that allowed? Obviously you could just say that nothing works, so I guess this is a pointless question, but maybe you can cast some light on this by omission as you seem to be the only person with real technical knowledge of the problem.