Just had the update to CS5 today and since then my Intuos3 isn't recognized anymore by PS. (the yellow triangle with ! saying a tablet is needed for pressure sensitivity ).
Updated my catalyst drivers
Reinstalled my wacom drivers
Works fine in Corel Painter
And I do have a separate setup for PS in my Wacom properties panel.
Isn't this the issue with the new PS update enforcing the DLL security policy that DLLs cannot be loaded from the PATH, anymore, and so the workaround that sometimes works is to copy the drier DLLs into the PS directory?
sorry ssprengel, what DLLs do you mean? and where should I find them? Please elaborate?
edit: Chris, thanks but if the driver wasn't working well, it wouldn't work in Painter.
Anyway I reinstalled them over and over again but it doesn't work in 64bit, only in 32bit mode.
i updated photoshop 32 and 64, still same prob
only 32 works
drivers work correctly
(btw to check for sure if they work correct, go to option panel of your tablet, for example mine is bamboo, so i go to bamboo preferences,
and then hold ctrl and click on about
a window with a lot of info wil appear, and look at pen pressure, it shoul be 0, and when you press on your hardest it should be 511, if press soft, it should be in between, if this is not the case, wrong drivers or broken tablet/pen)
but since it works in painter for you, chances are slim
I solved the problem!
Here's how I did it:
Hope this works for you guys too
Apparently, the problem comes back when the pc is used after someone has logged onto my Win7 64bit with a different account, but only when I start CS5 with the mouse.
When I start it with the stylus, I have pen pressure sensitivity.
This was after I copied the Wacom_Tablet.dll in my PS directories.
So starting the app with the stylus solves it.
Also, use the stylus to open the brush dialog.
It seems that if PS detects a mouse is being used, it automatically assumes no pen is installed or being used.
It seems that if PS detects a mouse is being used, it automatically assumes no pen is installed or being used
Nope, doesn't work that way.
You probably need to follow up with Wacom - this sounds like another driver conflict/issue.