I tried to duplicate this and failed.
I put the bit depth up to 32 bit.
I locked one of the layers.
I included a vector layer.
I included a layer that was turned off.
In every case, I was still able to select Auto Align or Auto Blend.
Can you upload a screen shot of your workspace? Just paste it from the clipboard. Show the layers panel.
I can't see anything wrong with your screen shot, other than it is a quite a big document
From its pixel size and zoom ratio, it is a bit over 6000 pixels wide, and judging by the layers panel scroll bar, has about 20 layers.
Are you trying to align 20 odd layers of about that size?
I've tried to duplicate this, and I can still auto align
I am wondering if the layers being named as Nikon RAW files is significant? What is hiding behind your Edit menu drop down?
Tell us a bit about the layers?
This is a known issue with opening image from Lightroom, workaround is to open Photoshop first
Thanks - opening PS before transfering from Lr did the trick.
Come on Adobe, I do this for a living, you just cut my hourly wage in half. I am building photo stacks of 25 or more layers, now you want me to open each one in Photoshop first? What’s next, I have to wear a blue shirt for the software to work?
You can’t do upgrades that make us less efficient. That has to be the opening line in software management 101.
No, you misunderstand. You just need to have Photoshop open first, before opening Lightroom. Then everything works as you're used to.
Or disable the home screen.
Thanks! I ended up downloading Zerene Stacker, Ps was making mush of the stack once I got it in anyway. So far the third party program is much more forgiving, and I’m on deadline.
I have the same issue in Windows. Opening images from Lightroom as layers most of the menu items in Photoshop are greyed out. If you open the same images directley from Photoshop everything works normally. It seems like this is an integration issue with Lightroom and Photoshop. This only started happening with the last software update. Interestingly this same issue does not happen on the Mac.
As Ged says, known issue.
A bug fix is in the pipeline.
Why has this bug not been fixed yet? It's been two years...