Godot: SurfaceTool spams output if not setting an index array

Created on 19 May 2018  路  8Comments  路  Source: godotengine/godot

Godot version:
Godot 3.02

OS/device including version:
Windows 10, GTX 1060

Issue description:
using surface tools with tool mode keeps spamming the output window with:

drivers\gles3\rasterizer_storage_gles3.cpp:3265 - Condition ' surface->index_array_len == 0 ' is true. returned: PoolVector<uint8_t>()

Minimal reproduction project:

SurfaceToolTest.zip

archived enhancement core

Most helpful comment

It seems the issue here is somewhere in the mesh code. For some reason the mesh drawing code is expecting there to be an index array. For now, an easy way to avoid getting the errors is to get the SurfaceTool to generate indexes for you by calling surfacetool.index() before you commit it.

All 8 comments

It seems the issue here is somewhere in the mesh code. For some reason the mesh drawing code is expecting there to be an index array. For now, an easy way to avoid getting the errors is to get the SurfaceTool to generate indexes for you by calling surfacetool.index() before you commit it.

Thanks for taking the time to review this issue, and yes I confirm that calling surfacetool.index() solves the issue.

Related: #18201 (built-in primitive quad mesh spamming the same error)

@Zireael07 Should we merge those two issues (since it seems to be about the same problem)?

Feel free to.

Okay, merging into #18201, as it is the same problem (meshes without indexed arrays spam output).

This issue is still present. Will this be addressed anytime soon?

@ConnorDY This is the same issue as #18201, please track the progress there.

Was this page helpful?
0 / 5 - 0 ratings