You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
For 3mf, a triangle corresponds to 3 vertices, each vertex has a corresponding attribute, that is, the same vertex in different triangles, its attribute value is different, and the existing data structure, only consider one vertex in all triangles, its attribute is the same. Therefore, it is necessary to upgrade the data structure to meet the development needs
Describe the solution you'd like
Set the attribute index, and then associate the attribute value. The pseudo-code is as follows
struct aiFace {
//! Number of indices defining this face.
//! The maximum value for this member is #AI_MAX_FACE_INDICES.
unsigned int mNumIndices;
//! Pointer to the indices array. Size of the array is given in numIndices.
unsigned int *mIndices;
//Associated with mNewColors
unsigned int *mColorIndices;
//Associated with mNewTextureCoords
unsigned int *mTextureIndices;
......
}
struct aiMesh {
......
//new add
unsigned int mNumNewColors;
C_STRUCT aiColor4D *mNewColors;
unsigned int mNewTextureCoords;
C_STRUCT aiVector3D *mNewTextureCoords;
......
}
Describe alternatives you've considered
Upgrade plasticity with new data structures
Additional context @kimkulling I'd like to hear your opinion, or is there a better way to implement it
The text was updated successfully, but these errors were encountered:
@GalenXiao I think in this case, the vertices for each face should not be the same. Even if they have the same position, they should have different indices.
Vertices should only be identical if and only if all their attributes are the same
(Same Position & Same UV & Same Color)
Some formats will let vertices share same individual attributes (i.e. OBJ file format uses indices into positions/normals/texture coords), but I feel like more recent formats have begun to make vertices share all attributes.
What is the downstream use case for changing the data structure?
Is your feature request related to a problem? Please describe.
For 3mf, a triangle corresponds to 3 vertices, each vertex has a corresponding attribute, that is, the same vertex in different triangles, its attribute value is different, and the existing data structure, only consider one vertex in all triangles, its attribute is the same. Therefore, it is necessary to upgrade the data structure to meet the development needs
Describe the solution you'd like
Set the attribute index, and then associate the attribute value. The pseudo-code is as follows
Describe alternatives you've considered
Upgrade plasticity with new data structures
Additional context
@kimkulling I'd like to hear your opinion, or is there a better way to implement it
The text was updated successfully, but these errors were encountered: