Skip to content
This repository has been archived by the owner on Dec 4, 2023. It is now read-only.

Importer versioning #34

Closed
bqqbarbhg opened this issue Nov 1, 2023 · 1 comment
Closed

Importer versioning #34

bqqbarbhg opened this issue Nov 1, 2023 · 1 comment
Labels
enhancement New feature or request

Comments

@bqqbarbhg
Copy link
Collaborator

bqqbarbhg commented Nov 1, 2023

Describe the proposed feature and how it helps to overcome a problem or limitation

There should be some way of using the previous FBX2glTF path for older projects/assets. There will always be some subtle differences in ufbx/FBX2glTF. Especially as the imported scene graph may be depended deeply on by users any slight variation (node order, name, skeleton root, what have you), even when imperceptible when rendering, will cause compatibility issues.

These two Godot PRs might be relevant for how assets can be versioned:

Fortunately, maintaining the FBX2glTF path should not be too bothersome as it's an external application and the glTF path is kept up to date, being the preferred asset format for the engine.

It is unclear to me where this should be implemented, but just adding a tracking issue here for now.

Other information about your context or usecase.

Having an existing project with FBX files, updating to use ufbx for FBX importing would potentially cause compatibility issues with existing imported assets, where reimports would subtly change the imported scene graph.

If known, describe how your proposal will work, with code, pseudo-code, mock-ups, or diagrams

Ideally there'd be per-asset or per-project metadata for which importer to use.

Anything else

-

@bqqbarbhg bqqbarbhg added the enhancement New feature or request label Nov 1, 2023
@fire
Copy link
Member

fire commented Dec 4, 2023

Will be moving to the godot pr for merging.

@fire fire closed this as completed Dec 4, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants