Jump to content

ladlon

Members
  • Content Count

    108
  • Joined

  • Last visited

About ladlon

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hi, Chris B. Ya, we've been trying to sort this one out, figuring out triggers/specifications. It seems it might be partially related to a bug that was found where it seems that selection order now (after the recent update) seems to matter when merging (...select the layers in the wrong order, and the merge results in the contents from the pixel layer being erased). I've done some tests over here, and have found some specifications for my particular issue. It seems to be related to grouping (as well as groups within groups). I'm going to do some further tests, and provide support with a specific list of situations and results, but here's what I have found so far (...and this relating to the Merge button on the top right of the Adjustments windows): 1) Adding a targeted adjustment (using the Adjustment icon method described above) to a single, unparented layer (with no childred) and hitting the Merge button works fine 2) Doing the same to one of two grouped layers (each without children, and with their group not grouped/parented to anything.... just two single layers grouped together) resulted in a non-responsive Merge button (Nothing happens to the layers). Note: The command history DOES show that a Merge is triggered each time, but nothing happens to the layers... the adjustment layer child remains) 3) Doing the same to a single layer that is grouped with several other layers, which is also grouped to another set of layers (group within a group) results in the destructive/content clearing bug I noted in my previous examples.... adjustment layer is removed/merged, but the pixel layer's contents are cleared completely, leaving it empty, but still present. There has been a discussion about this (and some other related issues we've been finding) in my thread found here:
  2. @Carl123: I know that was targeted to HuniSenpai, but in my case, I'm selecting the target layer, and then clicking the Adjustment icon to add a layer-specific adjustment to it, which is automatic, so I have no control of how it connects it. In my case, there seems to be a bug(?) related to grouped items (and/or groups in groups), which perhaps the team hasn't run into yet. I'm going to do some more tests, and establish a specific list of situations and results for each to provide to support.
  3. Further findings: So, in my REAL project (as opposed to a simple test one), I found the following: 1) Adding a targeted adjustment (using the Adjustment icon method described above) to a single, unparented layer (with no childred) and hitting the Merge button works fine 2) Doing the same to one of two grouped layers (each with out children, and with their group not grouped/parented to anything.... just two single layers grouped together) resulted in the non-responsive Merge button shown in one of your videos (...Note, the command history DOES show that a Merge is triggered each time, but nothing happens to the layers... the adjustment layer child remains) 3) Doing the same to a single layer that is grouped with several other layers, which is also grouped to another set of layers (group within a group) results in the destructive/content clearing bug I noted in my previous examples.... adjustment layer is removed/merged, but the pixel layer's contents are cleared completely, leaving it empty, but still present. Going to go for a walk, but will tinker around with this further. For now, the workaround seems to be to do the targeted layer method (click on the Adjustment icon, etc).... but rather than hitting the Merge button, you exit, select the pixel layer (which will select both it and the child adjustment layer) and hit Rasterize in the context menu. A bit less convenient, but at least it works for now. Hopefully, I can assign a hotkey to Rasterize (....an annoyance I point out in ANOTHER of my threads, where I am baffled by why only a select few of the commands can have a keyboard shortcut assigned, rather than all of them being available in the shortcut edit window). I'll keep you posted on what I find. Thanks again for your help so far!
  4. Just did a quick test... My three coloured blob layers.... but this time, I grouped them together, and applied a targeted adjustment to the 2nd layer (selected it, clicked the Adjustment icon, selected HSL, made the adjustment and then hit the Merge button). That actually worked, too.... So, it's not specifically/exclusively a bug related to heirarchies... by that, I mean that it CAN work, but in the case of my (real) project, it doesn't. So, more tests will follow....
  5. I'm going to try a bunch of tests with various heirarchies/groupings, and see what it does. You are on to something, even though your results (though also incorrect/bugs) are different from mine!
  6. Ha, we are both responding so fast, this is like live chat! That last video is interesting. Doesn't seem to be what is happening with mine, but that certainly seems like a bug (...in the sense that it should just merge the target layer (adjustment to the donut)) In my case, the rest of the heirarchy remains, but the target layer clears (rather than results in a layer that contains ALL the content of ALL the layers in the hierarchy, like your video does.
  7. UPDATE: I just did a test on a new/test 'project', rather than my actual project. Three simple pixel layers... each a different blob of colour. Selected the middle one, clicked the Adjustment icon (bottom of Layer window), and selected HSL. HSL adjustment window opened, and I dialed down the saturation (making that layer grey). Clicked the dreaded Merge button at the top of the HSL adjustment window.... and it WORKED! Okay, so for some reason, there's some aspect of my (real) project file that is buggering up the merge functionality.... Memory usage??? (I've got 32 gigs, and this isn't a massive project, so that SEEMS unlikely) Nothing obviously odd in my layers.. just a bunch of paint layers... some grouped together... a few with adjustment layers..... but that's it. Nothing fancy or unusual. Yet, it is obvious that something is either stressing the program... or some previous action has somehow buggered up the program's functionality... No idea. But, yes, it is confirmed that the Merge DOES work in a small/different test project. That would explain why many are not seeing this issue. I'm going to close my (real) project, and reload it... to the issue is 'baked' into the project, or if it's related indirectly (duration of the work session, etc).
  8. Seems to be happening since the last update, as it worked the way I expected up to now... unless I have gone completely insane.
  9. I'm on the latest version (1.8.2.620) Win7 Pro. I'm having a few odd things happen... including another quirk I did a thread on (which I think you are also involved in, too) where the square bracket keyboard shortcut for sizing the brush stop working after some random amount of time (yet all the other shortcuts and the program itself continue working!).
  10. It really seems like they broke merging in general with the new update... including that bug previously pointed out about the selection order!
  11. @HuniSenpai: Thanks for all the vids and effort! Yes, that last video shows you doing the thing I'm talking about in the first part of the video... yet, in your case, it works (or at least doesn't clear the content of the layer. I'm doing the same thing, but when I hit Merge, the contents of the layer disappears/clears!
  12. Okay, let me try another explanation.... You have 8 layers. All are lovely, except the 3rd one is too bright compared to all the other layers. Normally, you'd just select that layer, and apply (say) a Levels adjustment (live, destructively), adjusting it until it looks right, compared to the other layers. Unfortunately, it appears that AP doesn't allow for that, opting instead to do a non-destructive Adjustment Layer method... which I am not against (as it does, afterall, offer the benefits of a non-destructive adjustment). However, sometimes, you don't want all those adjustment layers parented inside each of your layers. Sometimes, you just want to bake it, as you are sure you don't want to revert it back or whatever. So, with the current system, you'd normally select the 3rd pixel layer... apply a (non-destructive) adjustment layer (Levels in this case) to it, so when you adjust the Levels dials, you can see the affect of the adjustment live, compared to the other layers, until you find the right setting. You would then (normally) hit the Merge button at the top of the Levels adjustment window you have been using (unless you wanted to keep the non-destructive Levels adjustment layer parented inside the 3rd pixel layer). Normally, hitting this button would bake the Levels adjustment into that third pixel layer, and you'd have a (longwinded) destructive/instant levels adjustment to the 3rd layer. But, that doesn't currently work, now... Doing so causes (at least on my system) the 3rd layer to be cleared when the merge occurs. But, there is no other method to do this type of thing, as putting an adjustment above the 3rd layer will adjust ALL the layers below it, so when you dial down the brightness of the 3rd layer (eyeballing it to the other layers), all the other layers below will also simultaneously get darker, making it impossible to match, since the other layers will 'run away' from their original settings as you approach them.
  13. I'm dealing with a real project (multiple layers, etc).... but, in trying out things to troubleshoot, I am simply applying a single adjustment layer (child) to a single pixel layer.
  14. But, that functionally doesn't make sense. If you want to effect a specific layer (as opposed to a global effect), you would first select the layer, which then causes an adjustment selection to be (rightfully) parented to it (otherwise, it will effect ALL layers, making it impossible to compare the targeted layer to the layers you want to adjust it to (compare). To click on the Merge button in the adjustment window SHOULD merge (bake) the adjustment to the selected/targeted layer... as that's the entire point of it. Otherwise, again, if you have 8 layers, and you want to tone down the 3rd one (as, say, it's too saturated compared to the others), how WOULD you apply a desaturation to just that layer WHILE BEING ABLE TO LIVE MONITOR YOUR ADJUSTMENT while doing so, so you can set it to the right level (compared to the other layers). Putting the layer above the target layer will adjust ALL layers below it, making it impossible to set the adjustment of the target layer, since all the other (lower) layers that you are trying to compare it to are simultaneously (and wrongfully) getting adjusted as well, so you will never be able to get all their saturations balance, as the other layers will FURTHER desaturate as you lower the saturation of the target layer (and adjustment which won't bel applied, once you do the manual merge).
  15. This is the button I'm referring to, which should merge the effect (of the open adjustment window) to the layer that it is targeting (the parent pixel layer)
×
×
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.