# creative\_prop MoveTo disposed error when called from other Verse

**URL:** <https://forums.unrealengine.com/t/creative-prop-moveto-disposed-error-when-called-from-other-verse/837372>\
**Category:** Programming & Scripting\
**Tags:** unreal-editor-for-fortnite, fortnite\
**Created:** [April 1, 2023, 2:35pm UTC](https://forums.unrealengine.com/t/creative-prop-moveto-disposed-error-when-called-from-other-verse/837372 "2023-04-01T14:35:28Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![Conan\_Reis](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/conan_reis/32/1016955_2.png) [@Conan\_Reis](https://forums.unrealengine.com/u/Conan_Reis)\
**Post date:** [May 5, 2023, 12:04am UTC](https://forums.unrealengine.com/t/creative-prop-moveto-disposed-error-when-called-from-other-verse/837372/7 "2023-05-05T00:04:40Z")

</div>

Since you are using `MoveTo()` you also might want to check this post out:

> [@MoveTo is severely Buggy \[Fixed Fortnite v25.0\]](https://forums.unrealengine.com/t/moveto-is-severely-buggy/879773/10):
>
> UPDATE: Fixed June 6, 2023 in UEFN as of Fortnite v25.0 MoveTo() now works as expected and a hack to prevent snapping is no longer necessary. You can switch the call to MoveToPositionalExpected() from MoveToPositional() in FollowPositional() to see nice smooth movement without visual hitches. If MoveTo() is canceled it seems to have a glitch where it may reset a prop to its starting position. We’ve identified the likely cause of the MoveTo() glitch and are working on a fix for a future upda…

---

_[View the full topic](https://forums.unrealengine.com/t/creative-prop-moveto-disposed-error-when-called-from-other-verse/837372)._
