[BUG] Fatal Error when importing older fbx format

Build Info Version: beta 1808360

Install Path: C:/Rocket

Specifications

OS: Windows 8 pro
Ram: 4 gb ddr3 ram
Graphic Card: NVIDIA GEFORCE GT 630 / 2 GB
CPU: Intel i5 2450 m @ 2.5ghz
Uac Status: on

Description:

I had an old FBX file which I wanted to use in my level. I thought of importing it without upgrading the file version. Normally Unreal will import an old file version after displaying a warning. But the editor displayed a Fatal error message and exited. without giving me a chance to save any changes.

Repro Steps

  1. Import a file in content browser
  2. selected fbx file
  3. imported the file…message displayed pressed ok
  4. new warning message displayed pressed ok
  5. fatal error window message displayed

vlcsnap-2013-09-24-13h14m14s129.png

alt text

Hi Ajay,

Is this the only FBX file that you have which was exported with an older version? If you have other files, have you attempted to import them as well?

I ask because in our tests we can successfully import FBX assets that were exported with older versions. For instance, I just successfully imported an FBX into Rocket that was also made with version 6.1.0

Whatever is causing the crash is most likely something unique to the asset. We would be interested in knowing the conditions under which the asset was made or exported if you have any more information available.

Thanks

Hi Stephen,

The fbx file I had used was made with Sketchup 8.0.4811. As you suggested I used another file. This time I made a box (Simple box without any texture). Same problem occurred during the import. But later I used google sketchup 2013 for exporting the same file. The FBX worked fine. If you want a recorded video of the whole process I can send it to you.

Regards

Ajay Chaudhary

Thanks for the information. Could you please send us the FBX for the box made with 8.0.4811 that crashes?

link text

Excellent, thank you. I did experience the crash in Rocket with the asset, but luckily it did not occur in our more recent internal build. This should indicate that the issue has been addressed since the release of Beta 4 and is expected to not occur in future builds.

Thanks!

One more thing… you made this post Private, but it contains no sensitive information. Do you have any objection to me making this Public, so that others can view it?

ok no problem