Photographing the Milky Way

Your content will be up shortly. Please allow up to 5 seconds
News & Insight

Liquify Is Broken In The Latest Photoshop Update & Here’s A ‘Fix’

By Kishore Sawh on December 7th 2015

liquify-photoshop-error-broken-fix-8bit-gpu-adobe-cc-photography-slrlounge-kishore-sawh-7

If autocorrect were to ‘work’ on speech, it would’ve said my first reaction to what the new Photoshop CC’s Liquify does to photos was ‘What the duck?’ Because in case you weren’t aware, with the new update came a new and exciting way to frustrate you, due to the fact that using the liquify tool to adjust an image would result in a rather large, not inconspicuous block around the area worked on as seen above.

I’d heard about the problem about a week ago, but I had friends visiting and was on hiatus from editing, and in any case assumed it was not a common experience. However, now in the throes of reviewing a rather good Photoshop panel, I’ve found this issue a blemish on an otherwise good day. To be clear, the issue in my experience has arisen irrespective of the specific action tool within the Liquify toolbox, whether it be pucker, bloat, reconstruct, or forward warp, but there is a workaround. Actually, there are two.

Thankfully, now that some time has passed since the issue initially arose, the boffins at Adobe have fiddled with the Rubik’s cube of a problem, and offered up the following:

  • The issue seems to only pertain to 16-bit files, so if you’re shooting 8-bit you shouldn’t notice a difference, and, therefore, you can get around this issue by simply converting the file to 8-bit prior to using Liquify. Now, of course, asking some to edit in 8-bit is tantamount to asking them walk through Tehran in a Star Of David T-shirt, and I’m in that camp, so that’s not really an option. If you’re with me then here are the other options:
  • Open your image as normal:
    liquify-photoshop-error-broken-fix-8bit-gpu-adobe-cc-photography-slrlounge-kishore-sawh-8Go into Liquify as normal, make your edits, and select ‘Save Mesh’ before exiting Liquify. It’ll ask you where to save and typically just let it save in the location of the image being worked on. There’s no need to keep the file name in mind either, and you’ll see why.
liquify-photoshop-error-broken-fix-8bit-gpu-adobe-cc-photography-slrlounge-kishore-sawh-6

Me, with a beer belly.

liquify-photoshop-error-broken-fix-8bit-gpu-adobe-cc-photography-slrlounge-kishore-sawh
liquify-photoshop-error-broken-fix-8bit-gpu-adobe-cc-photography-slrlounge-kishore-sawh-5

  • Now that you’ve done that, you can click ‘Cancel’ in the main Liquify dialogue box, and then holding down Option/Alt select the Liquify tool from the Filter menu again. What this does is disable the GPU in Liquify (more on that in a moment). Once in it, simply click on ‘Load Last Mesh’ and you’ll see the adjustments you made last, reappear. Now, click ‘OK’, and Bob’s your uncle.

liquify-photoshop-error-broken-fix-8bit-gpu-adobe-cc-photography-slrlounge-kishore-sawh-3

I don’t work on Windows computers, so this is second-hand information, but I’ve heard that option two above doesn’t really work for Windows users, something to do with disabling the menu or some other nonsense. So, Windows users, it would appear that your options are either to convert to 8-bit for edit, or simply go in and fully disable the GPU before working in liquify, and then coming to your senses and switching to OSX (I’m kidding).

[REWIND: 10-BIT SUPPORT NOW AVAILABLE FOR PHOTOSHOP CC IN OS X]

Thoughts

I’ve often advocated Adobe’s move to Creative Cloud and I still will. I like the fact it opens up availability to many more people due to the pricing structure, and that it allows for updates to be pushed out quickly. That said, there’s just been a slew of poorly executed updates, and that is a scar on the whole thing. I may be out of place here trying to speak for the majority, but forgive me for believing that most users would rather there be more flawless updates at the cost of having fewer of them.

Thankfully, this issue can be sorted in some way, but frankly, it’s a pest if you’re spending any decent time retouching. I’m a bit surprised that this rather glaring error could be overlooked by the Adobe Photoshop team. Come on Adobe, you’re letting the side down.

You can see a thread of angry users and their comments here

About

Kishore is, among other things, the Editor-In-Chief at SLR Lounge. A photographer and writer based in Miami, he can often be found at dog parks, and airports in London and Toronto. He is also a tremendous fan of flossing and the happiest guy around when the company’s good.

Q&A Discussions

Please or register to post a comment.

  1. David Delahoussaye

    Not sure if anyone has replied to the comment about this workaround not working in Windows but it does work. Just tried it.

    | |
    • Gabriel Rodriguez

      Yeppers, it does work! Just tried it out, too! Im running on Windows 10, in case if you guys are wondering.

      | |
  2. Paula Brown

    I think the problem may go beyond liquify. I was editing using “adaptive wide angle” filter last night and had to ditch it. Correcting the verticals worked OK, though very slowly. When I finished and applied the filter it had strange boxes all over it that made a grid effect all over the image. It was ruined!

    | |
  3. Arnaud Giret

    i wish i was working with anything than photoshop for the last 4 days,
    intense retouch, then liquify stopped down all my delivery planning,
    trying to resolve a problem i thought occured in my computer /
    time lost / client does not care / Adobe.
    That’s a wonderfull baseline :
    time lost
    client does not care,
    Adobe.

    | |
  4. Craig Cacchioli

    I wish I had come here first. I’ve just trawled the Adobe forums trying to find an answer and nothing current is there. I hope they push out a fix for this really quick.

    | |
  5. Chris Keeley

    YES! OMG…. thank you for posting this. This has completely halted my editing, and I thought I was totally alone on this. I noticed it a week ago and was like…. wtf?! THANK YOU SO MUCH! Let’s hope this get’s truly remedied.

    | |
  6. Tom Blair

    Tan lines……..I miss summer

    | |
  7. Pye

    I agree, Adobe needs to work on their updates. They keep breaking things because I think they are trying to roll out things too quickly. Still having issues with the heal stamp brush =(

    Great post Kish, hilarious belly =)

    | |
    • Tanya Goodall Smith

      I agree. What’s the rush? The less updates the better, in my opinion, LOL.

      | |
    • Tanya Goodall Smith

      Kish, you’re so dang cute, even with a beer belly! ;) As for the botched software, my solution is to wait to update until I’m absolutely forced to do so… True story. Hopefully they have the bugs worked out by the time I update. Haha.

      | |
    • Ed Rhodes

      sounds like they are trying too hard to justify the subscription model by putting out updates before they are ready.

      | |
    • Jason Finch

      The constant updates would indicate justification in subscription. If you are paying monthly for a product, I guess to some degree you expect constant updates. Perhaps they should consider offering channels similar to browsers, so you can subscribe to either the bleeding-edge channel or the stable channel. Bleeding-edge updates get rolled over to stable channel only after say 6 months of real use.

      | |
  8. Bill Bentley

    “That said, there’s just been a slew of poorly executed updates, and that is a scar on the whole thing. I may be out of place here trying to speak for the majority, but forgive me for believing that most users would rather there be more flawless updates at the cost of having fewer of them.”

    I “was” considering making the move to CC in Jan 2016. Looks like I’ll continue making magic with PS6 and LR4 for a while longer.

    | |
[i]
[i]