- User Since
- Jan 18 2018, 1:18 AM (86 w, 6 d)
Thu, Aug 22
Thanks for letting me know - and the link to the limitations page.
Jul 26 2019
Thanks again for the information, Sergey. I had no idea that you could play back subframes - this does show that there is some weird mojo happening in this animation, sometimes with the armature doing a full 360 degree rotation in one frame. I'm guessing this is due to something breaking in the FBX import of the animation, as once you look at the curves (focusing on the Hips bone) it's obvious what's going on.
Jul 25 2019
Thanks for the reply, Sergey. This is good information ... that I've never run across. I went ahead and did some tests to see what worked and what didn't, and I've found that it's not necessary to disable AutoSmooth - but you DO have to click the "Add Custom Split Normals Data" button under "Geometry Data". This is a detail that I don't think I've ever run across (not that I'm a Blender Guru), but it seems important enough that there should be a pop-up warning when someone goes to render an animation with Autosmooth enabled, without Custom Split Normals Data added to a mesh. The reason behind this is that anyone coming into Blender/Cycles who doesn't know this requirement is going to write off Cycles as a renderer almost immediately - *I* was getting close to giving up on it. The difference in blur quality is dramatic:
Jul 22 2019
Roger that ...
That would have been nice if that's what was causing it ... but it looks like that's not the (only) issue since after cleaning up the model with the 3D print tool, I still get the same rendering artifacts:
Jul 21 2019
Jul 17 2019
May 31 2019
Feb 22 2019
Ah - Thanks - what I get for following someone else's example without really LOOKING at it.
Jan 22 2019
Agreed - it's very likely it's the same underlying cause. FWIW, I didn't see the same behavior in 2.79, so it's something new.
Nov 27 2018
I can confirm this on the Windows build as well (failure to import OBJ files) - Windows 7 X64
Nov 22 2018
Jul 11 2018
Appologies for not including the graphics card with the report.
Jul 10 2018
Feb 21 2018
I forgot to add that this is Blender 2.79 Cycles running on Windows 7 64-bit using an nVidia GeForce 980 GTX ti for rendering.
Jan 22 2018
I think it might have something to do with Softimage's bones having "roots" and "effectors" by default. If I export the FBX without the roots and effectors, I get a different result - still broken, but different.
Jan 18 2018
Absolutely! Anything to bring Blender's FBX compatibility up to par. I'm seriously considering migrating to Blender for my work and FBX compatibility is critical for me. This would be a huge PLUS in Blender's favor :)
Sorry - that RAR is a Version 5 archive - incompatible with version 4 (so you need the updated WinRAR).