# Request for pointVectorField pointDisplacement from objectRegistry region0 failed | available objects of type pointVectorField are 0()

**URL:** <https://precice.discourse.group/t/request-for-pointvectorfield-pointdisplacement-from-objectregistry-region0-failed-available-objects-of-type-pointvectorfield-are-0/658>\
**Category:** Using preCICE\
**Tags:** openfoam\
**Created:** [July 15, 2021, 12:44pm UTC](https://precice.discourse.group/t/request-for-pointvectorfield-pointdisplacement-from-objectregistry-region0-failed-available-objects-of-type-pointvectorfield-are-0/658 "2021-07-15T12:44:14Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![Makis](https://yyz2.discourse-cdn.com/free1/user_avatar/precice.discourse.group/makis/32/25_2.png) [@Makis](https://precice.discourse.group/u/Makis)\
**Post date:** [July 19, 2021, 1:56pm UTC](https://precice.discourse.group/t/request-for-pointvectorfield-pointdisplacement-from-objectregistry-region0-failed-available-objects-of-type-pointvectorfield-are-0/658/8 "2021-07-19T13:56:06Z")

</div>

I understand now that the problem is really that the mesh motion solver (you are using [multiSolidBodyMotionSolver](https://www.openfoam.com/documentation/guides/latest/api/classFoam_1_1multiSolidBodyMotionSolver.html) does not define `pointDisplacement` in the same way as e.g. `displacementLaplacian`. Therefore, the adapter does not know how to read displacements in this class context.

Since you are trying to use overset, do you also need to use multiSolidBodyMotionSolver? If yes, then you would also need to modify our `Displacement.C` accordingly.

As far as I know, overset should work with `displacementLaplacian` (check again Derek Risseeuw’s master’s thesis for details, he had a moving flap there).

---

_[View the full topic](https://precice.discourse.group/t/request-for-pointvectorfield-pointdisplacement-from-objectregistry-region0-failed-available-objects-of-type-pointvectorfield-are-0/658)._