Infer array length from custom array if no vertex array is provided - #1133
Merged
Merged
Conversation
While the `RenderingServer::mesh_create_surface_data_from_arrays` method does support vertexless meshes (see #62046 and #83446), it enforces that the size of custom arrays is dependent on the size of the vertex array. This effectively means that custom arrays cannot be used in vertexless meshes. This commit changes the way the array length is computed so that if no vertex array is provided, its length will be inferred from the custom arrays, if provided. It therefore adds support for custom arrays in vertexless meshes.
Co-authored-by: A Thousand Ships (she/her) <96648715+AThousandShips@users.noreply.github.com>
…et_vertex_to_custom_array_length_factor`
mcdubhghlas
pushed a commit
to mcdubhghlas/redot-engine
that referenced
this pull request
Feb 17, 2026
…edot-Engine#1133) * Infer array length from custom array if no vertex array is provided While the `RenderingServer::mesh_create_surface_data_from_arrays` method does support vertexless meshes (see #62046 and #83446), it enforces that the size of custom arrays is dependent on the size of the vertex array. This effectively means that custom arrays cannot be used in vertexless meshes. This commit changes the way the array length is computed so that if no vertex array is provided, its length will be inferred from the custom arrays, if provided. It therefore adds support for custom arrays in vertexless meshes. --------- Co-authored-by: Adrian Samoticha <86920182+Adrian-Samoticha@users.noreply.github.com> Co-authored-by: A Thousand Ships (she/her) <96648715+AThousandShips@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
While the RenderingServer::mesh_create_surface_data_from_arrays method does support vertexless meshes (see godotengine/godot#62046 and godotengine/godot#83446), it enforces that the size of custom arrays is dependent on the size of the vertex array. This effectively means that custom arrays cannot be used in vertexless meshes.
This commit changes the way the array length is computed so that if no vertex array is provided, its length will be inferred from the custom arrays, if provided. It therefore adds support for custom arrays in vertexless meshes.
closes #150
PR by @Adrian-Samoticha