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.
For posterity, APIs that are still experimental:
meshopt_generateProvokingIndexBuffer
: added in this release, unclear if it will need changesmeshopt_EncodeExpClamped
enum: added in this release, unclear if it will stay (cutoff fixed to 0) or be replaced bymeshopt_encodeFilterExpClamped
function (customizable cutoff)meshopt_SimplifyPrune
enum: added in this release, implementation is still in flux with likely behavior changes in future releasesmeshopt_simplifyWithAttributes
: a lot of implementation changes in this release; while the implementation should be relatively stable, it's unclear if interface changes will be needed for at least one planned featuremeshopt_simplifySloppy
: hasn't changed in a few releases but significant implementation work may be outstandingmeshopt_simplifyPoints
: a few implementation changes in this release; likely effectively stable, unless we decide we need to support RGB/RGBA modes which would need an interface change to specify if the input color is 3-float or 4-floatmeshopt_optimizeMeshlet
: no changes since last release, but would like to wait for one more release to stabilize in case clusterizer sees significant changes in the next release.meshopt_spatialSortTriangles
: no changes in a while;meshopt_spatialSortRemap
has been stabilized and is useful for point clouds, but there's some issues with sorting triangles for compression efficiency that I'd like to look into before stabilizing this, as right now it's unclear if the triangle sort is practically useful.As a reminder, "experimental" means the interface or implementation may see significant change; non-experimental means interface is de-facto locked down (both API/ABI) and implementation should be production ready, but future releases may still improve behavior/performance in a compatible manner. Experimental APIs are still fine to use, it's just that the compatibility isn't guaranteed.
meshopt_generateProvokingIndexBuffer
,meshopt_simplifyWithAttributes
,meshopt_simplifyPoints
andmeshopt_optimizeMeshlet
will most likely become stable in the next release.