Photoshop: Tilde (~) - Toggle composite and grayscale mask in Quick Mask mode is not working.

  • 1
  • Problem
  • Updated 2 years ago
  • In Progress
  • (Edited)
The ~ ( tilde ) shortcut to view mask as grayscale stopped working. I can see the layer mask as a 50% red overlay by pressing \ (backslash), but not as a garyscale. and I usually go around both view modes when working on masks. I have already reset photoshop settings but it did nothing.
Photo of Gustavo Romanelli

Gustavo Romanelli

  • 7 Posts
  • 1 Reply Like
  • frustrated

Posted 2 years ago

  • 1
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 13977 Posts
  • 1671 Reply Likes
Seems to be working here (Mac, English app/OS and keyboard layout) What OS are you on? What language is PS, your OS and keyboard?
Photo of Gustavo Romanelli

Gustavo Romanelli

  • 7 Posts
  • 1 Reply Like
iMac with MacOS Sierra , Photoshop CC 2015.5.1, US wireless keyboard set in the OS as "U.S international - PC".
I recently re installed my OS and updated it to Sierra, it was after doing so that the Tilde shortcut stopped working. Not sure if this process interfered in PS shortcuts, though.
Photo of Gustavo Romanelli

Gustavo Romanelli

  • 7 Posts
  • 1 Reply Like
Actually, right after sending this reply I tried changing the keyboard to just " US"  and it worked. What is weird about it is that the Tilde in the "US International - PC" is at the same key position, but it does not work as a shortcut as it should.
(Edited)
Photo of Jeffrey Tranberry

Jeffrey Tranberry, Sr. Product Manager, Digital Imaging

  • 13977 Posts
  • 1671 Reply Likes
I've asked our localization expert to look into this to see if it's a bug or expected.
Photo of David

David, Official Rep

  • 2701 Posts
  • 361 Reply Likes
Howdy Gustavo,

Wow.  Sorry about that.  I'm not quite sure what went wrong, but you're correct -- the same key and character that work fine for US English and British English fail for International English.  Very odd.  For what it's worth, however, this is also happening with 10.11.6.  I've gone ahead and logged a bug against this issue, so we can further investigate and hopefully fix it.

Thanks again for the heads up and sorry for the trouble,
David