Import and Export of glTF Format and Save Dependencies of a 3D Scene in the Real File System using Aspose.3D for .NET 16.11.0

Share on FacebookTweet about this on TwitterShare on LinkedIn

Aspose.3D for NET APIs

We are pleased to announce the availability of new version 16.11.0 of Aspose.3D for .NET API. The new version adds support of GL Transmission Format (glTF). Developers can import glTF files into the Aspose.3D API, and then export them in any supported 3D format. Developers can also save all dependencies of a 3D scene in the real file system. The GL Transmission Format (glTF) is an efficient, extensible, interoperable format for the transmission and loading of 3D content. Developers can install Aspose.3D Nuget package in their .NET applications because we publish each version as a NuGet package on the NuGet gallery. We recommend our clients upgrade old version of the Aspose.3D API to this latest one. For details on API fixes, please check Release Notes having a complete list of the features, enhancements and bug fixes.

Import and Export 3D Scenes from/to glTF Format

Using Aspose.3D API, developers can now convert any supported 3D file to glTF format, and vice versa. The GL Transmission Format (glTF) is a runtime asset delivery format for GL APIs. Being an open standard, it fills a real and growing need to bring 3D assets quickly and efficiently to a wide variety of platforms and devices. Please check these help topics to set load and save glTF settings: Use of the glTF Load Options and Use of the glTF Save Options

Retrieve Dependencies of a 3D Scene and Save them in the Real File System

Aspose.3D API allows developers to retrieve all dependency files from a 3D model, and then write them in the real file system or simply discard. There are three ways to save dependency files as define a path of the local directory, save in the MemoryFileSystem class object and simply discard saving dependencies. The FileSystem property is added to all save option classes. These articles show how developers can save dependencies of a 3D scene: Save Dependencies in the Local Directory, Save Dependencies in the MemoryFileSystem Object and Discard Saving the Material Files

Public API Changes

The following API changes in the new version are also worth noting:

  • Aspose.ThreeD.Formats.GLTFLoadOptions class has been added. It helps in importing glTF files into Aspose.3D API.

  • Aspose.ThreeD.Formats.GLTFSaveOptions class has been added. It helps in saving a glTF file.

  • GLTF and GLTF_Binary format entries have been added in the Aspose.ThreeD.FileFormat class for loading and saving purposes.

  • An Extension property has been added in the FileFormatType class to get the extension name of the file format.

  • Aspose.ThreeD.Utilities.DummyFileSystem class has been added. It helps to discard saving the dependency files of a 3D scene.

  • Aspose.ThreeD.Utilities.LocalFileSystem class has been added. It helps to save dependency in the Local directory.

  • Aspose.ThreeD.Utilities.MemoryFileSystem class has been added. It helps to save dependency file in the MemoryFileSystem class object.

  • The AddEntity method has been added in the Aspose.ThreeD.Node class. It gives a shortcut way of adding an entity to a node.

Aspose.3D for .NET Resources

The following resources will help you work with Aspose.3D for .NET:

We hope you’ll enjoy this new release that save time and efforts. The API is quite simple and developers can use it in application easily.

convert 3d files