Hi,

- 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)

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.

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.

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?

-Noel

Hey Chris,

I created a couple of 3D layers from high and low wing airplane models, and generated perspective shadows using 3D light and perspective. The illustration still cheats on altitude and cast shadow size, but I may get away with that.

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.

I've see it on my setup without Suitcase.

Hi Chris,

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.

Thanks,

BJ

PS: I can rasterize the layers with latent cross-link behavior and they rasterize as displayed.

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 also having this problem, I have an untouched CS5 file if needed (33 MB)

Creative Cloud

iMac 2.7 GHz Intel Core i5, 12 GB RAM

OSX 10.7.4

One font with error and in use in PS document at time "Grenoble" (see screeshot below)

File being used with MediaLabs Sitegrinder 3.5.6 s_319

ok Chris, I'd need your email.

sending now via largefilesasap.com

I'm off to the bar to cure my very frustrated brain

Till then I'm back to using CS5

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

they know...

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:

• Will Adobe confirm or deny that any files that are experiencing this form of  corruption are unsalvageable? I’m pretty much assuming that my files are toast, but I want an on the record confirmation from Adobe
• Will Adobe let us know if there’s anything that can be done to keep this from happening to our other files, when using the current version of PS CS 6, or should anyone experiencing this issue refrain from using PS CS 6 until a fix is posted? At the moment I’m using PS CS 5.x in fear of losing any more important work files.
• Will you provide an ETA for a fix on a daily or at least weekly basis?
• Will you provide me (and any other user) with an Adobe contact should we wish to get a refund?

I agree with Noel. It's one thing to want to express the serious nature of an issue (but I'm sure that's beyond obvious in this case) and it's quite another to drop in with a ********* legalese laundry list. I'm sure that if you peruse your terms of use agreement you'll find that you accepted all risks inherent with using the software. If you sincerely want a refund, take that up directly with Adobe customer support.