OKi, closing then
You can close this, I contacted SideFX, its a bug in the Houdini exporter and not Blender. Apologies for any time wasted
Wed, Nov 14
Hm, seems I cant reproduce (a crash).
[Same for 2.79 master and 2.79b btw.]
@Sybren A. Stüvel (sybren) : mind having a look?
I have attached a simplified .abc that is still able to reproduce the crash.
Please try to reproduce with something you can share publicly.
(there might be multiple people involved in such a report and exchanging assets between all those persons via mail is just not practical).
Mon, Oct 29
We are seeing a couple of issues here (possibly we'll be splitting these in distinct reports if neccessary):
Attached is a scene from 3ds max with no animation exported as Alembic. Blender 2.8 crashes when I import this.
Fri, Oct 26
we need the updated .abc as well...
I have done a lower resolution test with the same track animation for the camera.
Interestingly, the camera is not animated in the ABC file.. That being said, it no longer crashed. Files attached
@Jesse (FreakTheMighty) : cant reproduce.
in 2.79, the provided FBX wont import Focal Length [but that is expected since rBAb890f0d7e8a6 isnt included]
in 2.79b (or onwards), the provided FBX will import Focal Length [bunch of keyframes, but all very similar -- around 8.1/8.2mm]
crashes in 2.79 as well
Thu, Oct 25
There seems to be a curve in the .abc as well (Circle.001)?
let me know if you have any issues downloading
Cannot reproduce (when exporting from blender itself)
Sep 25 2018
Not sure why, but focal length keying worked for me in Blender Version 2.79 (2.79 2017-09-11, Blender Foundation), but does not work in Version 2.79b (2.79b 2018-03-22, Blender Foundation).
Sep 19 2018
Confirmed the vertex can be read correctly by Blender and two other softwares, and Alembic regression tests are passing.
Confirmed. @Sergey Sharybin (sergey), am going to summon you here, since I believe there may be something wrong in DEG - animation is in the CacheFile datablock, hence not in Object one (as any other modifier would be). And it is never evaluated afaict, even though dependency looks correct?
Thanks dude! I hope I have time to test & commit this soon :)
Sep 18 2018
I went ahead and took the plunge into the Blender source and sure enough I fixed it! I submitted a patch at https://developer.blender.org/D3704 along with some more info on indexed writing.
I attached an Alembic file that contains a tree model with several vertex color layers. I tested it extensively in Houdini. Please test it and post back your success or failure. I hope it fixes this bug for at least Houdini and Maya.
Sep 14 2018
@Sybren A. Stüvel (sybren) that one is for you I think?
Sep 13 2018
Sep 12 2018
Please follow our submission template and guidelines, also read these tips about bug reports, and make a complete, valid bug report, with required info, precise description of the issue (only ONE issue per report!), precise steps to reproduce it, small and simple .blend and/or other files to do so if needed, etc.
Sep 3 2018
ok. you are the coder.
That’s the last time I say it: THIS BUGTRACKER IS NOT A USER SUPPORT SERVICE!
I think that it not necessary to look into the code as first thing to check. Maybe I used wrong configuration on the settings of the FBX panel,or it's necessary to use a "special" combination of settings,that I don't know. The best solution I think could be to make some attempts by the cross users,users who uses/know blender and nuke. I think that it worth trying before to close this post. If It was not strictly a bug,it was very close to be a bug,because each combination of setting should produce a different kind of effect,but since it could work only in some circumstances,it could be a bug.
You’ll have to give proof that issue is from Blender side, not from Nuke side first… afaik meshes are pretty reliable in our FBX io addon. Not our job to investigate that kind of issue, especially not with a closed-source software we don’t have access to.
Sep 2 2018
ok for the armature,but not good for the mesh. Nuke should import correctly the FBX file format.both in 6.1 ASCII and in 7.4 binary format. If it does not do it correctly,it's a bug of blender. So,I suggest to re open this bug. And anyway,the question deserves to be deepened,not closed on two feets.
Thanks for the report, but this sounds more like user support than bug to me - we don’t even know whether Nuke supports rigging at all, even less if it can import it correctly from FBX…