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
This commit was created on GitHub.com and signed with GitHub’s verified signature.
What's Changed
Add support for CMF file format with carbon-mesh
Integration with Granny SDK itself is now optional, controlled by a CMake option.
The following Granny-related classes were removed from Trinity:
Tr2GrannyVector3Curve - not used anywhere
EveShip2Builder - potentially used in Tech3 ship pipeline, but the code does not belong to Trinity and should be re-created in Carbon Mesh
Tr2NamedPipeListener - not used
Tr2GRNMemoryPersist - not used
The following classes do not support .cmf file format, are not available when building Trinity without Granny support, and should be considered deprecated: Tr2GrannyTrack, Tr2GrannyEventTrack, Tr2GrannyTransformTrack, Tr2GrannyVectorTrack
GState support (Tr2GStateAnimation) is still Granny-only; it is planned to provide the .cmf replacement for it in the future.
Python-exposed function trinity.GrannyRayIntersection only supports .gr2 files and is deprecated. Use TriGrannyRes.RayIntersection instead.
Python-exposed functions EveSpaceObject2.CalculateSkinnedBoundingBoxFromTransform and EveSpaceObject2.CalculateSkinnedBoundingSphere work differently for .cmf files: instead of performing CPU-side skinning to determine the exact bounds, they return approximated bounds based on the space object's dynamic bounds.
Add SaveToCMF methods to Tr2ParticleSystem and Tr2RuntimeData (work exactly like their SaveToGranny functions, but save to .cmf format).
Add multiple getters to TriGrannyRes to inspect geometry files. These methods work with both .gr2 and .cmf files.