LogSerialization: Warning: Memory map bulk data failed error

Engine: Unreal Engine 5.6.1
Platform: Android (Meta Quest 3)
ConvAI Plugin Version: v3.6.9-hotfix2

MyProject.log (146.5 KB)

Hello, this is a continuation of this post I made a few days ago. I downgraded my version of ConvAI and got the application running on the Meta Quest succesfully, but I’m having a new issue. As soon as the application loads and the Metahuman I have set up spawns into the world, they immediately start floating upwards forever until they vanish from sight, which isn’t something that ever happens in editor. Again, I’m pretty sure this is because of Convai, due to the application logs I’m seeing:

[2026.02.23-20.15.19:351][ 0]LogSerialization: Warning: Memory map bulk data ‘/ConvAI/MetaHumans/Animations/Motions/Talk/MH_Talk’ FAILED
[2026.02.23-20.15.19:351][ 0]LogSerialization: Warning: Memory map bulk data ‘/ConvAI/MetaHumans/Animations/Motions2/FP/Idle/FP_IdleBase’ FAILED
[2026.02.23-20.15.19:351][ 0]LogSerialization: Warning: Memory map bulk data ‘/ConvAI/MetaHumans/Animations/Motions2/FP/Jog/FP_Jog_F’ FAILED

I get a few dozen more error messages like this, but all relating to a memory map failure with convai animations. The full logs are attached if needed. I believe I’ve ruled out physics collisions as a possible cause, as I disabled collisions and enabled gravity wherever possible on every part of my Metahuman blueprint, to no avail. I tried applying the patch found in this thread, though that issue was a bit different than mine, but this also had no effect beyond making my Metahuman deformed as well as floating upwards forever. Has anyone else had this issue, or know what might be causing it?

Hello,

Does this floating behavior also occur while the MetaHuman is walking or running, or only when it first spawns and stands idle?

Only when it first spawns and stands idle, as far as I can tell. I’ve yet to add any movement functionality to my Metahuman, I just need him to stand still and verify that the Convai portion works properly in AR for now.

Is this issue happening only on Meta Quest, or does it also occur in the editor?

Only on the MetaQuest, all of Convai’s animations load properly in editor. Yesterday, I looked into the issue possibly being a result of an OVRPlugin being missing instead of Convai, but removing Convai did fix the issue and make my Metahuman spawn in front of me normally without flying off.

Could you please remove this node: ConvaiBaseCharacter BP -> Update

You’ll find ConvaiBaseCharacter inside the Core folder in the plugin content.

I’ve tried three new approaches: Removing the body and face animation classes from the Metahuman and leaving just reassigning his parent class to ConvaiBaseCharecter, doing the same with your suggestion implemented, and fully implementing the animation classes to the Metahuman with your suggestion implemented. In all three of these cases, the floating upwards issue still happened. In the logs for the first two cases with no animations, I could see that the LogSerialization issue I posted about is gone, but this didn’t fix the bigger issue of the Metahuman flying off.

Made a new attempt: All Convai aspects enabled normally, but with passthrough turned off. This time, it worked perfectly: The animations loaded in properly, the Metahuman spawned and stayed grounded, and conversation worked. So, it appears the issue is actually an interaction between ConvaiBaseCharecter and whatever governs passthrough.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.