Jump to content
You must now use your email address to sign in [click for more info] ×

Zero1

Members
  • Posts

    41
  • Joined

  • Last visited

Recent Profile Visitors

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

  1. Yes, i am using Aphoto, the first one was indeed from V1 but as @lepr pointed out, it is because of the blue blend range why it is turning black when you turn off the HSL.
  2. Thank you!! Missed that one.. It would be nice if Affinity would show the colored curves in the blend ranges (similar to a curves adjustment) so that you can directly see that there is a difference.
  3. I have attached a document where it looks like the groups are an exact copy (at least i cannot find or missed the difference). Group1 is from an old document which i copied over... Group 2 is one i created from scratch... Any one an idea what is happening? Group-acting-differently.afphoto
  4. I think title is self explanatory. I searched forums if this was already known but couldn't find anything. In the attached image you see that when the HSL is being clipped by a rectangle, the blend range is not applied.
  5. @Lisbon I believe the transparent areas are treated as black (value 0), which then makes sense why everything is divided by 2 (with alpha 0.5)
  6. When a procedural texture is applied to a curve object (eg. a rectangle) and the alpha value is changed (eg. 0.5), i would expect it would only affect the curve object's alpha, however the alpha is also applied to the layers below. When i lower the alpha of the rectangle with a curves adjustment, it only affects the rectangle as expected. See the screenshot, where on the left, the alpha of a red rectangle is halved with a curves adjustment. The blue background is not affected. However doing the same with the procedural texture (live) filter on the right, the alpha of the blue background is also affected. Initially I thought this only happened with the Alpha, but the bug also exists with RG or B. Then i rasterized the rectangle and applied the procedural texture again and it still happens. So it looks like the procedural texture (live) filter propagates down for the transparent areas even though it has applied as clipping layer. I would expect, because it is a clipped child it would only affect the parent (like the curves adjustment). I assume this is a bug unless i am missing something here? PS. Using the latest v2.04 (mac)
  7. You are completely right! Which brings us to the original question A checkbox is being hidden without reason... which is bad
  8. Haha, that is true, but still think it is detectable whether the merge is going to apply to the "parent" image or a child pixel... (at the end it applies to something and is processed if applicable, so it can be detected too...). Maybe hiding the button would case confusion (why not shown etc), but rasterizing the image layer would make sense.
  9. Thank you... missed that But in order to do that, i think Serif has to be very clear what is fixed/updated and not add a text like: - Assorted other fixes
  10. Thank you for clearing that out.. that was also my expectation (destructively applied(, however as i am mostly working with image layers, nothing was happening. Pixel layer was the magic word here I would suggest that when the filter is a child of an image layer, to hide this button or have the image layer rasterize to pixel (with a warning from assistant), which would make more sense. Secondly it is kind of strange behaviour when the (blur) filter in on top of image layer and a pixel layer is below it. The image layer gets blurred when merge is pressed, it skips the image layer and merges with the pixel layer below. It makes sense but i don't think that is expected behavior.
  11. Let's agree to disagree on the matter of whether it gives a better overview or not (less/more room). On the matter of the V1 Layer remark, the width of the panels can be controlled, so the full text can be made visible if needed and indeed i do add them now in the title when i change the title (which i was not doing when using v1) Again it is not something critical, i just wanted to point out that when show object types is turned off, it becomes very difficult to notice the difference between pixel and image layer (without hovering). All the other layers have their own icons and are easier to spot.
×
×
  • Create New...

Important Information

Terms of Use | 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.