rendering thin 300+ / 600+ polyline (Line2D) quality/speed/memory

dotted

I have already bumped up the capacity settings in in the project settings but I find I the overall quality is not that great for rounded joint of width 2 or so large points line2d. I think off hand have enabled anti aliasing.

I am curious if a shader and other construct could be used for better memory/speed efficiency.

I want to only render rounded corners, which I assume are comparable with a shader's abilities.

Also I have several dozen of these larger poly-lines on display, but most are a list of thumbnails.Here I think I can render them to an image, then dispose of the line2d to save on resources.

Calinou

I have already bumped up the capacity settings in in the project settings but I find I the overall quality is not that great for rounded joint of width 2 or so large points line2d. I think off hand have enabled anti aliasing.

Did you reduce Border > Round Precision in the Line2D properties? For thin lines, you probably don't need it to be set above 2 or 3.

cybereality

Can you post a photo of the bad quality or what it should look like?

dotted

Some seem crisper, but the various segments do not have consistent width, some look like they are not aliased (this may be my own mistake) but in other shapes the line width deviation is more evident.

dotted

Q: would a shader improve performance or does godot already do this in a shader like:

https://stackoverflow.com/questions/3484260/opengl-line-width

I may also want to bevel some lines (more accurately chamfer corners) which i think can be accomplished in a shader

dotted

@Calinou said:

I have already bumped up the capacity settings in in the project settings but I find I the overall quality is not that great for rounded joint of width 2 or so large points line2d. I think off hand have enabled anti aliasing.

Did you reduce Border > Round Precision in the Line2D properties? For thin lines, you probably don't need it to be set above 2 or 3.

No, I will give a go tomorrow. thanks!

dotted

@Calinou said:

Did you reduce Border > Round Precision in the Line2D properties? For thin lines, you probably don't need it to be set above 2 or 3.

This along with more carefully ensuring settings are properly propagated has resolved the quality issue. Thanks.

This leaves rendering times. I probably have a lot of complicated rendering going that I can cull out.

dotted

Improvements.

All of these shapes are recursively/iteratively defined and I wish there was a 2d version of geometry-instance.

Calinou

All of these shapes are recursively/iteratively defined and I wish there was a 2d version of geometry-instance.

There's MeshInstance2D and Polygon2D already :)

cybereality

That looks pretty good to me. You could use Polygon2D but I'm not sure it would be worth it. It already looks okay.

dotted

@Calinou said:

All of these shapes are recursively/iteratively defined and I wish there was a 2d version of geometry-instance.

There's MeshInstance2D and Polygon2D already :)

Yeh, but help me here, line2D generates meshes under the hood and probably in a shader(?) I would think I'd need to extract that information to stick it in a mesh-instance-2d, right? Or am I missing something?

I also imagine using a polygon would mean I'd need to re-create rendering of line2D for rounded corners..

The performance issues I am not happy with might also be an artifact that there are a dozen or so of these recursive items, each different ( I am listing a catalog of the ones I define with the project scene). In short, there are lots of node2d's floating around atm.

@cybereality said: That looks pretty good to me. You could use Polygon2D but I'm not sure it would be worth it. It already looks okay.

Indeed. I had some settings missing and Calinou's advice fixed the stroke thickness issues,