Frequently Asked Questions
Frequently Asked Questions
What is the licensing model for Aspose.3D?
Aspose.3D is distributed under the MIT License. This permissive open-source license allows for free use, modification, and distribution of the software, including in commercial products, provided the original copyright notice and license text are included. Full license details are available in the LICENSE file bundled with the project.
Is animation support available in Aspose.3D for Python?
No, animation support is not implemented in Aspose.3D for Python. While the API surface includes classes like AnimationClip, AnimationNode, and AnimationChannel, these are stubs and do not provide functional animation capabilities. This limitation is explicitly noted in the OBJ importer implementation summary.
Can Aspose.3D load texture images from files?
No, texture image loading is not implemented in Aspose.3D for Python. The library does not support loading or processing texture image files such as PNG or JPEG. This is a known limitation documented in the PyPI readiness report.
Does the OBJ importer support non-default texture coordinate mapping modes?
No, the OBJ importer only supports the default texture coordinate mapping mode. Other mapping modes such as planar, spherical, or cylindrical are not implemented. This restriction is documented in the OBJ importer implementation summary.
What are the current limitations of the FBX exporter in Aspose.3D?
The FBX exporter in Aspose.3D is basic and does not yet export normals or UVs. Additionally, the exporter raises NotImplementedError when invoked, indicating it is not yet functional. These limitations are documented in the PyPI readiness report and FBX implementation summary.
Why might _parse_element fail to advance past CLOSE_BRACKET in FBX parsing?
The _parse_element function in the FBX parser does not advance the return position past CLOSE_BRACKET when returning. This can cause parsing errors or infinite loops during FBX file parsing, especially in nested structures. This issue is documented in the FBX implementation summary as a known bug.
What happens when I try to load a deeply nested FBX file?
Deeply nested structures can trigger unbounded recursion during parsing. If you encounter a RecursionError when loading a complex FBX file, the file likely contains deeply nested scopes that exceed Python’s default recursion limit. As a workaround, increase the limit with sys.setrecursionlimit() before loading, or simplify the FBX structure in your authoring tool before export.
Which 3D formats are reliably supported for round-tripping?
The most reliably supported formats for full round-trip (load and save) are OBJ, STL (binary and ASCII), and glTF 2.0 / GLB. COLLADA (DAE) and 3MF are supported for loading. FBX loading is supported with the parser limitations noted above; FBX saving currently raises NotImplementedError. For production workflows, prefer OBJ or GLB as your interchange format.
See Also
Aspose.3D for Python has known limitations in parsing and feature support. When parsing nested scopes, elements may be added to incorrect scopes due to parser scope management issues. Deeply nested structures can trigger unbounded recursion during parsing. The library does not support animation, texture image loading, or advanced material features like multiple UV sets. These constraints affect 3D Python game and 3D Python visualization workflows.