# CustomUV-Values broken when used for World Position Offset

**URL:** <https://forums.unrealengine.com/t/customuv-values-broken-when-used-for-world-position-offset/383667>\
**Category:** Rendering\
**Tags:** fyi, unreal-engine, Rendering, question\
**Created:** [February 1, 2017, 9:25pm UTC](https://forums.unrealengine.com/t/customuv-values-broken-when-used-for-world-position-offset/383667 "2017-02-01T21:25:02Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Answers.Archive](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Answers.Archive](https://forums.unrealengine.com/u/Answers.Archive)\
**Post date:** [February 1, 2017, 9:25pm UTC](https://forums.unrealengine.com/t/customuv-values-broken-when-used-for-world-position-offset/383667/1 "2017-02-01T21:25:02Z")

</div>

Hi,

I’m getting same issue as this post:

> **[CustomUV-Values broken when used for World Position Offset](https://forums.unrealengine.com/questions/556072/customuv-values-broken-when-used-for-world-positio.html)**
>
> I´m trying to pass world position based UVs through the custom UVs inputs in a material. The passed data works well for color information but is broken when used as World PositionOffset. See the GIF as example: http://i.imgur.com/8Q96BSx.gif As you...

Are there any solution or recommendation?

---

<div class="post-metadata">

**Author:** ![Answers.Archive](https://d3kjluh73b9h9o.cloudfront.net/original/4X/2/8/5/28502927f1d97ba1051b3b47ccfe17233bf41ef0.png) [@Answers.Archive](https://forums.unrealengine.com/u/Answers.Archive)\
**Post date:** [February 1, 2017, 9:25pm UTC](https://forums.unrealengine.com/t/customuv-values-broken-when-used-for-world-position-offset/383667/2 "2017-02-01T21:25:16Z")

</div>

Hi Alfredo,

When working with WPO you don’t need to use the custom UV coordinates for Pre-Skinned Local Position (or world position) to work and in fact this may cause errors when running those values through a UV coordinate node based off the custom UVs.

Here is an example of how you would setup the graph.

 ![124540-temp1.jpg](https://d3kjluh73b9h9o.cloudfront.net/original/4X/9/e/8/9e85ddcdaa0edf1ed13ffa231ffabedf33de67a0.jpeg)

This is the result of the material applied to a sphere located at (0,0,0)

![124551-gif1.gif](https://d3kjluh73b9h9o.cloudfront.net/original/4X/b/8/2/b82da31c7fab276d4165f16eb2f88172d1b75810.gif)

I swapped the WorldPosition Node with Pre-Skinned Local Position and got a nearly identical result. It would be more accurate to compare to the local position node. Not to be confused though, Pre-Skinned Local position will behave very similarly to local position when used with WPO, but there is a distinct difference. The positions are all relative to the base pose.

To illustrate this point I assigned an animation to the character(so it isn’t in its base post) and then plugged pre-skinned position directly into WPO and multiplied by a scalar. I then switched to local position and did the same thing and recorded a short [video][3].

I’m not sure if this is going to be particularly useful for you depending on the effect you are going for.

We have a Pre-Skinned Local Normal node coming to 4.15 This works in a similar way to the Pre-Skinned Local Position node added in the 4.14 release but returns the local surface normal for skeletal and static meshes. This opens the door to more local-space, mesh aligned effects or advanced use-cases such as writing dynamic surface data to a mask read-back in another material.

Depending on the effect this may be what you are looking for. In short the bugs reported in that AnswerHub post aren’t a real issue and the nodes are working as expected.

Let me know if you have any questions or need anything else!

Ed
