Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
13

P: Inaccurate selections with Radeon graphics cards on Mac OS

LEGEND ,
Aug 03, 2011 Aug 03, 2011

After installing Lion, selections with the Rectangular Marquee Tool generally are reduced by one pixel when the mouse button is released. For example, dragging a 25x25px square results in a 24x25px selection.

Bug Fixed
TOPICS
macOS
1.2K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines

correct answers 1 Correct answer

Adobe Employee , Oct 25, 2013 Oct 25, 2013
It appears this issue was solved by a fix to the drivers released with Mac OS X 10.8.3 or later. Let us know if you're using a version of OS X 10.8.3 or later and still seeing this issue.
Translate
replies 116 Replies 116
116 Comments
LEGEND ,
Nov 16, 2011 Nov 16, 2011
AMD Radeon HD 6490M 256 MB

I don't have access to my home machine. It's a couple years older so it's almost certainly a different card.
Translate
Report
LEGEND ,
Nov 16, 2011 Nov 16, 2011
Same here. Suspect it's the same issue.
Translate
Report
LEGEND ,
Nov 16, 2011 Nov 16, 2011
We've reproduced the problem in other applications. But it's likely that Photoshop is the only application you are using that uses the Cocoa APIs and OpenGL where you can see the offset.

We've been working with Apple on these issues for a couple of years, but new bugs keep getting introduced with each OS/driver update. And if we work around the bug, then the fix will result in an offset as well.
Translate
Report
LEGEND ,
Nov 16, 2011 Nov 16, 2011
First off.. Thanks for working on the problem. I've always applauded Adobe for usability and precision.

> the fix will result in an offset

Really? Surely you could use a conditional.
Translate
Report
Community Beginner ,
Nov 16, 2011 Nov 16, 2011
Chris-

Your assertion that I'm complaining about an Apple driver bug may very well be true, but is both flippant and unhelpful. Unfortunately, unlike JacksonC, THAT is what I have come to expect from Adobe recently.
Translate
Report
Community Beginner ,
Nov 16, 2011 Nov 16, 2011
Thanks, Michael. My Mac Pro has an NVIDIA GeForce GT 120 512 MB. My iMac is either the Radeon HD 5670 or 5750. (it's at home, so I'm not sure which.)
Translate
Report
LEGEND ,
Nov 16, 2011 Nov 16, 2011
Jackson - how can we have a conditional for a fix in a driver that hasn't been released yet and might get broken in yet another driver update?
Translate
Report
Community Beginner ,
Nov 16, 2011 Nov 16, 2011
At home now. My card at home is: NVIDIA GeForce 9600M GT 512 MB ...Same problem as on the Radeon.
Translate
Report
Community Beginner ,
Nov 16, 2011 Nov 16, 2011
I'm getting the feeling that Adobe support is not interested in making sure their customers are feeling positive about the communication they're getting. -Jackson
Translate
Report
LEGEND ,
Nov 16, 2011 Nov 16, 2011
What we're trying to do is solve the problem, and stop having people yell at us about problems that we didn't cause and can't do much to solve.
Translate
Report
Community Beginner ,
Nov 16, 2011 Nov 16, 2011
Yup. I was right. 🙂
Translate
Report
Community Beginner ,
Nov 16, 2011 Nov 16, 2011
Chris-

Let me suggest how you could have made the same point without sounding unprofessional.

"Thanks for keeping this thread going, folks. We are aware of this issue. We currently think that this problem it is related to a bug in an Apple graphics driver. We are doing all that we can and will update this thread as we know more. Some workarounds that have been suggested are (...)"
Translate
Report
Community Beginner ,
Nov 16, 2011 Nov 16, 2011
My home machine: ATI Radeon HD 5750 1024 MB
Translate
Report
Community Beginner ,
Nov 16, 2011 Nov 16, 2011
Thanks for that, Matthew. I'll pretend Chris wrote that response.

The purpose of this support forum is for customers to indicate that they are having problems using Photoshop to do their jobs. Whose "fault" it is should not matter.

I think we (the paying customers) have done a lot to help identify the issue. For that, we get a guilt trip that we shouldn't be complaining. Wow.

I know customer service can be a difficult job. But frustrations like that should not be put on the customers.
Translate
Report
Guest
Dec 01, 2011 Dec 01, 2011
Same here! Tremendously frustrating.

Eye Dropper tool, Shape tools, Marquee tools, and even sliders on panels (sometimes i drag opacity down to 0 and then look back and it's mysteriously at 1)

Usually when drawing shapes, I keep an eye on the info panel so that i can see the pixel dimensions. For example, I'll drag a rectangle out to 200x200 as shown in the info panel - and again, as soon as I release it shifts to 200x199 or something.

With the eyedropper tool and color selector window open, i can put the cursor in one spot & press the mouse button down - see the color update accurately, but as soon as i release, the color updates to one of the neighboring pixels. Without moving the mouse, i can reproduce this behavior over & over...
Translate
Report
Guest
Dec 09, 2011 Dec 09, 2011
Michael, Any updates on this?

here's my machine info:
Graphics NVIDIA GeForce 8800 GT 512 MB
Memory 10 GB 800 MHz DDR2 FB-DIMM
Mac OS X Lion 10.7.2 (11C74)

BTW, this is definitely not a marquee only issue. As I mention above the problem also occurs with the Shape Tool, Color Picker, and sliders.
Translate
Report
Dec 09, 2011 Dec 09, 2011
Hi Marshall,

Sorry, I don't have any more updates. Our developers are investigating the issue right now and they're aware that it's not just a marquee only issue, so hopefully they'll get to the bottom of this.
Translate
Report
LEGEND ,
Dec 09, 2011 Dec 09, 2011
The primary issues were with Radeon cards (AMD/ATI).

The graphics issues on 10.7 are different, though still caused by bugs in the video card drivers. We are continuing to work with Apple to get these bugs fixed in MacOS.
Translate
Report
Community Beginner ,
Dec 09, 2011 Dec 09, 2011
Michael-

Can you comment on Chris's comment above about this being primarily a Radeon issue? We are definitely seeing it on NVIDIA cards as well.
Translate
Report
LEGEND ,
Dec 09, 2011 Dec 09, 2011
Read what I wrote. You're on MacOS 10.7, which has a whole new set of video card driver bugs.
Translate
Report
Dec 09, 2011 Dec 09, 2011
For better or worse all graphics driver updates for Apple are installed through system updates. So if the bug is on Apple's side we have to wait for them to fix it instead of updates from individual GPU makers. Chris mentioned that it's been seen mostly with Radeon, and is a GPU-related bug, but the issue appears to be on the system level as it relates to GPU, so we're waiting on Apple.
Translate
Report
Community Beginner ,
Dec 09, 2011 Dec 09, 2011
Michael- I just needed a little clarification, so thanks.

Chris- Your attitude toward people who are taking the time to provide feedback about Adobe's products is insulting.
Translate
Report
LEGEND ,
Dec 09, 2011 Dec 09, 2011
You are reading things into my replies that simply do not exist. I'm giving you the facts - that is all.
Translate
Report
Guest
Dec 09, 2011 Dec 09, 2011
Thanks for taking the time to reply. I hope we can get this sorted out!

Shot in the dark here, but, I if there are any interim work arounds that you guys have come across or that might be worth trying, i'm happy to be the guinea pig. Just let me know.
Translate
Report
LEGEND ,
Jan 11, 2012 Jan 11, 2012
I have this same issue on Windows 7 running a Radeon HD 6800 card.

It's annoying, but Michael's suggestion above to make selections based on actual cursor position rather than the actual selection box/line/marching ants works like a charm.
Translate
Report