Photoshop: Please let us switch off the "bird's eye" feature

this could be a suggestion, but for now it's a problem that's driving me crazy : how do you turn off that damn "bird's eye view" option? It's activating when i hit the space bar at certain magnifications and jumps out and disorients me. it's so annoying it's not true. it may be a good tool when someone specifically requests to use it, but otherwise we should either have the option to disable it, or disable it for the Space bar only. Seriously, this "feature" makes me seethe, it totally ruins my productivity as i'm set working at a particular area/magnification then instead of being able to scroll w/ the Space bar as we always did, the view jumps out jarringly and sometimes seems to change the tool i'm working w/ too.

i've had a bit google and someone else mentioned it getting activated by Space too. if it's not supposed to work like that, i'd suggest it needs to be looked at as a bug, because it's definitely a glitch, and an annoying one at that.

it's annoying that i have to lose all the OpenGL stuff tho, if i want rid of one feature - is there no chance of an update to let us have checkboxes to select which features we want?

PS is up to date as far as i know, i had it open when i started this and it didn't announce any updates.

i've got a Wacom Graphire I. i have slight issues w/ this, in that Wacom don't do a Win 7 driver, so (as per their tech people) i got the Intuos driver, which works about 95% (the eraser doesn't come on when i turn the pen around, eg). Dunno if this could be a conflict, like i said others have mentioned it so w/out knowing their set-ups i dunno if there's a pattern.
TIA

Does this happen repeatedly or just every once and a while?
If you restart PS does it work correctly?
What happens if you uninstall the Wacom Driver? Does the problem still reproduce? (Be sure to unplug the wacom after you uninstall it.)

it does seem intermittent, but i haven't been keeping an exact log, i'm usually too busy swearing at it. Seems to work most often at 100% magnification when i try to scroll around.

i'm not messing w/ the Wacom drivers, i don't see that that's anything to do w/ the issue and since i use the Wacom to draw there's no point in seeing if things work w/out it. Like i said, i'm not the only one who's reported this, so to my mind the problem is in PS itself.

Here's a way to reproduce this glitch: while zoomed, hold down ANY tool shortcut you're not currently using (i.e. hold B while you have Clone Stamp selected) and, at the same time, try to use the spacebar pan. There's your bug.

As I understand it, the birds eye zoom should only be activated by H, but it's getting activated by any combination of shortcuts and spacebar.
This is surely a bug and it's still present in CS6.

Please...any comment - has anyone found a way or hacked a solution to this????

- Im at the point of considering other software this is so annoying.

A simple checkbox in preferences like the "enable flick panning" would just totally solve this problem! And in any case, a feature like the "birds eye view" is such a dramatic change, a much bigger one than "enable flick panning" that I just don ́t understand why adobe would not let users select to turn this off.

Another way to "leak" the bird's eye view to space bar (a variation of Vinícius Rezende Paceka's method) :

while holding down ANY tool shortcut you're not currently using (i.e. hold B while you have Clone Stamp selected) and, at the same time press Alt. Release the tool's shortcut. While holding Alt, press and hold the spacebar. Release Alt. Try to use the spacebar pan. There's your other bug.

This method not only triggers the bird's eye view but now holding down just the spacebar+dragging behaves like holding down H+dragging.

At first we thought it was a feature but now knowing it's a bug that is around since CS4 is annoying. It punishes fast interactions immensely.

When I first started to describe this problem that is excactly the view I got from adobe. - They just could not reproduce the bug..... I finally recorded a video of the way this happens, I posted the video to the person at Adobe who was trying to help....and after the video I got no response, nothin

Another vote for some way to disable this feature please. I seem to end up stuck in birds eye view when using the hand tool for some unknown reason within a couple of minutes of starting to use Photoshop (latest CC version). After switching to a different tool and back to the hand it'll then clear up for the rest of that session. Restarting Photoshop I'll get it again.

Max zoom then select couple of pixels with the "M" tool. And here it comes - press "Z" then ALT then double click (to zoom out two levels) release ALT and press SPACEBAR and drag = birds eye every time. The tricky part is that you have to do it FAST - really fast else it won't happen. It's like if you're fast they slow you down to make it harder!

My workflow intention is this - zoom to pixel level select couple of pixels to measure them then zoom out little and drag to other region, zoom in and measure again. This can't happen because bird's eye bug happens every time and it drives me nuts because at high zoom levels I loose my location and have to look for it every time. I have to switch my ZOOMing style because of this :/

Every time this happens to me I just lament over all of the time that has been wasted finding my spot again and figuring out what tool I was trying to use. The normal solution would be to wait for a fix, but... Seeing as CS6 hasn't been updated for over a year, there isn't much hope there. I'm glad to see that the bug has been reopened, but I'm not holding my breath.

Adobe: Please fix this super annoying bug. I bought CS6 a couple years ago and am opposed to the subscription model. I will never ever subscribe. I will however consider buying later versions outright.

I bet there are a lot of people like me who feel the subscription model is, well, deplorable, who would rather learn a new tool than succumb to a tactic to cynically extract dollars. Many of them probably also proactively bought the last 'own-able' version for reasons of accrued value they would earn over the years, as opposed to the subscription model. what your econ folks may not understand is that, in spite of short-term gains, you are creating a massive amount of vitriol

This neglect for a bug that has been present for years, across multiple versions, demonstrates a lack of regard for your user experience and sows ill will. Why in world would I give adobe more money knowing full well that you don't adequately support your products? More garbage like content aware fill? vanishing point? Laughable.

I feel passionate anger towards Adobe. Bugs like this linger for years and years and years. I will continue to use cs6 for the rest of my days because quite simply it's good enough to earn a living, but unless Adobe takes measures to regain my trust - i.e. fixing old, lingering bugs like this retroactively. I can never trust you guys.

You guys should be afraid... there is a looming problem when a $5 ipad app (procreate) DESTROYS Photoshop in terms of support, usability, stability. and there are a wide array of products that are approaching Photoshop's feature-set, both free and paid.

I replied with a helpful AutoHotkey script that helps the problem, but they deleted my post. I totally feel you, but They'll probably silence you the same way they did me. If only there was another program to compare with photoshop. I also refuse to pay a subscription fee for a program. It makes sense for somebody who uses it professionally, but as a hobby that makes no money back, paying hundreds of dollars a year just isn't viable.

I replied with a helpful AutoHotkey script that helps the problem, but they deleted my post. I totally feel you, but They'll probably silence you the same way they did me. If only there was another program to compare with photoshop. I also refuse to pay a subscription fee for a program. It makes sense for somebody who uses it professionally, but as a hobby that makes no money back, paying hundreds of dollars a year just isn't viable.