Cannot call Scene.Save or Open

Aspose.3D Product Family
1
Hello,

I tried to save/open fbx file (my own or with unchanged sample project provided by you) and in both cases I got exception bellow. Any suggestion what I did wrong? I tried to reinstall Aspose.3D package, but this was not an solution. Currently I have dll with version 1.5.0.0.

Thanks in advance...

System.TypeInitializationException was unhandled by user code
Message=The type initializer for '#=qxAvFpqX7TzdIbxUhebYXE$berOCafQjRfpQ65VqFaIx8VyvqvPeSiJESitXZITHl' threw an exception.
Source=Aspose.3D
TypeName=#=qxAvFpqX7TzdIbxUhebYXE$berOCafQjRfpQ65VqFaIx8VyvqvPeSiJESitXZITHl
StackTrace:
at #=qxAvFpqX7TzdIbxUhebYXE$berOCafQjRfpQ65VqFaIx8VyvqvPeSiJESitXZITHl.#=qjCe2DPuEs2_ScJkEknn3nG5vzxefIZasm2I9D7AG7oc=(Int32 #=qauz4QUeWFsxOK1bwiAoAGg==)
at #=qJV3ODnNceGcQSHujYPfuzxYUA$fzcnBVNrX04JpY5e7HBWCmTw_EzTGFRBQUIaJJ.#=qe7YLX2VV6oYrrAG_iwHY7g==(FileFormat #=qx2c9jcGi_hkxpKQRZb2JMg==)
at #=qtph6FQDXdAhx1VpDa_FXpahWE6uX8e8vZw3juANPl9g=.#=qMZQgkGyltKfDZ4Vv6VgcOQ==(Scene #=qKW7UV7IILDnzEPsZeZN$bA==, Stream #=qcQkVg3wmeNxU$B5y$RuJFQ==, IOConfig #=qwQvRpa5xQm2CnHLOdVV8lg==)
at Aspose.ThreeD.Scene.Open(Stream stream, IOConfig config)
at Aspose.ThreeD.Scene.Open(String fileName)
at AsposeDemo.WebForm1.Page_Load(Object sender, EventArgs e) in S:\Studio9\DX10\AsposeDemo\AsposeDemo\WebForm1.aspx.cs:line 18
at System.Web.Util.CalliHelper.EventArgFunctionCaller(IntPtr fp, Object o, Object t, EventArgs e)
at System.Web.Util.CalliEventHandlerDelegateProxy.Callback(Object sender, EventArgs e)
at System.Web.UI.Control.OnLoad(EventArgs e)
at System.Web.UI.Control.LoadRecursive()
at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
InnerException:
Message=Input string was not in a correct format.
Source=mscorlib
StackTrace:
at System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
at System.Number.ParseDouble(String value, NumberStyles options, NumberFormatInfo numfmt)
at System.Double.Parse(String s, NumberStyles style, NumberFormatInfo info)
at #=qFFHGZ4pUb0fNIWqAhBt2cjAgt8pMJvgrCqr88REyO9GRfpQNkP5d8N7nxJ4yKMfd.#=q_CbNH8aV4BZ8jkV3ocdR7Q==(String[] #=qePa8dXU4ox7gkokjI2Ysbg==, Int32 #=q9TExCYtaDgTdKQglL3x5WA==, Int32 #=qaECEi2Tb2$LAt6oetWjrbw==)
at #=qFFHGZ4pUb0fNIWqAhBt2cjAgt8pMJvgrCqr88REyO9GRfpQNkP5d8N7nxJ4yKMfd.#=qfPy9R0y78_mFJFOPV2vlSveXouIsyqQiRi9eBeOcK9o=(String[] #=qePa8dXU4ox7gkokjI2Ysbg==, Int32 #=q9TExCYtaDgTdKQglL3x5WA==, #=qV3KOaORr_huqIafWzN8VKUoNUfq2aRT_ENpoGIH4X4AvuajdL98JGmj55G_F6yys #=qM4I761PxGRgOq1dPSLRafA==)
at #=qFFHGZ4pUb0fNIWqAhBt2cjAgt8pMJvgrCqr88REyO9GRfpQNkP5d8N7nxJ4yKMfd.#=qVeHUIPEsMzBSf_aoAeDD_A==(#=qtz$HOt5lASFB1AXREc0nKdseZ2Am5IHYF_9C6hr2VORT7sb3U3DagaPt$IoH4t$M #=q_RV7aybg_WFoObAkdIJhUA==, String[] #=qePa8dXU4ox7gkokjI2Ysbg==)
at #=qFFHGZ4pUb0fNIWqAhBt2cjAgt8pMJvgrCqr88REyO9GRfpQNkP5d8N7nxJ4yKMfd.#=qwyySpsVvidoW$5YlsD108w==(String #=qdlL1uJU$x2ACrbD7LNihQg==)
at #=qRO89Cec3A1bAnCF2svUPVzLPII$qQXOg9TFrMu2k1myVKPdGrc9gnofyx1pb2JsF..ctor()
at #=qxAvFpqX7TzdIbxUhebYXE$berOCafQjRfpQ65VqFaIx8VyvqvPeSiJESitXZITHl..cctor()
InnerException:
2

