Klimczak.Jan Posted November 28, 2017 Share Posted November 28, 2017 (edited) Hi, I observed that Editor2 crashes from time to time when I modify fbx file stored in asset directory. Step to reproduce: 1. Save fbx file somewhere in asset directory. It should be automatically loaded into Editor2 (you will see it in logs - if no, then you should activate windows with Editor2 by clicking somewhere in it or you can just import it). 2. Make changes to fbx file by external application (I do some changes with skeleton, bones and skin) and save this file (it should be the same file as in point 1). 3. Give focus for Editor 2 by clicking somewhere in it. It will reload automatically changed fbx file. At this moment from time to time Editor2 crashes. If will not crash for you then you should after point 3 repeat again from point 2 then 3 ... 2,3,2,3, ... Usually it is enough to do it once, twice or just a few times to crash Editor 2. Thank you Edited November 28, 2017 by Klimczak.Jan Link to comment
vvvaseckiy Posted November 29, 2017 Share Posted November 29, 2017 Hello, Unfortunately, we were unable to reproduce this issue. Could you please specify exact software you are using to edit skeleton, bones and skin. And, if it is possible, provide us .fbx which was used when you experienced Editor 2 crash. Thank you! 1 Link to comment
Klimczak.Jan Posted November 30, 2017 Author Share Posted November 30, 2017 (edited) On 29.11.2017 at 12:58 PM, vvvaseckiy said: Hello, Unfortunately, we were unable to reproduce this issue. Could you please specify exact software you are using to edit skeleton, bones and skin. And, if it is possible, provide us .fbx which was used when you experienced Editor 2 crash. Thank you! Hello, I am using Maya 2015 with SP6 installed (full version, not LT). The problem exists only for FBX with skinned mesh. I am exporting it into FBX 2014 format. I attach sample .fbx files. You can just update them to crash Editor 2 (switch or replace a files on the disk in assets folder). Thank You model.fbx model.fbx Edited November 30, 2017 by Klimczak.Jan Link to comment
vvvaseckiy Posted December 5, 2017 Share Posted December 5, 2017 Hello, Thank you for your feedback. We've added this issue to our internal bugtracker and will fix it in our future releases. Thank you! 1 Link to comment
Recommended Posts