Skip to content

Conversation

@yutingye
Copy link
Contributor

Summary:
After D85530152 added marker sequence support to fbx, we have functionality parity between fbx and gltf. This diff created a unified saveCharacterToFile() function in character_io that automatically selects between FBX and GLTF export based on file extension.

Added .fbx support loadMarkers as the unified function for loading marker data from any supported format.

Differential Revision: D85517572

@meta-cla meta-cla bot added the CLA Signed This label is managed by the Meta Open Source bot. label Oct 29, 2025
@meta-codesync
Copy link
Contributor

meta-codesync bot commented Oct 29, 2025

@yutingye has exported this pull request. If you are a Meta employee, you can view the originating Diff in D85517572.

@facebook-github-bot facebook-github-bot force-pushed the export-D85517572 branch 2 times, most recently from a39754d to f55895b Compare October 30, 2025 02:49
facebook-github-bot pushed a commit that referenced this pull request Oct 30, 2025
Summary:

After D85530152 added marker sequence support to fbx, we have functionality parity between fbx and gltf. This diff created a unified `saveCharacterToFile()` function in `character_io` that automatically selects between FBX and GLTF export based on file extension.

Added .fbx support loadMarkers as the unified function for loading marker data from any supported format.

Differential Revision: D85517572
facebook-github-bot pushed a commit that referenced this pull request Oct 30, 2025
Summary:

After D85530152 added marker sequence support to fbx, we have functionality parity between fbx and gltf. This diff created a unified `saveCharacterToFile()` function in `character_io` that automatically selects between FBX and GLTF export based on file extension.

Added .fbx support loadMarkers as the unified function for loading marker data from any supported format.

Differential Revision: D85517572
yutingye added a commit that referenced this pull request Oct 30, 2025
Summary:

After D85530152 added marker sequence support to fbx, we have functionality parity between fbx and gltf. This diff created a unified `saveCharacterToFile()` function in `character_io` that automatically selects between FBX and GLTF export based on file extension.

Added .fbx support loadMarkers as the unified function for loading marker data from any supported format.

Differential Revision: D85517572
yutingye added a commit that referenced this pull request Oct 30, 2025
Summary:

After D85530152 added marker sequence support to fbx, we have functionality parity between fbx and gltf. This diff created a unified `saveCharacterToFile()` function in `character_io` that automatically selects between FBX and GLTF export based on file extension.

Added .fbx support loadMarkers as the unified function for loading marker data from any supported format.

Differential Revision: D85517572
yutingye added a commit that referenced this pull request Nov 1, 2025
Summary:
Pull Request resolved: #753

After D85530152 added marker sequence support to fbx, we have functionality parity between fbx and gltf. This diff created a unified `saveCharacterToFile()` function in `character_io` that automatically selects between FBX and GLTF export based on file extension.

Added .fbx support loadMarkers as the unified function for loading marker data from any supported format.

Differential Revision: D85517572
facebook-github-bot pushed a commit that referenced this pull request Nov 1, 2025
Summary:

After D85530152 added marker sequence support to fbx, we have functionality parity between fbx and gltf. This diff created a unified `saveCharacterToFile()` function in `character_io` that automatically selects between FBX and GLTF export based on file extension.

Added .fbx support loadMarkers as the unified function for loading marker data from any supported format.

Differential Revision: D85517572
facebook-github-bot pushed a commit that referenced this pull request Nov 3, 2025
Summary:

After D85530152 added marker sequence support to fbx, we have functionality parity between fbx and gltf. This diff created a unified `saveCharacter()` function in `character_io` that automatically selects between FBX and GLTF export based on file extension.

Added .fbx support to `loadMarkers()` as the unified function for loading marker data from any supported format.

Added an additional unified `saveCharacter()` function in `character_io` that takes skeleton states as input instead of model parameters.

Rename `saveCharacter()` in `gltf_io` to `saveGltfCharacter()`, but keeping the existing ones for backwards compatibility for now. It will be removed in a later diff when downstreams are updated.

Differential Revision: D85517572
yutingye added a commit that referenced this pull request Nov 3, 2025
Summary:
Pull Request resolved: #753

After D85530152 added marker sequence support to fbx, we have functionality parity between fbx and gltf. This diff created a unified `saveCharacter()` function in `character_io` that automatically selects between FBX and GLTF export based on file extension.

Added .fbx support to `loadMarkers()` as the unified function for loading marker data from any supported format.

Added an additional unified `saveCharacter()` function in `character_io` that takes skeleton states as input instead of model parameters.

Rename `saveCharacter()` in `gltf_io` to `saveGltfCharacter()`, but keeping the existing ones for backwards compatibility for now. It will be removed in a later diff when downstreams are updated.

Differential Revision: D85517572
yutingye added a commit that referenced this pull request Nov 3, 2025
Summary:
Pull Request resolved: #753

After D85530152 added marker sequence support to fbx, we have functionality parity between fbx and gltf. This diff created a unified `saveCharacter()` function in `character_io` that automatically selects between FBX and GLTF export based on file extension.

Added .fbx support to `loadMarkers()` as the unified function for loading marker data from any supported format.

Added an additional unified `saveCharacter()` function in `character_io` that takes skeleton states as input instead of model parameters.

Rename `saveCharacter()` in `gltf_io` to `saveGltfCharacter()`, but keeping the existing ones for backwards compatibility for now. It will be removed in a later diff when downstreams are updated.

Differential Revision: D85517572
yutingye added a commit that referenced this pull request Nov 3, 2025
Summary:
Pull Request resolved: #753

After D85530152 added marker sequence support to fbx, we have functionality parity between fbx and gltf. This diff created a unified `saveCharacter()` function in `character_io` that automatically selects between FBX and GLTF export based on file extension.

Added .fbx support to `loadMarkers()` as the unified function for loading marker data from any supported format.

Added an additional unified `saveCharacter()` function in `character_io` that takes skeleton states as input instead of model parameters.

Rename `saveCharacter()` in `gltf_io` to `saveGltfCharacter()`, but keeping the existing ones for backwards compatibility for now. It will be removed in a later diff when downstreams are updated.

Differential Revision: D85517572
yutingye added a commit that referenced this pull request Nov 3, 2025
Summary:
Pull Request resolved: #753

After D85530152 added marker sequence support to fbx, we have functionality parity between fbx and gltf. This diff created a unified `saveCharacter()` function in `character_io` that automatically selects between FBX and GLTF export based on file extension.

Added .fbx support to `loadMarkers()` as the unified function for loading marker data from any supported format.

Added an additional unified `saveCharacter()` function in `character_io` that takes skeleton states as input instead of model parameters.

Rename `saveCharacter()` in `gltf_io` to `saveGltfCharacter()`, but keeping the existing ones for backwards compatibility for now. It will be removed in a later diff when downstreams are updated.

Differential Revision: D85517572
yutingye added a commit that referenced this pull request Nov 3, 2025
Summary:
Pull Request resolved: #753

After D85530152 added marker sequence support to fbx, we have functionality parity between fbx and gltf. This diff created a unified `saveCharacter()` function in `character_io` that automatically selects between FBX and GLTF export based on file extension.

Added .fbx support to `loadMarkers()` as the unified function for loading marker data from any supported format.

Added an additional unified `saveCharacter()` function in `character_io` that takes skeleton states as input instead of model parameters.

Rename `saveCharacter()` in `gltf_io` to `saveGltfCharacter()`, but keeping the existing ones for backwards compatibility for now. It will be removed in a later diff when downstreams are updated.

Differential Revision: D85517572
Summary:

After D85530152 added marker sequence support to fbx, we have functionality parity between fbx and gltf. This diff created a unified `saveCharacter()` function in `character_io` that automatically selects between FBX and GLTF export based on file extension.

Added .fbx support to `loadMarkers()` as the unified function for loading marker data from any supported format.

Added an additional unified `saveCharacter()` function in `character_io` that takes skeleton states as input instead of model parameters.

Rename `saveCharacter()` in `gltf_io` to `saveGltfCharacter()`, but keeping the existing ones for backwards compatibility for now. It will be removed in a later diff when downstreams are updated.

Differential Revision: D85517572
yutingye added a commit that referenced this pull request Nov 8, 2025
Summary:
Pull Request resolved: #753

After D85530152 added marker sequence support to fbx, we have functionality parity between fbx and gltf. This diff created a unified `saveCharacter()` function in `character_io` that automatically selects between FBX and GLTF export based on file extension.

Added .fbx support to `loadMarkers()` as the unified function for loading marker data from any supported format.

Added an additional unified `saveCharacter()` function in `character_io` that takes skeleton states as input instead of model parameters.

Rename `saveCharacter()` in `gltf_io` to `saveGltfCharacter()`, but keeping the existing ones for backwards compatibility for now. It will be removed in a later diff when downstreams are updated.

Differential Revision: D85517572
yutingye added a commit that referenced this pull request Nov 8, 2025
Summary:
Pull Request resolved: #753

After D85530152 added marker sequence support to fbx, we have functionality parity between fbx and gltf. This diff created a unified `saveCharacter()` function in `character_io` that automatically selects between FBX and GLTF export based on file extension.

Added .fbx support to `loadMarkers()` as the unified function for loading marker data from any supported format.

Added an additional unified `saveCharacter()` function in `character_io` that takes skeleton states as input instead of model parameters.

Rename `saveCharacter()` in `gltf_io` to `saveGltfCharacter()`, but keeping the existing ones for backwards compatibility for now. It will be removed in a later diff when downstreams are updated.

Differential Revision: D85517572
yutingye added a commit that referenced this pull request Nov 8, 2025
Summary:
Pull Request resolved: #753

After D85530152 added marker sequence support to fbx, we have functionality parity between fbx and gltf. This diff created a unified `saveCharacter()` function in `character_io` that automatically selects between FBX and GLTF export based on file extension.

Added .fbx support to `loadMarkers()` as the unified function for loading marker data from any supported format.

Added an additional unified `saveCharacter()` function in `character_io` that takes skeleton states as input instead of model parameters.

Rename `saveCharacter()` in `gltf_io` to `saveGltfCharacter()`, but keeping the existing ones for backwards compatibility for now. It will be removed in a later diff when downstreams are updated.

Differential Revision: D85517572
yutingye added a commit that referenced this pull request Nov 8, 2025
Summary:
Pull Request resolved: #753

After D85530152 added marker sequence support to fbx, we have functionality parity between fbx and gltf. This diff created a unified `saveCharacter()` function in `character_io` that automatically selects between FBX and GLTF export based on file extension.

Added .fbx support to `loadMarkers()` as the unified function for loading marker data from any supported format.

Added an additional unified `saveCharacter()` function in `character_io` that takes skeleton states as input instead of model parameters.

Rename `saveCharacter()` in `gltf_io` to `saveGltfCharacter()`, but keeping the existing ones for backwards compatibility for now. It will be removed in a later diff when downstreams are updated.

Differential Revision: D85517572
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Meta Open Source bot. fb-exported meta-exported

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants