Okay, this is weird.
I have a type layer with some text in it (a headline, let's say). I click on the layer, I click on the Character Panel, and first thing I see is the color in the Panel is not the color of the font in the layer.
I then click on any Panel property, and the text in this layer is replaced by text from another layer in my document ( a paragraph layer, let's say), but the color is not the same as the layer the text came from.
Seems like a glitch, but I don't know how else to diagnose it.
- Having the same problems, Looks like there might have been the same problems or similar in the "Beta Version of CS6" and the problem has been carried over to the Release Version.
- Certainly makes it very hard to work / productivity goes out the window
- Just like the Beta once it appears in CS6 and you try opening it in CS5 it carries the problem across
Using - CS6 Extended (Mac)
- Can someone give us an idea (ball park) of when this might be rectified (e.g. it might not be until our next dot release) or are we better of using CS5 if we are plannig using text layers in photoshop
I have the same problem with Photoshop CS6 Creative Cloud on Win7 x64. I also discovered that the broken text layers that are somehow cross-linked to each other will break if I resize the document the same as when I try to edit them and they become text from another text layer. Also, the font size properties are misreported for the affected type layers.
Here's an image pair that demonstrates the text layer behavior:
When I click on the text layers in the design above, or resized the image, this is how the text jumps around:
I've made duplicates of the text layers and moved the text that's jumped layers to the correct positions. Now I'm going to edit the file using CS5 since I don't trust CS6 not to mess the file up again as I edit it. This is not a bug I can live with, and it's not comforting to find out that it was documented in Beta and it was allowed to go out like this.
We haven't figured out how the files get into that corrupt state. The damage was done long before you see the problems.
But the text team is working on it.
And the shadow looks like a V tail single engine with it's gear down, shot from below. (angles aren't right for a shadow, or a standard tail)
It's a Bonanza V, the shape is a path made from a top-down view of the airplane not a shot from below. The image isn't gear down, that's a blip in the corn field rows but I should remove that detail since it does look like landing gear at low res.
At dawn, the shadow wouldn't really make it to the ground in a recognizable shape, so I may have to invoke the "suspension of accuracy" privelege granted by Artistic License™. But I'll play with making a mask from a top-down front view of the aircraft and then placing it into the scene with perspective. Pilots can be a pretty retentive group as you may know ;-)
I don't really grasp how the text layers could be corrupted "long before" the problems became apparent. But I have seen many instances in various versions of Photoshop where type size is misreported in layers, and that seems to track with scaling a document. Since absolute type sizes change when the glitch is manifest, perhaps there's a link between this problem and document resizing (or perhaps type layer scaling). This illustration started out as a low res comp and I resized the document to a much larger pixel area file to work. Anyway, if I wanted to try to replicate the issue, I'd build a document with text layers and resize the document.
Sounds very much like a problem first reported during the public beta:
Chris' "long before" comment implies the corruption is saved in the PSD file from a prior edit (which could have been only minutes before, but minutes are "long" for computer geeks like me and Chris).
By the way, one interesting thing I see that prompts a question: Up to now I had thought that the problem had been reported only by people saving PSD files from Macs, yet I see in the screen grabs shown that D.Estabrook is on a PC... Was a Mac ever involved in editing that PSD file, D.Estabrook?
My file has only been edited on my workstation (I'm on Win7 x64 as noted above). One other factor that may relate the two platforms: Suitcase Fusion font manager. Perhaps something related to font activation for Adobe Suite applications? I run Suitcase Fusion 4 and the cartoon fonts were in temporary status, which I later set to permanent status.
I don't think so before the text layer problem cropped up. I'm editing the file now in CS5, but I've been working almost exclusively with PS CS6 since I installed the public preview. I can't be certain, however.
The Suitcase Fusion update says that PS CS6 doesn't allow automatic font activation - as opposed to the rest of the Suite. The update claims CS6 compatibility with this update, with PS CS6 auto font activation in a future revision.
>> Pilots can be a pretty retentive group as you may know.
I know that far too well. (and I haven't been to Oshkosh or Fond du Lac in 20 years, back when my grandfather was judging and hanging with the IAC folks).
Yes, Suitcase could be partly responsible -- we'll have to test that and check with other users experiencing this problem.
When you said you're "editing the file now in CS5", are you saying you took a file that was failing in CS6, and opened it in CS5 and not seeing the problem?
With regard to resizing (and related to the question I just asked), let me comment a bit on what people are seeing.
When you open a PSD with text layers, the file contains rasterized versions of the text layers, and that's what you see; you're not seeing the "actual" text, you're seeing a raster image of the text. Until something triggers a re-rasterization of a text layer, that will remain unchanged.
When you click the text to edit a text layer, or you resize the document, the text layer must be re-rasterized, and that's when the bogus text will appear. In all liklihood, the text within the text layer was corrupt in the file when you opened it, but you don't see it until you perform some action that triggers a redraw. This is why Chris commented that the corruption probably occured long before you actually see the problem.
We are working to identify the cause of this problem, but at this point we cannot reproduce the steps that cause it, or know when it happens, so the more information you can provide us, the better. We apologize for this, and do want to get this resolved as quickly as possible.
I made a duplicate file to work on in CS5 and saved the failing one in case Adobe Support wanted a copy.
The corrupted file exhibits the same buggy behavior in CS5.
To be able to work on the file, I went ahead and started editing each text layer, then I moved them around and resized them per the original layout. I haven't experienced this problem except via CS6, so I'm doing the production work in CS5 in hope that I can finish it up without a recurrence of the problem.
I have earlier versions of the illustration. One has three text layers that are still behaving (58 MB). Another earlier version with six text layers (71 MB) exhibits the problem, but this file triggers this message when I open it:
If I click No, the layers look okay but they do the musical chair thing on a per-layer basis if I edit a layer. If I click Update, the file opens with all the text jumped to the next layer's location coordinates and relative font size.
The most recent (71 MB) file with the broken layer behavior doesn't trigger the above message. It opens with the text looking fine, but editing the layer shows the cross-linked layer text problem. Perhaps that message is supressed because I clicked no and resaved the file? I don't know for certain if I did that, just a guess.
I can provide any or all of the above files, let me know how you like large files delivered.
And for any of the files with the latent cross-linked layer problem, resizing the image causes the same changes to all the layers as editing them individually will.
PS: I can rasterize the layers with latent cross-link behavior and they rasterize as displayed.
Again, we need the good (before opening in CS6) and after (corrupts when changed) files.
You can mail them to ccox (at) adobe (dot) com and I'll forward them to the type engineers.
If they're too big to email, contact me and we'll work something out.
I'm pretty sure that my files don't have a snapshot of the magic moment. In spare moments I'm trying to capture the moment in amber, building a new file with text layers, doing what I do, and saving a new file each time I do something. No luck sighting the Textsquatch yet.
I’m experiencing this issue as well and it’s turned into a freelancer’s nightmare. I’m a consultant, and this has now corrupted at least four very important PSD source files for two different client projects.
The first project involved three very large (in file size) heavily layered files. Photoshop seemed pretty slow to save, and the next morning my colleague and I both experienced the same messed up type layer behavior - when attempting to edit a type layer resulted in the text completely changing, to something from another text layer, and also changing font size and color. I figured it might be my system, or that the files were so large something went awry.
Then I started working on a different project, with a much more modest (in file size) iOS mockup. Things went along fine, no lagging in PS performance, then the same type layer corruption started happening on this other project.
This is horrible, my clients are anticipating having access to my layered files. I’m now looking at hours of lost work that will likely have to be recreated. Now I’m contemplating having to do this with my older version of PS CS 5, but worried about this bug lurking in my source files.
If this is impacting any significant number of users, it’s very irresponsible not to alert your entire user-base. This is having an extremely negative impact on my business. I used to work for Frame/FrameMaker before Adobe acquired it and have a long history with Adobe products. I wholeheartedly regret upgrading to CS6 at this moment.
@ChrisCox I have a before/after file set that I can post for you to download. I was able to locate past version that appears “OK”, via incremental backups. I will email you a link. Please make this a top priority!
Setup: OS X 10.7.4, Adobe Photoshop Extended as part of CS 6, Suitcase 15.0.1 (although one file did not contain any non-system fonts). Once the corruption is in place, the type errors are present even when attempting to open in older Photoshop CS 5.x
I’ll be posting and tracking this on my twitter, @jydesign, with the hashtag #psd6typebug
Thanks @charles badland - It’s quite clear to me that they (Adobe) know what’s up here. It’s the fact that the many users of Adobe Photoshop CS 6 probably don’t know about this issue and may not find out until it’s too late and their files are corrupted like ours.
@Chris Cox - Thanks for your vague response. I urge you to follow up with the specific information:
I know no Adobe employee is allowed to speculate on the timing of future releases, however knowledge-based their information may be, and frankly some of the rest of it sounds like you're trying to build a legal case.
It's asking for that kind of thing that results in big companies pulling their engineers off public forums and denying everything, even obvious bugs. I'd sure rather not see that happen; Chris is a real asset here.
Data corruption bugs like this are considered a very serious problem, and this text issue is receiving the appropriate attention at all levels of the Photoshop team. We are sharing as much information as we can with you and others regarding this bug; I'm sorry we don't have more definitive information about the status of the engineering effort or any potential resolution date. As Noel noted, we cannot speculate publicly on future releases, or provide daily (or weekly) ETA's.
If and when we can offer interim advice about how to avoid or work around this problem before we resolve this, we will do so. In the meantime, we appreciate your patience and thank you for contributing your files to the effort.