Jump to content

Recommended Posts

Posted

This is more of a question: I don't know if this is just a beta issue or intended functionality but it doesn't make a whole lot of sense. ...and if the assistant is routinely going to step in and rasterize layers (even when I don't ask it to), then why not here?

Mac Mini (2018) - OS X 10.15.7 - 3 GHz 6-Core Intel Core i5 32 GB 2667 MHz DDR4 Intel UHD Graphics 630 1536 MB 

Posted

I was going to say it's because you need to rasterise your image layer, which will then work and because it isn't an option within the assistant to automatically rasterise the image layer but selecting merge visible works without the prior need to rasterise the image layer which is the same behaviour as V1 but I'm unsure why the differentiation between merge selected and merge visible, i.e., why the latter automatically rasterises the image layer but the former doesn't...

I'm sure someone else will know the answer though... :)

Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0
MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Posted
1 hour ago, Hangman said:

but I'm unsure why the differentiation between merge selected and merge visible, i.e., why the latter automatically rasterises the image layer but the former doesn't...

Are you sure that "Merge Visible" rasterizes the image layer? It certainly copies pixel information from the image layer, but Merge Visible (in my experience) creates a brand new layer, and does not affect the layers it's merging from.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.3.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Posted
1 hour ago, orangefizz said:

and if the assistant is routinely going to step in and rasterize layers (even when I don't ask it to)

Do you have an example where the Assistant rasterized something you had not asked it to rasterize? I don't think I've ever experienced that.

-- Walt
Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases
PC:
    Desktop:  Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 

    Laptop:  Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU.
    Laptop 2: Windows 11 Pro 24H2,  16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU
iPad:  iPad Pro M1, 12.9": iPadOS 18.3.1, Apple Pencil 2, Magic Keyboard 
Mac:  2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1

Posted
24 minutes ago, walt.farrell said:

Are you sure that "Merge Visible" rasterizes the image layer? It certainly copies pixel information from the image layer, but Merge Visible (in my experience) creates a brand new layer, and does not affect the layers it's merging from.

That is a very good point... :)

Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0
MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse
HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse

Posted
24 minutes ago, walt.farrell said:

Are you sure that "Merge Visible" rasterizes the image layer? It certainly copies pixel information from the image layer, but Merge Visible (in my experience) creates a brand new layer, and does not affect the layers it's merging from.

I found it simply doesn't merge a pixel layer with an image layer—nor does it automatically rasterize the image layer in order to do so.

Mac Mini (2018) - OS X 10.15.7 - 3 GHz 6-Core Intel Core i5 32 GB 2667 MHz DDR4 Intel UHD Graphics 630 1536 MB 

Posted
24 minutes ago, walt.farrell said:

Do you have an example where the Assistant rasterized something you had not asked it to rasterize? I don't think I've ever experienced that.

It happens fairly often for me (probably the same edit I'm doing across many images). It might possibly be when I try to apply a filter or other such edits to an image layer.

Mac Mini (2018) - OS X 10.15.7 - 3 GHz 6-Core Intel Core i5 32 GB 2667 MHz DDR4 Intel UHD Graphics 630 1536 MB 

Posted
16 hours ago, orangefizz said:

and if the assistant is routinely going to step in and rasterize layers (even when I don't ask it to), then why not here?

The assistant steps in exactly in the configured situations, and only then.

The description in help and UI does not give a full list of preconditions and edge cases. But in essence:

  • when trying to use brush for painting on vector layers, or empty canvas (but not on image layers)
  • when trying to use delete brush on vector layers
  • when applying filters destructively to vector layers (but only certain layer types)

If you thing the is something wrong, please use history to check what exactly happened. In many cases it is just the wrong layer active/selected in layer stack leading to surprises. If your find something broken, please upload the document (saved with history) and a screen recording (including visible layer stack, navigator panel, history panel if possible).



 

A4551649-668F-4CE9-91B6-CC7C3415DD15.png

Mac mini M1 A2348 | MBP M3 

Windows 11 - AMD Ryzen 9 5900x - 32 GB RAM - Nvidia GTX 1080

LG34WK950U-W, calibrated to DCI-P3 with LG Calibration Studio / Spider 5 | Dell 27“ 4K

iPad Air Gen 5 (2022) A2589

Special interest into procedural texture filter, edit alpha channel, RGB/16 and RGB/32 color formats, stacking, finding root causes for misbehaving files, finding creative solutions for unsolvable tasks, finding bugs in Apps.

I use iPad screenshots and videos even in the Desktop section of the forum when I expect no relevant difference.

 

  • Staff
Posted

It looks like there's a bug wherein the order of the layers matters if you're going to merge a pixel layer and an image layer.

If the Pixel layer is above the Image layer, it will not work:

Pixel above Image.png

However, if you drag the Image layer above the Pixel layer, it will merge:

Image above Pixel.png

Result:

Merged.png

This was reported a while ago so I'll go ahead and wake it up as it hasn't had any activity for a while. Thanks!

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • 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.