Polygon2D mesh disappears when vertices exceed boundaries

[Demonfir3]

Tested versions

4.2.1

System information

Windows 11 - Vulkan (Forward+) - RTX 4060

Issue description

Polygon2D instances disappears from a viewport when being strongly rotated by attached Bone2D.
This happens to all polygons2D when you zoom close enough or polygon starts reaching end of the viewport.
In provided video feet starts to disappear when I try to straighten them.

DungeonCrawler.zoomed.in.mp4

Steps to reproduce

1. Open project provided.
2. Open player_3.4v3/node_2d.tscn
3. Use AnimationPlayer and play "new_animation_3".
4. Zoom in to actor feet or right arm while animation plays.

Minimal reproduction project (MRP)

minimal_project.zip

[TokageItLab]

I assume the problem is probably the self-intersecting path, but is this a bug that depends on the size of the viewport?

[Demonfir3]

The closer to the edge of a viewport the polygon is, the earlier this happens. If I play the same animation and the feet are in a center of a viewport , the feet will not disappear.
I think it is something similar to this #74132, because suggested workaround for using polygon offset instead of position solves the issue. Tried version 4.3 dev 1, the same thing happens.

[GreatRedBird]

Good evening, I have a similar problem. Version 4.2.1.
Did you manage to fix this problem somehow?
I'm a complete newbie, I tried various options, but none worked. Is the only option to wait for version 4.3?

[kleonc]

Is the only option to wait for version 4.3?

@GreatRedBird The fix was cherry-picked to both 4.1.4 and 4.2.2, specifically it's included since 4.1.4.rc1 / 4.2.2.rc1. Although these are "release candidates" (so not yet "stable" releases) they should be rather safe to use already (because there's a selection of what is being backported to earlier versions; big / potentially unsafe changes are not being backported etc.).
So if you don't want to wait you can try 4.2.2.rc1 - download from here or here.
(Of course you could also try 4.3.dev3 (the fix is included since 4.3.dev2) but it's a dev version and it's expected to be more buggy / less stable.)

[kurayamiblackheart]

Is the only option to wait for version 4.3?

@GreatRedBird The fix was cherry-picked to both 4.1.4 and 4.2.2, specifically it's included since 4.1.4.rc1 / 4.2.2.rc1. Although these are "release candidates" (so not yet "stable" releases) they should be rather safe to use already (because there's a selection of what is being backported to earlier versions; big / potentially unsafe changes are not being backported etc.). So if you don't want to wait you can try 4.2.2.rc1 - download from here or here. (Of course you could also try 4.3.dev3 (the fix is included since 4.3.dev2) but it's a dev version and it's expected to be more buggy / less stable.)

Where can you find the source code download of it though? They all seem to be pre-built downloads...