search

o3de / sig-graphics-audio

Documents and communications for the O3DE Graphics-Audio Special Interest Group
12 stars 14 forks source link

.gltf support #19

Open WashedUpStudio opened 3 years ago

WashedUpStudio commented 3 years ago

Summary:

Support for .gltf files so developers will have the choice of multiple file formats that should work nearly the same. .fbx and .gltf work very close to the same for what they have inside of the file that would be used by the o3de engine.

What is the relevance of this feature?

The support for .gltf is important to me because fbx support on an open source project is always going to be time consuming especially if fbx got an update in the future. .gltf on the other hand is open and assimp has great support for it already so a lot of the features that one would need already work at least at a visual level when imported.

What are the advantages of the feature?

The advantages of using .gltf over .fbx is that .gltf is faster than .fbx for loading and unloading, and that greatly increases if you use the binary version of .gltf.

What are the disadvantages of the feature?

Some disadvantages is it is hard to scale an export of a .gltf file since most applications I have tried does not allow to scale the exported asset.

How will this be implemented or integrated into the O3DE environment?

The great thing about this feature is it can already be integrated by using assimp.

Are there any alternatives to this feature?

The only other alternative I know of is .fbx files, and the support for them in any open source software is rough around the edges, but for O3DE it is getting better daily so in the future this should also be a reliable source.

Are there any open questions?

What platforms if not all would this be able to support?

For more information on this topic go to the issue page where it all started: https://github.com/o3de/o3de/issues/3058

HogJonny-AMZN commented 3 years ago

Here is an open discussion thread to capture requirements (and plan compatibility): https://github.com/o3de/o3de/discussions/3750

It's not as easy as just turning on the file format type in assimp, there is a lot of additional plumbing an implementation required.

We can revise this RFC after we have a better understanding of how customers and the community expect to work with glTF2+ data.