CS5 Bug - Moving layers

In the past two weeks I've noticed a weird problem with my Photoshop CS5. I'm on Windows 7 64-bit with CS5 version 12.0.4 X64.
Sometimes (not always) when I click a layer in the layer menu and try to move it with the move tool, it jumps to a different layer (not to the one I selected) and moves that one instead. Now, this is only if I move it with my mouse. If I move it with the keyboard, it works fine.
Also, if it starts doing this with a layer, it will continue to do it with that layer forevermore. Even when I close the program and re-open it again. Or if I save it as a diffeent filename. If I duplicate the layer, it will do it on both the original layer I was having trouble with and the new copy of that layer. I can also merge it down with a blank layer and it'll retain the problem in the new, merged layer.
Any advice? It's annoying to have to move the affected layers with the arrow key.
I did find a mention of this problem on a mac, but the solution did not seem to apply to a PC.

I might have years ago. Not the most recent. Certainly not the most pressing issue
This post just reminded me that "Auto-Select" might confuse some people with its terminology.
I remember a Photoshopworld a while back where J. Kost was admonishing "You target a layer. Select is something different."
Next time round.

Similar Messages

Photoshop CS5 bug - shape layers icons disappear

So I'm having this normal PSD when suddenly all the shape layer icons disappear and nothing seems to work to get them back. (I've tried restarting photoshop, computer, open the PSD from another PC) They work like they are there, double click and all that but just the icons are missing. It's not the first time happening and I noticed it happens after the layers get's a lot. Anyone has a fix for that?

If you click on the fly-out menu icon at the upper-right of the Layers panel, then choose Panel Options, then choose a different sized icon, do they reappear?
Only other thing that comes to mind is to update your display driver by visiting the web site of the manufacturer of your video card (e.g., nVidia.com or ATI.com) and locating the driver package that matches your hardware and operating system.
Can you make a small PSD file (e.g., by cropping your master file quite a bit) and post it online? Others could try opening it and seeing if the icons are there.
-Noel

Major CS5 bug where Smart Objets get thin horizontal lines??

Our prepress company has come across and proven out a rendering bug in Photoshop CS5 for Mac. It has caused us to consider totally avoiding CS5 until it's fixed. We are finding that CS5 is putting in several randomly generated thin horizontal lines about a pixel in height and varying widths, in cases where CS4 does not. Some files get these lines when converting live "smart objects" from one ICC colorspace to another.
I am providing a link to a specific file that shows proof of this bug. The example file has an embedded sRGB profile. To see the bug, set you working RGB colorpsace to AdobeRGB, and set your Policies to "Ask". During opening, USe the embedded profile. Then convert it to the AdobeRGB 1998 colorspace using File Convert, and do not rasterize the smart objects. You will see lines in the lower right hand corner after it's converted. Now go back and rasterize the smart object layers first, and these lines will not show up. And now do the same with CS4, without rasterizing the smart objects and you will not get lines. CS5 bug, CS4 no bug.
Let me know what you find on your end. Can any of the adobe employees document this for me and get it on the fix list?
Test file:
http://www.mediafire.com/?ant3ya9aaft1a95

I also head a Graphics/Prepress department at a medium format digital print shop, with next day service to the casino industry. My two cents worth, CS4 did not have this issue, CS 4 was a Cocoa app and CS5 a Carbon app, to me that is not a reason why a major software company like Adobe has multiple leading products (PS, ID, Ill) that cause these kind of problems. I can't count the times my print opp's have come back with a file showing lines. Now, I have told my designers that we should also be looking for the lines, now that we know about it.
I have printed fabric before and it is a pain to print one and see if there are lines in it, but which is more painful, printing one to test? Or trashing $3k worth of fabric? I know this works for one image printed x times, but multiple images printing a couple each to fulfill the job would be a huge ordeal. Adobe doesn't understand that yet. The squeaky wheel gets the grease, maybe we should all start calling tech support daily.
I saw a post suggesting rasterize pdf's in lower PS to work around, clearly an ad agency/freelance solution, not a production house solution. Opening and closing PS12 and PS11 somewhere around 15 to 20 times, per work station? We process somewhere around 40 minimum pieces of art a day, and sometimes double that. I could rant on this suggestion all day.
The bottom line is Adobe has no clue where it is coming from, they are more worried about the iPad/mobile industry right now.

CS6 dead slow moving layers and groups

I have this brand new PC, got it last week, i7 core, SSD drive, 16gb ram.
When I open my PSD doc with my design (approx 43mb psd file) then the photoshop application spikes in memory usage, to 3.5gb (from 120mb), and moving groups and layers around is DEAD SLOW, horrible lag.
I had CS3 on my previous PC, which was Core2 Duo with 4gb ram, and the speeds there were similar on the same psd document.
I've also tried CS5.1 on a similar PC hardware specs as my new PC, and moving groups and layers around is much faster.
Is it just CS6? Why is this so slow?

Wow, that was kind of an over the top response...
Many of the files I'm using were made in CS4 and didn't have this problem. I updated to CS6 about a month ago. The same files, that worked perfectly in CS4 are having this issue in CS6. It's not about the files - it's about CS6.
Maybe I worded my post wrong. The point I was trying to make is - something is wrong in SC6 Photoshop that's not unique to me or my files. A lot of other people I know complain of the same thing.
I was trying to highlight that this is an unaccepatble issue for software at this cost. And that it's a really, really big deal. What is more fundamental than moving layers?
From the volume of posts I see and the lack of an actual solution, my assumption is that there is not one and that this is a program flaw. I hope Adobe can adress this in an update soon.
If that is wrong and there is a true "solve", please advise.
On a side note. I'm an Creative Director doing web based work. The files are 72dpi. And this issue occurs when dragging / moving simple layers. They are not huge files or items that require substantial redraw.
RAM 15,214 - Photoshop allocated 10,497
History states: 50
Cache levels: 2
Cache tile size: 128
All other preferences are default.
Changing the settings above or alterting graphics processor usage or settings and no noticable affect.

Problems moving layers

I've been an Elements user for 10 years, using PE12 since June. I just recently had a problem moving layers both within and between files. When working on a file if I try to drag and drop a layer it just snaps back to where it was. I can move the layers with the arrow keys but this takes entirely to long. I don't understand why this just now started happening. I can open my previous version, PE 6 and move layers as I always did but since I paid to upgrade to PE12 it would be nice to be able to use it. Any input on how to resolve this would be greatly appreciated! Thanks in advance, Kirsten

Mac user with Yosemite? If so, see:
Photoshop Elements doesn't respond when you use editing tools in Mac OS X 10.10

Moving layers and adjusting perspective

Hi there,
I am wondering if it is possible to move each layer to that
they do not overlap. I also want to be able to move the layer in 3D
like in after effects. the reason is I want to have each layer
represent each face of a 3D cube.
For instance. A cube as 3 visible faces so there are 3
layers. Is it possible to move layers around like that and adjust
their perspective?

Wow, that was kind of an over the top response...
Many of the files I'm using were made in CS4 and didn't have this problem. I updated to CS6 about a month ago. The same files, that worked perfectly in CS4 are having this issue in CS6. It's not about the files - it's about CS6.
Maybe I worded my post wrong. The point I was trying to make is - something is wrong in SC6 Photoshop that's not unique to me or my files. A lot of other people I know complain of the same thing.
I was trying to highlight that this is an unaccepatble issue for software at this cost. And that it's a really, really big deal. What is more fundamental than moving layers?
From the volume of posts I see and the lack of an actual solution, my assumption is that there is not one and that this is a program flaw. I hope Adobe can adress this in an update soon.
If that is wrong and there is a true "solve", please advise.
On a side note. I'm an Creative Director doing web based work. The files are 72dpi. And this issue occurs when dragging / moving simple layers. They are not huge files or items that require substantial redraw.
RAM 15,214 - Photoshop allocated 10,497
History states: 50
Cache levels: 2
Cache tile size: 128
All other preferences are default.
Changing the settings above or alterting graphics processor usage or settings and no noticable affect.

Photoshop CC lagging - moving layers, video

Here is my problem:
https://www.youtube.com/watch?v=bCMbASsil7Y
Any solutions?
I need help with lagging. Moving layers with move tool (time: 1:26). Any solutions?
PSD only 40MB.
Not helped:
- Task manager process to High
- Switch off integrated video card
- Switch off GPU performance
- Drivers are actually
My PC:
i7 4790K @ 4.4Ghz
Nvidia GeForce MSI 980 Gaming 4G
2x8 GB RAM 1600 DDR3
SSD 256 GB
Windows 8.1
Adobe Photoshop CC

Any solutions?

Photoshop CS3 crashes a lot when moving layers - Help.

Using:
MAC OS 10.5.4
Photoshop 10.0.1
MacBook Pro, 2.5 GHz Intel Core 2 Duo, 4 GB 668 MHz DDR2 SDRAM
My crashes are very specific. When I move a layer around in the layers palette, Photoshop will crash. It doesn't always crash when moving layers, but it does happen a lot!
Anyone have the same problem? Any solutions?
Thanks so much.
John

How much space do you have on your scratch disk?

Moving layers with respect to one another

I'm trying to trace a new map using parts of two maps. I can trace the parts I want of one map, imported as a template, but now I want to import the other map as a template, and reposition my tracing over the second template. When I import the second template, it's in the wrong place (as expected), but I can't move my tracing layer to a different place over the new template -- both layers move together. Is there a way of moving layers independently?

Open both of your tracing images in phohtosp. Copy the new tempalte image adn paste that on top of the original template. Set the blending mode to multiply , and then transform to repositon. Set the belnding mode back to normal, turn visibility off for original layer if needed, save. Go to illustrator, if you were linked Illustrator should ask you to update image.

Moving Layers Problem CS5

I'm having issues moving individual layers once they've been put into a group in CS5. It just moves everything in the group! Very inconvenient. This hasn't happened to me before or in CS6. Can anyone offer any recommendations on how to correct this?

Nevermind, I had the pointer tool set to group. Yay for problem solving.

BUG REPORT: Layers with 100% height in timeline knock bottommost layer(s) out of scrollable area

I have tried to post this twice to the official bug report page, but (somewhat hilariously) the bug report page bounces it back with an internal error about an unknown email address, so I'm posting here too just in case. As I have no idea how to report a bug about the bug report page, I decided I might as well just post the bug here.
CS5.5/Windows 7 - Verified on 6 different machines, some 64 bit, some 32 bit
If I have a layer in the timeline that has been expanded to 200% or 300% (via Layer Properties) height, the bottom-most layers gets pushed outside of the viewable area. The scrollbars simply don't scroll that far. I double-checked and this is new since CS4--which still works correctly--so never let it be said that the engineers aren't working on the code! :-/
Basically, I use this for audio layers, as it is nice to expand them to 200% so it's easier to see the waveform and guess where certain words are ending, etc when doing timeline syncing.
It can be worked around by expanding the timeline to be tall enough to bring everything into view, so I suspect the bug lies in the scrollable area calculation. However, since space is at a premium, usually I only have about 5-6 layers worth of space allocated to the timeline panel, so this bug hits me quite frequently (since I have all my old projects set up with 200% audio tracks).

sam wrote:
I have the same soundcard (or at least the same modules loaded) and I'm getting good volume.
Things to check:
If you have the pcm and main volume all the way up in alsa mixer that should be it. You may have to adjust the volume separately if you use esd, arts, pulse, or jack (I don't use them).
Another thing to test is to make sure your using alsa not oss, and you may want to raise the oss level and see what happens.
The final thing is you want to check to see which sound device the audio programs are using (usually found in the preferences).
If none of that works, then you're out of luck. It would help if you post what sound programs you are using and what sound daemons you are using.
Here is my Daemons line from /etc/rc.conf
DAEMONS=(@syslog-ng @network @netfs @crond @alsa @hal @fam)
So i would think im using alsa not oss. but how would i go about raising the oss to make sure? there is no "oss" option in alsamixer. I have tried just abuot every audio progream there is and even firefox, all of them produce about half of the maximum volume level.

Moving layers into Group

I am a web designer and have created a script that puts a browser UI around a Photoshop document. The action places several images and creates several text layers. What I want to do is place all the images then add them into a group called "BROWSER". I can do this and it works fine in CS3, but it fails to select all the layers in CS4 and CS5.
I have tried several methods which all work in CS3, but not 4 and 5. I have selected the top layer, held shift and selected the bottom layer "Add Continuous", I have selected them individually with the "Add" modification (holding down the command). After I create the selection, I try and "Make Group from layers", however, in CS4 and 5 it only places the last layer in the folder.
I have also tried creating the Group folder, naming it and moving the individual layers into the folder. The problem here is that when moving, PS uses the layer number instead of the layer name! For instance, I have a layer call "Page Title", when using the move command it uses it's raw layer number "layer 16" or whatever.
So sorry for the wall of text. Can anyone offer any insight? I am downloading the trial of CS5 to see if that makes a difference.

Are all the layers visible?? I just tried recording an action in CS5 and had no problem. I create a new document white background layer and added 6 layers. I targeted the middle layer and then recorded this action
Alt+, (Target bottom visible layer in this case the background)
Alt+] (Target next visible layer up in the stack in this Layer 1)
Shift+Alt+. (Select continuously up the stack to the upper most visible layer 6 layers with there visibility off between will also be selected)
menu Layers>New>Group From Layers (Create new group named it test and the layers were collapsed into the new group named test)
stopped recording
I then went back into the history palette to before the group was created where I had the 7 layers. I played the action and it worked. Went back in time again and added layers till I had 100 layers on top of the background layers. I turned the visibility of some layers off. As long as the background layer and the layer above it as well as the Top layer visibility was on the action worked. All bets are off it the visibility of any or those three layers are off. The Action will fail.

Problem with hidden objects when moving layers, groups or artboards

Hi there,
I am using Illustrator CS5.5 on a Mac.
Sometimes, after moving stuff around (groups, layers or artboards), I notice that hidden objects didn't move with everything else.
Does somebody knows how this can be if no objects are locked ?
I cannot make this happen on purpose with a simple example and it is really annoying not to be sure that everything was moved properly.
Thanks
R.

Emil,
A little misunderstanding here.
Like you say, clicking on the target to select (targeting objects) : this is exactly what I do.
So, SOMETIMES, when I select a group (not a layer) which contains hidden objects by clicking on its target in the layers panel, only the visible objects get selected (i.e. : only the visible objects get a full square at their right in the layers palette and the group gets a small square) AND the group is NOT targeted at all (i.e. : the target of the group is not highlighted, only the targets of the selected (visible) objects within the group are highlighted).
Then, if I move the group, only the visible objects are moved because only those are selected.
Problem is that I don't know why but when doing this (targeting objects), SOMETIMES this result in selecting everything within the group BUT SOMETIMES it result in selecting only the visible objects withtin the group.
I don't know what triggers that difference in behavior.
R.

Layers problem in PS cs5 extended, all layers change at once, including background layer.

layers problem in PS cs5 extended, when working in a layer, all layers changes at once i.e size, cropping, smart object etc. even the background layer changes...it is really annoying, please help, My system windows 7 64 bit 4gb ram. It is not grouped, deleted preferences, usually work in rgb/ 8 bit channel - have same problem with all new projects.

Hi
Problem with layers is when I use the crop tool in a layer out of 20, all of them get croped at once including a locked backgound layer.
When I use smart object in a layer to size down image with transform tool, guess what happens to all the layers in project? all behave odd, changes same as the layer being sized down. If I work images or layers in separate files, once I bring them over to my workspace, all get affected without maintaining their own individuality. This happens with every new project. I think colors are not affecting layers. Layers are not grouped, I do not know anything about linking layers. This problem is stopping me from using photoshop. Please help!!!
I had previously a problem with a photoshop bug (GPU sniffer), which I was able to resolve it with reintalling the graphics video card with the help of HP technical support, I am able now to work with repousse however with same video card.
Let me know if you need me to give you more details.
thanks,

CS5: Bug with Photoshop documents?

I frequently use layered Photoshop docs in Premiere, without much incident. I'll use them both flattened and as individual layers; if I need to make a change, I use Ctrl+E to open the image in PS, edit it, save, and it updates in the Premiere timeline. At least, that's how it worked in CS4, though I'd ocassionally and inexplicably have to Alt+Tab back and forth between PS and PPro once or twice in order to make the update "take."
Well, with CS5, it seems to be worse. After updating a PSD and returning to PPro, there is no visible change to the image in the Program Monitor. However, if I scrub or playback the sequence, the changes suddenly appear. Once I stop either activity, the original, non-edited version reappears. No amount of Alt+Tabbing seems to make the changes stick. I've found that if I sometimes open a different sequence, the image finally updates in "pause mode" but it's sort of hit-or-miss, too.
I seem to be noticing this more with PSD imported as individual layers, but I don't think it's specific to that particular import method. Anyone witnessing the same?
I am running a GTX 480 with the hack in place, and (apparently) the not-so-good current version of the nVidia drivers. Might this be a cause? I'll test out on my non-MPE workstation to see if there's a difference.

I had imported as merged.
I've tried again with the 8-layer image taking the following steps based on
your workflow:
1. Import PSD into PPro project as sequence.
2. Open sequence timeline and view output in Program Monitor.
3. Open PSD in PhotoShop.
4. Turn off 4 layers to give obvious visual effect.
5. Save from PS.
5. See no change at all on Premiere timeline.
This is exactly as I would expect because there is no link between PPro and
PS when edits are done externally like this. The footage would need to be
re-imported or the project re-opened to register the changes.
I also tried:
1. Select one layer in clip window.
2. Invoke Edit Original.
3. Turn on/off some layers to give obvious visual effect on image.
4. Save from PS.
5. No effect back in PPro even after re-rendering.
6. Deleting render files still did not force an update.
This is not what I was expecting and is, I think, worth reporting as a
potential bug.
NOT A GOOD ANSWER !
Because I don't often use import as sequence, I failed to realise that all layers are selected on by default in PPro, so turning off layers in PhotoShop doesn't give a useful test of this possible bug. Please ignore the above results, which I've only left up because some read this via newsgroups.
Out of time now. I'll do a better test on Thursday.
Message was edited by: akribie

CS5 Bug - Moving layers

Similar Messages

Maybe you are looking for