Photoshop CS6: Brush tool sometimes shows "no entry" sign

  • 1
  • Question
  • Updated 4 years ago
  • Answered
  • (Edited)
HI,

I have intermittent unresponsiveness with PsCS6

e.g. sometimes after changing tools back to brush I find I get the no entry sign, but after clicking around a bit and then back onto the mask I was trying to paint on, it then works.

I expect the advice will be first to disable plug-ins? If so - how do I do this (without actually uninstalling them? and what is the procedure for isolating a culprit?

thanks
Photo of Simon King

Simon King

  • 103 Posts
  • 1 Reply Like

Posted 5 years ago

  • 1
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 818 Reply Likes
The no entry sign means that you are targeting something where that tool cannot work. That is not unresponsiveness at all - that is just user error.

To disable a plugin, change the name of the plugin or folder to start with ~
Photo of Simon King

Simon King

  • 103 Posts
  • 1 Reply Like
thanks for the reply Chris - yes that's what I suspected too but for the life of me I can't work out what the error is

If I click out of the brush tool and back into it and then on the mask again it works fine

I will have to try to follow my steps closer next time as the same proceedures don't happen in CS5 which is why I thought it might be something other than my fault
Photo of Chris Cox

Chris Cox

  • 20280 Posts
  • 815 Reply Likes
it's clicking on the mask again that clears the problem - you start out targeting something that isn't visible, or isn't paintable, then end up targeting the mask correctly.
Photo of Simon King

Simon King

  • 103 Posts
  • 1 Reply Like
ah - OK thanks
:)

I still don't understand why it has never happened before (in my previous versions of Ps) but hey ho
:)
Photo of Simon King

Simon King

  • 103 Posts
  • 1 Reply Like
here's another thing I don't understand did this tool change in CS6? (CS5 different -shows -actual pixels etc))

Zoom+control in PsCS6

Photo of Simon King

Simon King

  • 103 Posts
  • 1 Reply Like
Just updated to Mac Os 10.9.3 - that has fixed it!