Wacom Intuos4 and Photoshop CS4

[keenox]

I can't get pen tilt working in Photoshop CS4. If I choose pen tilt option in brush shape for shape dynamics it works as if the control would be set to pen pressure sensitivity. Diagnostics in driver options show tilt is detected. Tilt only works for angle control in CS4. And I'm using the latest update for CS4. In spite of this, i tried my intuos4 in corel sketchpad and it works great, just as expected. It detects pressure, tilt angle and tilt direction. I don't know what could be the problem. Can someone confirm having tilt working in CS4?

I'd like to use tilt for roundness control.

[Guest]

I'm g-o-o-o-o-o-d!

[Guest]

So what are the lotto numbers for tomorrows drawing?

Bart Cross wrote:

I'm g-o-o-o-o-o-d!

[Guest]

Which one? The one I always lose at or the other one I always lose at?

[keenox]

Have you forgotten us for good?

[Ricky-T]

Well Chris wrote that it won't be a simple dot release, so it more than likely means CS5 will have it fixed (hopfully). Other than that, what else is there to say.... 😕

[keenox]

I don't think people paid for CS4 only to get fixes in CS5 for more money.

[Ricky-T]

Fair point and i agree with you, but unfortinatly it seems that that is exactly what is going to happen 😕 But who knows, maybe adobe will find a way around this for CS4. Fingers crossed!

[Philippe90]

Hi every body,

At the begining of the post it's very difficult to recreate the same default on your version (chris version and others) may be we can have this one. Wy some one haven't this probleme ? Have they the CS5 version?.. Ok for the problem, every one can do a mistake, but it seam very simple to correct it (but I m not programmer, I try for a long time to be a photographer) 

[Guest]

I don't have this problem in CS5 because CS5 is not out yet to have problems with.

[Guest]

Do you really think that they will correct this for CS5? They haven't bothered updating the code to make this work properly for years now.

Oh yeah, I forgot, it does work if you squint really hard and believe the engineers.

[Guest]

If I don't squint I can't read the monitor......

[Guest]

Glasses my man, glasses! Preferably with Scotch in them.

[Philippe90]

It's not what I said Dec9 ... Have you a CS4 version ? Have you this problem whit the Wacom pen  ?

[Guest]

You wrote have they the CS5 version thus my answer.

My Wacom is broken and I don't plan on buying another.

[anonmous]

Hello, is Adobe planning on addressing this issue (lack of pen tilt functionality)?  After reading through all of the posts, it appears that Adobe's position is that the problem is not a "simple dot release fix."  If it's not that, could it be a major dot fix release fix, i.e. not 11.0.2, but 11.1.0?  It would be nice to know whether Adobe plans on addressing this problem for the affected CS4 customers.

Thanks,

Matt

[Guest]

Another poster had issues on windows 7 with a bamboo pen & touch. He downloaded the 25 November 2009 driver package, wiped the old drivers off the computer and did a fresh install. This fixed his problem.

Did you try this driver set? Looks like the update is good for Windows 7, Vista and XP

http://www.wacom.com/downloads/drivers.php

[anonmous]

Hi, thanks for your reply.  Yes, I had already installed the most recent version (6.1.2-5) in the hopes it would fix the problem, but it appears per Adobe's admission that for those of us affected, it's a legitimate bug in Photoshop CS4 that Adobe needs to address, hopefully soon.  I'm just looking for some guidance from Adobe as to when they plan on handling it for us CS4 users.

Thanks,

Matt

[Guest]

Ya, I hear ya. This person had windows 7 so maybe it is better working with the API or something or another...... lol

[keenox]

Bart Cross wrote:

Yes, it is called CS5 and it will be out next year. Hope you don't mind waiting.

That's a good one.

[romgen]

I just wanted to add me to this thread since I also have that problem (only with CS4 though).

[Guest]

I'm glad you chimed in also.

Chris' original position was that all the users were nuts since it works for the engineers. Eventually he relented that it did not work as it should and that QE will try to solve the problem.

Although Chris' opinion was annoying (eg: all these users are stupid... (etc; insert what you want here), at least at some point user frustrations did get across because enough of us bitched about it.

While Adobe does montior these forums it does not have to, the people at Adobe have always monitored these forums (although they seem care less than before). I think that, as this thread shows, if enough users complain about an issue in one thread, they wil pay attention.

The point if marketing doesn't think a problem is important because the complaints don't go through proper channels. The engineers are aware of problems and would like to solve issues but marketing says do this or that because this is what we can sell. This about stocks and giving a good divide to shareholders (although this doesn't make any sense at all when you think about it).

The bottom line is Adobe is not quite the same company they used to be but do, begrudgingly listen to the customer base when it serves them.

Honestly, overall, I am happy with Adobe as a company, but it is not the same company I dealt with back in the mid-ninties.

[Chris Cox]

Although Chris' opinion was annoying (eg: all these users are stupid... (etc; insert what you want here), at least at some point user frustrations did get across because enough of us bitched about it.

No, Chris's observations (not opinion) were correct -- I did not see the problem when I tested it.

The problem was more complex than you (or I) realized.

I repeatedly asked for more info so we could reproduce it, and it took us a while to reproduce it.

I never said anything about anyone being stupid, or even being wrong -- just that we were not seeing it, and needed more information.

Quit reading things into my words that aren't there to start with.

We listen, but when you see something that we don't -- you're going to have to work with us to help us reproduce the problem.

And accusing us of crap because we don't see exactly what you see on your particular system, doesn't help.

[Guest]

Points not taken.

You can say what you want, but you did eventually see the problem, but did not bother to explain how you suddenly happened to see the problem at your end. You did not exactly call anyone stupid, but you continually insisted there a problem with our systems, not Adobe's. You have admitted that it not only a small problem but a really big coding problem.

If you want to continue to blatherskite on the issue, I am sure I can quote you contrarily.

You already admitted you screwed up, leave at that and I will.

Praise be to Painter.

[anonmous]

Chris Cox wrote:

The problem was more complex than you (or I) realized.

Hi Chris,

  Thanks for your attention to this.  Any update as to an ETA?  Will this be fixed for CS4 users?

Thanks,

Matt

[Ricky-T]

I think this topic should be closed and a message should be put at the top of the forum like it is when Adobe release questionares and such like, stating about the title problem and making it clear that it will or will not be fixed for CS4; as it stands, it looks more and more likely that it will not. Yes it is annoying that the problem will exist in CS4 forever by the looks of things, but everyone makes mistakes. I think this topic is getting a bit out of hand....