P: CS6 / CC Keyboard shortcuts not responding Mavericks/Yosemite MacOS 10.9; 10.10

Not only; I have the NVIDIA GeForce on my MBP and I get this problem every time I use PhotoShop CC

It is for users with mavericks, ps cs6+, tablet and INTEL HD GRAPHICS, that's why disabling acceleration sometimes work for some users

I have the latest macbook pro with maverick pre-installed and the this bug is driving me crazy..
But talked to my friend today who just went by a pro retouch studio..
He described this issue to retouchers but they couldn't recognize it at all.
They are working with mac pro's (believe it's 2010 models) maverick and photoshop cc and wacom intous 4 and 5. They do not have any problems. They also have a macbook pro (older model) with same software setup which works fine as well.

So i belive it's only some of us having this problem?

Yes, you can, but any document features new to CS6 will come through in a minimal compatibility mode.

Anybody knows if you can open files created on CS6 from CS5?

(Apologies, I tried to edit my earlier comment and add this to it, but I think it timed out.)

What I find most upsetting about this comment is the fact that it reinforces my greatest fear, that Adobe sees this as a superficial problem at its worst. For users such as myself, who experience this bug with consistency, Photoshop is unworkable, and we do not have the luxury of downgrading.

Until more CC/CS6 users *unknowingly* purchase hardware which does not allow downgrading, thus exposing themselves to this error, I have no confidence that either Adobe or Apple will take this error seriously. This is very discouraging to me.

I second the "I would downgrade instantly if I could" statement.

"You can downgrade to MacOS 10.8 at any time."

Chris, do you realize that, as consumers have already reported in this very thread, downgrading is a non-option for those of use with late 2013 Apple hardware?

If I could downgrade to 10.8, I would do so in a heart beat. This is not a trivial matter of users not *wanting* to downgrade: for many of us, downgrading is impossible.

I purchased my hardware under the assumption that it would function as advertised by the developer, and while most Adobe support has been overwhelmingly positive, I find this comment callously curt. While I appreciate your sentiment, I do *not* appreciate your tone.

We're still debugging the issue, and aren't positive where the cause is yet.

Does anyone else find that the problem happens more quickly when painting with longer strokes?