This site is currently in read-only mode during migration to a new platform.
You cannot post questions, answers or comments, as they would be lost during the migration otherwise.
0 votes

I met with some difficulties in using the immediate geometry node.
It runs incredibly slow on Macos and my mobile phone ( Android system, I haven't tried IOS yet ) .But it runs quite good on windows, and the frame per second can be hundreds of times of other platforms'.
I ran the same code on Windows and Macos and on the same computer, there are just dozens of triangles need to be rendered, if I use the meshinstance, it will be very quick for sure.
After hours of searching, I thought it's probably a problem of the system rendering API but I'm not sure.

So I hope anyone can tell me how to run the immediate gometry node quickly on Macos and mobile phone.

And if it's due to some problem inside the system and can't be fixed by godot itself, what technique can I use to replace the immediate gometry node and also have the benefit of changing/adding triangles easily?

in Engine by (12 points)

Try using ArrayMesh, SurfaceTool or MeshDataTool instead, or use a vertex shader to achieve what you need. ImmediateGeometry has known performance issues.

Please log in or register to answer this question.

Welcome to Godot Engine Q&A, where you can ask questions and receive answers from other members of the community.

Please make sure to read Frequently asked questions and How to use this Q&A? before posting your first questions.
Social login is currently unavailable. If you've previously logged in with a Facebook or GitHub account, use the I forgot my password link in the login box to set a password for your account. If you still can't access your account, send an email to [email protected] with your username.