# UE5 Niagara: Can't access SolveForcesAndVelocity Output Position

**URL:** <https://forums.unrealengine.com/t/ue5-niagara-cant-access-solveforcesandvelocity-output-position/552915>\
**Category:** FX\
**Tags:** unreal-engine, UE5-0\
**Created:** [May 9, 2022, 4:28pm UTC](https://forums.unrealengine.com/t/ue5-niagara-cant-access-solveforcesandvelocity-output-position/552915 "2022-05-09T16:28:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![AndyK](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/andyk/32/753284_2.png) [@AndyK](https://forums.unrealengine.com/u/AndyK)\
**Post date:** [May 9, 2022, 4:28pm UTC](https://forums.unrealengine.com/t/ue5-niagara-cant-access-solveforcesandvelocity-output-position/552915/1 "2022-05-09T16:28:28Z")

</div>

I’ve just been following the “Building advanced effects in Niagara” video posted on the UnrealEngine channel and am stuck at the point where a Lerp is used to blend between particle positions.

Here are some basic steps of the setup:

- Particles are initialized via “InitializeMeshReproductionSprite”
- Particles are affected by forces such as “VortexVelocity”
- The force(s) are followed by a “SolveForcesAndVelocity”
- “UpdateMeshReproductionSprite” binds the particles to the mesh’s surface
- A “LerpParticleAttributes” is used to blend between the position affected by the forces and the position on the mesh surface

In the video the SolveForcesAndVelocity has a position output, which seems to be missing here. I’ve only got access to “IncomingPhysicsForce” and “Velocity”. Has something changed in UE5?

I’ve followed the steps a couple of times now but seem to encounter the same problem each time. Just thought I’d ask here while I try digging deeper. Thanks in advance! 🙂

Link to video:

[![](https://d3kjluh73b9h9o.cloudfront.net/original/4X/a/8/c/a8ce825a4388010b08e948ee4d105e65cff83346.jpeg "Building advanced effects in Niagara | Unreal Engine") ](https://www.youtube.com/watch?v=syVSRDQxrZU)

---

<div class="post-metadata">

**Author:** ![Michael.Galetzka](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/michael.galetzka/32/924122_2.png) [@Michael.Galetzka](https://forums.unrealengine.com/u/Michael.Galetzka)\
**Post date:** [May 9, 2022, 5:33pm UTC](https://forums.unrealengine.com/t/ue5-niagara-cant-access-solveforcesandvelocity-output-position/552915/2 "2022-05-09T17:33:29Z")

</div>

Unless the output was removed completely from the module, it was probably changed from a vector type to a position type (see [the docs](https://docs.unrealengine.com/5.0/en-US/large-world-coordinates-in-niagara-for-unreal-engine/) for more info).

You can convert a position to a vector in the stack, but be aware that doing so probably breaks the effect when using it with large world coordinates.

---

<div class="post-metadata">

**Author:** ![AndyK](https://d1ap1mz92jnks1.cloudfront.net/user_avatar/forums.unrealengine.com/andyk/32/753284_2.png) [@AndyK](https://forums.unrealengine.com/u/AndyK)\
**Post date:** [May 18, 2022, 6:27am UTC](https://forums.unrealengine.com/t/ue5-niagara-cant-access-solveforcesandvelocity-output-position/552915/3 "2022-05-18T06:27:59Z")

</div>

Converting the position output from a position type to vector type solved it, thanks! I’m not working with large world coordinates, but will keep that in mind.
