I was implementing 3D conversion using ASPOSE cloud API. GLB to USDZ is working fine, but we also need USDZ to GLB/GLTF. When I tried to do this, I encountered some errors:
GLB as a file format is not accepted. Screenshot attached:
image.png (41.4 KB)
For GLTF, the generated file is not visible in any online GLTF viewer and it says: ‘THREE.GLTFLoader: Unsupported asset. glTF versions >=2.0 are supported.’ Screenshot attached:
image.png (24.9 KB)
How to fix these issues? Can anyone help me?
To resolve the issue with the GLTF conversion using the ASPOSE Cloud API, use gltf2_binary as the format. This should ensure compatibility with GLTF viewers supporting glTF version 2.0 and above.
I’m trying to convert obj to gltf. I tried d ALL the suggested gltf format (gltf gltf2 with and without binary). The result is not correct.
Would you be so kind as to provide the source file?
No code, I’m just using Aspose.3D Cloud API Reference. The converted file is created fine but when downloaded the conversion is wrong. I have tested many different obj models. It’s very easy to reproduce the test. Here is obj model to test attached a very simple model. You can try Many thanks
It is important to understand if the service offered by Aspose, to which I have signed up for a paid account, is actually able to convert .obj and possibly .fbx to gltf2_binary.
I have currently uploaded a obj verified with blender that works perfectly and that has correctly produced the .glb file when using blender. When trying to do the conversion with Aspose cloud using API (without codes but using the exposed APIs) the procedure stops after about 1 minute with the following message “Undocumented TypeError: Failed to fetch”.
Used storage linked to Azure storage .
It is impossible to use internal storage because the upload completes but the file does not appear. It is a stressful situation.[
trying api reported error]
(https://arstorage.blob.core.windows.net/eqtaspose/err.png)
We apologize for this and are currently investigating and fixing the API.
I have reviewed the image file you provided and noticed that the filename you entered as ‘newfilename’ contains an error. Since the format of your new file is GLTF, the filename should end with the ‘.gltf’ extension to ensure consistency with the file type. Additionally, I tested the file you provided and confirmed that the conversion process was successful using this format.
I am sorry to have to report the non-functioning.
Given that if the conversion is for the binary version the correct extension should be glb and not gltf which instead applies to the text version and this incorrect use of the extension causes problems in the viewers.
However, I performed the conversion as indicated and the result is as per attached snapshot no.1.
The test uses the linked storage in Azure named “arstorage”.
For testing drone_costom.obj works but it is a tiny file.
More significant is to try the conversion on the one indicated in the example.
If there are size limits please indicate this information to verify if your service is practically usable for our needs.
Assuming a problem related to external storage, I try to upload (snapshot 2).
Once the uploading is finished (no error or warning) it seems without problems, performing a subsequent refresh the file does NOT appear in the internal storage. (snapshot 3).
I then try to upload via the API (put).
Very long execution times (?)
Upload via PUT fails (snapshot 4).
However, our preferred use is for external storage on Azure.
I deleted the small obj on internal and external storage.
If you wish to try a test,you should select the only .obj left on external storage.
I also left a .fbx on which in my opinion the conversion service still fails.
It would be enough for me to work on .obj.
Thanks and sorry.
Best regards.
G P Barabino Equi Technologies Int, USA
[No.1 ](https://arstorage.blob.core.windows.net/eqtaspose/test_after_email 24032025 no 1 .png)[no 2](https://arstorage.blob.core.windows.net/eqtaspose/test_after_email 24032025 no 2 .png)
[no 3](https://arstorage.blob.core.windows.net/eqtaspose/test_after_email 24032025 no 3 .png)[no 4](https://arstorage.blob.core.windows.net/eqtaspose/test_after_email 24032025 no 4 .png)
I apologize deeply for this. If the format of your file is GLTF2_Binary, the file extension should be “.glb”. I have tested using the file you provided and obtained correct conversion results. Thank you for your feedback.
Best regards.
Thank you but despite countless attempts, we are not able to obtain conversions. On small files the system works (about 15Mb).
But on a file of about 140 Mb (small for ur apps) we get errors of various types, from time out to internal errors.
Unfortunately, I have to abandon your solution for our ecosystem (app4ar.com).
If we do not receive updates from you tomorrow we will unfortunately cancel the subscription.
Kind regards
I apologize deeply for this.We are actively working on this issue.
I apologize deeply for this.We have solved the problem of errors when uploading large files with put requests and have updated it. We are currently preparing to expand memory to resolve the issue of large file conversion failures.
Many thanks. Please inform us when it will be possible to:
Dr. G P Barabino
Equi Techonologies Int. USA
(CTO)
We sincerely apologize for any inconvenience this may have caused!
We are pleased to inform you that the expansion of our server storage has been fully completed, and we now support processing large files. To ensure optimal efficiency and stability, we recommend keeping file sizes under 500MB. We have fixed the bug of converting from .fbx format to other formats.
We would like to reiterate our sincere apologies for any earlier issues and thank you for your understanding and support!
Dear Sir,
Thank you for your kind cooperation.
I have carried out a series of tests.
There is an improvement but problems remain.
Best regards
Equi Technologies Int. USA
Dr. G P Barabino
(CTO)
err 504 Time-out.png (43.2 KB)
Thank you for your support and understanding, we are actively working on the issue of incompatibility of generated glb files.
Hello! Thank you for your continued support and patience. We have completed the update , and we are confident that this optimization will effectively resolve compatibility issues, ensuring a more stable user experience for you.
Thank you for your kind cooperation.
I repeated the series of test .
- OBJ CONVERSION:
The time out remains. See attachment.
About this issue I may suggest :
A timeout in Nginx occurs when the server doesn’t receive a response from an upstream server or client within a specified time limit.
To resolve timeout errors, you can adjust the timeout settings in the Nginx configuration file.
http {
proxy_connect_timeout 60s;
proxy_read_timeout 60s;
proxy_send_timeout 60s;
send_timeout 60s;
}
reload nginx
…
- FBX conversion: generates a non-compliant glb. I added the failed validation reports .
I understand the difficulties but unfortunately the errors remain.
At your disposal.
Kind regards
Equi Technologies Int. USA
(CTO)
.
27-03-2025 time-out err.png (57.7 KB)
fbx validator errors.png (10.5 KB)
(Attachment stall validator errors .glb.report.json is missing)