We are using the trial version of Aspose.3D for .NET to assess suitability for integration into a product. I’ve encountered the same error twice now on different FBX files. Both are large (6 and 9 GB respectively). The files were exported from Navisworks.
Fails with the following error:
Illegal property LayerElementMaterial while serializing NurbsCurve
And an obfuscated stack trace.
Is this a known issue?
Thanks for looking into it - I’ve downloaded the updated assemblies and these files now process correctly.
I’m not using the rendering side of things just now, but it’s good to know that you’re looking into that too!
I still have an Out of Memory exception with version 17.7 when opening an 1GB FBX file in Aspose.ThreeD.Scene.Open(…)
Smaller files (65mb) work correctly.
Is your application running as a 64-bit process?
Thanks Ben, That was the issue. I compiled it as an 64-bit application and now it seems to work.
- Edit : Unfortunatly, saving is now the issue and runs out of memory.
I haven’t tried using the Aspose saving functionality I’m afraid - my application was just extracting data from the FBX and writing to a file directly.
My 9GB FBX ended up taking 48GB of RAM for me to process (which required a significant upgrade to my PC). So you might just need to add more RAM or allocate more page file space.
Thank you for the details. We would like to recommend you, kindly send us your source FBX file, code snippet and details of the machine. We will investigate and share our findings with you.
Today I used an other machine and it turns out that, to write an 1GB FBX file takes up 20 GB physical ram and app. 10 GB of swapfile. But at least it works now
We are gradually improving the performance and memory consumption issues of the Aspose.3D for .NET API. You can share all details of the use case, so that we could log an investigation to improve this scenario specifically.
In order to test the memory consumption while writing a large FBX file, we have logged an investigation under the ticket ID THREEDNET-284 in our issue tracking system. We have linked your post to this ticket and will keep you informed regarding any available updates.