Sprite3D View Frustum Culling Issue on Android

[Ralf12358]

Godot version:
Head on Branch 3.2; 89f57ae

OS/device including version:
GLES2, Android. Tested with Galaxy S7 Edge and Amazon Fire HD 8

Issue description:
On Android Sprite3D Is culled as soon as the origin is out of the view frustum - without considering the size of the sprite. Works correct on Desktop (Linux) and Browser. Other platforms (iOS) are not tested

Steps to reproduce:
Create new 3D Scene. Add camera. Add Sprite3D. Position Sprite3D to have the origin outside of the view frustum, but parts of the sprite inside the view frustum. View Scene: On Desktop the partial sprite is shown correctly, whereas on Android the complete sprite is culled.

Minimal reproduction project:
See attached minimal project:

GodotBug.zip

[Calinou]

This has most likely been fixed in #39867 (in addition to performance improvements). Give 3.2.3beta1 a try 🙂

Edit: I didn't see the part about OP using the HEAD of the 3.2 branch. Sorry about that.

In the meantime, you should use MeshInstance + PlaneMesh or QuadMesh instead of Sprite3D to improve performance and avoid this issue.

[Ralf12358]

Just to be sure: I'm on head on the 3.2 branch. This should include all fixes from the 3.2.3beta1, right? So, it is probably not fixed.
With the regular 3.2 release: Sprite3D was unusable with less than 1 FPS.
As you suggested I'm now using a QuadMesh, I experiencing a new Android specific issue with pngs with alpha channels. I would like to report a new bug, but before doing so I would make sure to use the newest 3.2 branch.

[Calinou]

cc @clayjohn

I suppose this occurs because the culling AABB is never set, so it keeps its default size which is an infinitely small box.

[clayjohn]

@Calinou are you sure? The OP says that it works fine on desktop but fails on Android. Sprite3D does have an AABB and I think the VisualServer generates another one when the mesh is set.

I'll have to look in more detail.

[clayjohn]

Confirmed on Windows 10.

[akien-mga]

Fixed by #40559.