Attached in zip form
packed .zip (69.1 KB)
We apologize for the inconvenience caused by the validation issue. Our team has successfully reproduced the problem and has logged it in our internal bug tracker for immediate attention. We will resolve this issue in our next major version release of Aspose.3D.
Regarding the timeout issue, we recommend considering our On-Premise product, Aspose.3D for .NET, which runs locally on your hardware to take full advantage of its capabilities. You can obtain a free temporary license from https://purchase.aspose.com/buy. The On-Premise product offers more features and improved performance compared to the cloud-based version.
To convert an FBX file to GLB using Aspose.3D for .NET, you can simply use the following one-line code:
Aspose.ThreeD.Scene.FromFile(@"input.fbx").Save(@"output.glb");
Dear gentlemen,
I have not understood the meaning of your clarification.
The performance is not in evaluation but the fact of having confirmation whether your cloud service is able to provide conversion or aborts and therefore does not perform the task provided by the exposed API.
I seem to understand that the cloud product is withdrawn.
Best regards
Dear @Gpb
I want to assure you that we have no plans to discontinue our Cloud API. Instead, we’re committed to continuing its development and improvement. While we may not meet every expectation, I’d like to offer an alternative solution to our On-Premise product.
Regarding the GLB validation issue, I can confirm that we’re actively working on a fix for our On-Premise product, which will then be deployed to our cloud service once complete.
Additionally, we’re also addressing the timeout issue and expect it to be resolved soon. Thank you again for your feedback, as it helps us prioritize our development efforts.
Dear Sir,
Thank you for the information on maintaining the cloud service.
I therefore maintain the subscription to the service and its permanence as a component of the APP4AR ecosystem and associated companies and I ask you to kindly keep me updated on the resolution of the problems encountered.
The resolution of the time-out problem would already allow us to make initial use of it.
Best regards
Dear @Gpb
I’m pleased to inform you that we’ve updated the timeout parameters, and we’ve also resolved the glTF validation issues on our end.
We’re planning to deploy these updates next Monday, shortly after the release of our .NET product. This new version focused on glTF and IFC support.
Thank you for your patience and understanding as we continue to enhance our API offerings!