Hi Jindřich,


Thank you for contacting support. Please give your source FBX file and also navigate us to the provided sample project. We’ll investigate and reply you appropriately. You may prepare an archive (ZIP) of the source FBX document before attaching it to your post. Your response is awaited.

3

Attached zip with fbx and project

4

Hi Jindřich,


Thank you for supplying a source FBX file and project archive. The NuGet added references were targeting to framework 4.5 and the application was targeting to framework 3.5. We upgraded the target framework of the application to 4.5. It is throwing a NullReferenceException. We’ve logged this problem under ticket id THREEDNET-166 in our bug tracking system. Your post has also been linked to this ticket. We’ll keep you informed regarding any available updates. We’re sorry for the inconvenience caused.

Furthermore, we could not reproduce the same error message as you narrated in your first post. Please provide details of your working environment, e.g. Operating System name and edition, local language settings, .NET Framework or any other information that you think is necessary. It’ll help us in replicating the same error message on our side.

5

Hi Jindřich,


Thank you for being patient. We have a good news for you that the issue id THREEDNET-166 has now been resolved. If there is no issue in the QA phase, then this fix will be included in the next version of Aspose.3D for .NET 1.6.0. We’ll inform you via this forum thread as soon as the new release is published.

6

Hi, just to complete your question, I tried it on win10 and w2008r2 server, same result.

Is there any way to get update sooner? We need to decide if we use your dlls in our 2 upcoming projects. Without creating renders (need to create few png images from fbx) we cannot made decision about purchase

Kind regards Jindrich

7

Hi Jindřich,


Thank you for the details. We’re just finalizing the latest version 1.6.0 of Aspose.Diagram for .NET API. It is expected to come out in a couple of the days. We’ll notify you once it is available for the public use. Please spare us a little time.

8

The issues you have found earlier (filed as THREEDNET-166) have been fixed in Aspose.3D for .NET 1.6.0.

This message was posted using Notification2Forum from Downloads module by Aspose Notifier.
9

Hi,

I just setup new console project with latest Aspose.3D nugget (1.6.0.0) however issue still persist. I tried my previous code without no luck, so I decide to setup new console project with same result. Tried with .NET 3.5 and .NET 4.0. Still same fix file as was provided before.

10

Hi Jindřich,


Thank you for the inquiry. It appears as the problem is specific to the working environment. Please prepare a simple console application which reproduces the issue on your side and attach its zip archive to your reply post. We’ll run and closely observe that application on our side and let you know about our findings.

11

Before I post project, can this be caused by parallels virtual environment, both my windows computers are hosted on MacBook using parallels virtualization…

12

Hi Jindřich,


Thank you for the inquiry. Well, it should not be the problem of virtual environment. We suspect that obfuscation could be the cause of this. Please make sure that you have not changed the source FBX against the version 1.6.0 (as shared earlier). If it still throws an error as narrated in your first post, then please provide a sample project. We need to properly investigate this issue at our end.

13

Hi Jindřich,


Thank you for being patient. We have uploaded the version 1.6.1 of Aspose.3D for .NET API. It has internal bug fixing caused by the obfuscation. Please download and use it in your project and let us know how that goes on your side.

14

First of all, thanks for your support. I tried 1.6.1 on 2 test projects (web and console app) and still same error (maybe type signature is different, but error is same). I attached test console project, fbx file same as before.

15

Hi Jindřich,


Thank you for posting a sample project. We’re sorry to share with you that we could not reproduce the error message at our end. We have tested your project in the Windows 10 Professional 64 bit. We need to be more specific. Did you try to check this problem on another computer? If not, then please try on any other machine. Meanwhile, we’ll check this issue in details and let you know about our findings (if any).

16

Hi Jindřich,


Thank you for being patient. We managed to reproduce this error by changing the system region format to Albanian (Albania). We’ve logged this error under ticket id THREEDNET-173 in our bug tracking system. Your post has also been linked to this ticket. We’ll let you know once a significant progress has been made in this regard. We’re sorry for the inconvenience caused.

17

Hi Jindřich,


Thank you for being patient. In reference to the ticket id THREEDNET-173, please download and use the latest Hotfix version: Aspose.3d for .NET 1.6.2.0. Please also let us know how that goes on your side.

18

1.6.2 version is ok on .net and w2008 server, thanks. I will do some test if I can reach goal what I need. Thanks for your support

19

Hi Jindřich,


Thank you for the confirmation. It is nice to hear from you that the hotfix version 1.6.2 works perfect on your side. Please let us know in case of any further assistance. We’ll be happy to help you.

20

The issues you have found earlier (filed as ) have been fixed in this Aspose.Words for JasperReports 18.3 update.