Unable To Import Alembic File Into UE4(4.16) from Houdini16

Hello People,

We are having some issues bringing in an alembic file into UE4, which I detail below Please Help!!!

Objective:

We are trying to get an alembic cache file from Houdini 16 into Unreal Engine 4.16.3. The alembic is a FLIP fluid White Water which has been surfaced/meshed, and has a frame range of 24 frames for this test.

Problem:

UE4 importer does not want to import the asset, giving an error message and stating to check the Output log. Upon clicking Import, selecting the file, and importing, it refuses to cooperate, and does not bring up the Importer Dialog box for the imported asset, only showing an error window instead.

We’ve successfully imported a FLIP fluid simulation into 4.16 in the past, but we have been unsuccessful in replicating the same results of victory so far! We know it is possible to import it as we have done so, so we are very stumped as to what it could be that makes the UE4 importer not bring in any further fluid abc files.

I’ve attached some screenshots below of what we’ve been looking at for the last few days.
We’ve successfully imported some basic files like a cube and cached it into an Alembic with nothing else added, as vanilla as can be, and that worked so long as we checked the option to remove empty frames and made it a Geometry Cache and not Static Mesh.

So what do I do to get this alembic in finally and make awesome stuff?!?

I would really appreciate any and all help because this is very bewildering as to why some alembics are imported just fine and others are not.

Thanks a ton!

PS. Even if you have had this issue in the past, just reply here so we know we’re not the only one’s out there with the same issues!

Here’s what we’ve been seeing:

UPDATE # 1:

Hello, so it would appear our issue has been resolved, “seemingly”, for the time being.

1 - In a brand new empty scene, and creating a Geo node at the scene level, go inside it.
2 - Inside the Geo node, create a “File” node (and NOT a “File Cache” node) appears to have made the difference and is giving consistent working results.

However, out of curiosity, I tested the File Cache node as well and that worked too, so I’m still not sure why the file node is working, but it is. We spent the last 2-3 days trying to resolve this, but its working now!
If anyone finds out what the real culprit is, let us know!

For anyone who has the same issue, you can comment on here and ask questions as the post is being followed.