Neue Testversion 25.00b11

[Vivi_Ram]

I guess you expect too much from Mesh Gradient on so complex vector shapes. It is more logical to draw simple shape specially for mesh gradient and use main vector image as clipping mask for it.
Screen Shot 2025-11-12 at 2.41.58 PM.jpg

That's what I did to workaround it. I clipped a mesh to the shape. However, that does not explain why the shape is being distorted.

[Vivi_Ram]

I am trying to run text on path, but instead of text, I dropped a vector shape into the text layer and then ran the text on a circle. Until this point it works perfectly. The vector shape is run on the circle. But now select the same text layer and turn it into a dynamic layer, it produces an instant crash.

Steps to reproduce crash:

1. Take a vector object like a square or circle and drop it into text layer.
2. Run the text layer on path.
3. Turn the same text layer into a dynamic text layer in the tool settings. >> Crash.

Also, question: Why are we not able to make vector objects repeat when run on path like we can with text. It would be good to add this as an option. It's a small workaround for the lack of morph along path, by the way.

[Vivi_Ram]

Applying 3D Body on Text produces strange artefacts. When you zoom in and out, the shapes render differently. Outlines when you zoom in close. And solid objects + overlapping text when you zoom out. Is this a bug?

[Herbert123]

Yes, but in PL, it only works if the lines are raster layers. You cannot do a flood fill directly on a vector layer. In the GIF I have added to my previous response, the lines are vector. That's what I mean. And the resulting curve is sharp because there's no anti-aliasing. There are three nodes. One for each corner.

See below: layer.jpg

? I have three vector layers each with a line that cross to define a curvy triangle. (Same as your example).

I then select the background layer (or any image layer), activate the flood fill with All Layers as the source, Overfill and Create Vector Layer checked.

Fills the shape as defined with those three lines.

It's not that much work, but I do agree the fill tool ought to be available when a vector layer is selected. It is counter-intuitive when the user needs to select a bitmap layer or even is forced to create a new bitmap layer before the fill tool becomes available for vector layers.

[Vivi_Ram]

layer_4.jpg

Okay, I can see what you mean. But like you say, there's no reason why flood fill shouldn't be available with vector layers active. I agree.

However, even with your solution, we still have the problem of enormous number of nodes. This can be vastly improved.

[Vivi_Ram]

Here's another workflow challenge I face:

All filters/adjustments applied to vector shapes are clipped just to the initial bounds of the object. In order to avoid this, I have to manually select the mask, unlock the mask position and scale it. This should be automatic. The problem becomes apparent when you expand the bounds of the shape beyond the mask: The filter/adjustment is not applied to whatever is beyond the shape.

layer_5.jpg

In the image above, I've applied a gaussian blur to the shape, and as you can see, the blur is clipped to the initial bounds of the shape. Then, I pulled the node outside the limits of the mask, and the blur does not apply to this portion.

[shijan]

Here's another workflow challenge I face:
All filters/adjustments applied to vector shapes are clipped just to the initial bounds of the object. In order to avoid this, I have to manually select the mask, unlock the mask position and scale it. This should be automatic. The problem becomes apparent when you expand the bounds of the shape beyond the mask: The filter/adjustment is not applied to whatever is beyond the shape.
In the image above, I've applied a gaussian blur to the shape, and as you can see, the blur is clipped to the initial bounds of the shape. Then, I pulled the node outside the limits of the mask, and the blur does not apply to this portion.

Uncheck "Group with Previous layer" when add adjustment layer and it will use document area instead of layer frame. Next you can manually drag adjustment layer inside vector layer or add both to group.

Screen Shot 2025-11-14 at 12.12.40 PM.jpg

Also in already created adjustments you can uncheck locking icons and edit adjustment mask like this. Or use "Layout->Image->Bring to Document Size" and then fill transparent areas with white color.

[Vivi_Ram]

Thank you @Shijan: I manually expanded the mask like you show there. The group thing works.

Edit: Applying adjustment to the group throttles the CPU really hard.

[Herbert123]

layer_4.jpg

Okay, I can see what you mean. But like you say, there's no reason why flood fill shouldn't be available with vector layers active. I agree.

However, even with your solution, we still have the problem of enormous number of nodes. This can be vastly improved.

It can be fixed (partly) by optimizing (simplifying) the curves with Layout-->Vector-->Optimize Vector Layer.

2025-11-14 14_08_22-#1.jpg

Of course, it's not going to as good as manually placing points... (well, AI could probably do it)

[Herbert123]

Thank you @Shijan: I manually expanded the mask like you show there. The group thing works.

Edit: Applying adjustment to the group throttles the CPU really hard.

At some point in the compositing process, depending on the resolution of the file as well as the number and type of adjustments and live effects, PhotoLine will slow down. That is only to be expected, and happens with all image and video editing software, even if they are GPU hardware accelerated.

This is the reason why smart objects were introduced in Photoshop and why Placeholder layers should be introduced when things start to bog down PhotoLine. Same reasoning behind subcomps in After Effects and nested clips in NLE video editors.

Compared to Photoshop when we work in PhotoLine we have far more freedom of choice: live non-destructive effects are only possible with smart objects in Photoshop, while PhotoLine users aren't locked in this workflow (with placeholder layers). But when the comp begins to slow down, we also have to start converting part of the layer stack to placeholder layers to keep PhotoLine from slowing down too much.

[der_fotograf]

It can be fixed (partly) by optimizing (simplifying) the curves with Layout-->Vector-->Optimize Vector Layer.

Of course, it's not going to as good as manually placing points... (well, AI could probably do it)

@Herbert123: Wow, thank you so much for this hint. Just by coincidence, I was looking for a solution to reduce vector points in a symbol, checked everything, but couldn't find a solution to smooth the delivered *.svg file. So I used a free service online from a company not related to graphics, and the result was great. However, with your hint, I was able to get an even smoother result within PL.

These tiny tips and hints are so valuable…

[Vivi_Ram]

layer_4.jpg

Okay, I can see what you mean. But like you say, there's no reason why flood fill shouldn't be available with vector layers active. I agree.

However, even with your solution, we still have the problem of enormous number of nodes. This can be vastly improved.

It can be fixed (partly) by optimizing (simplifying) the curves with Layout-->Vector-->Optimize Vector Layer.

2025-11-14 14_08_22-#1.jpg

Of course, it's not going to as good as manually placing points... (well, AI could probably do it)

Thank you! @Herbert123: This is essentially what I did too. What I meant by improvement is at the level of code. The flood fill tool used on vectors should not produce so many nodes. I guess its something to do with edge detection. Not sure.

[Martin Huber]

That's what I did to workaround it. I clipped a mesh to the shape. However, that does not explain why the shape is being distorted.

The shape isn't distorted, but simplified, because otherwise you would get even more points.

With a complex shape like yours you should either use a clipping path (like shijan suggested) or split the shape in several basic ones.

[Vivi_Ram]

Right... Okay. Thank you. So it's a feature, not a bug.

What do you think of the excessive number of nodes in the flood fill tool? Do you see any room for improvement there?