Skip to main content
Inspiring
November 17, 2020

P: No red preview when changing brush size

  • November 17, 2020
  • 319 replies
  • 17152 views

I've just downloaded the new photoshop update (22.01) and I noticed there is no classic red area when you change Brush size and feathering (when using keyboard shortcut OPTION+CONTROL). 

 

it is quite frustrating

This topic has been closed for replies.

319 replies

Known Participant
December 8, 2020

Same problem for me.  The red preview doesn't work for v.22.0.1 and v.22.1  I had to go back to version 22.0

It's very frustrating...

Camagna
Known Participant
December 8, 2020

22.1 is out and same bug. MacOS, latest Catalina. Horrible bug. A real showstopper.

Participating Frequently
December 8, 2020

@ouioui_photo  idem sur mac Catalina. Bug du pinceau non résolu. Par contre, on retrouve la roue de sélection des couleurs.

ouiouiphoto
Known Participant
December 8, 2020

W10 PS 22.1 not fixed 

.Sheepdog trying to help Lightroom and Photoshop beginners
Inspiring
December 8, 2020

hey adobe, was ist mit euch? heute kommt ein update, alle schreien schon, dass die pinselvorschau nicht funkt und schon wieder sieht man keine farbe. das kann doch nicht soooooo schwer sein den bug zu fixen!?!?

Inspiring
December 8, 2020

@JeffreyTranberry  Just updated to the new version 22.1.0 on Windows and the bug is still there! It's really frustrating and I'm planning to roll back to the CC2020...

carminecuccuru
Participating Frequently
December 8, 2020

@JeffreyTranberry in new update Ps have still problem, red overlay, lag and more. This is a problem for my workflow...almost one month.

Thank you

Inspiring
December 8, 2020

Photoshop 22.1 update:

No red preview when changing brush size...!!!

Inspiring
December 8, 2020

No mention of this bug being fixed in 21.1 update release notes? is this bug that effectively makes the latest PS version unusable just being ignored then?

Inspiring
December 8, 2020

An update and this very obvious issue that seems to affect nearly everybody has not been fixed? I could not believe it - but it is true ... not fixed on 22.1 (Windows)

Why has the update not been delayed until this got fixed?