Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

[Closed] CustomUV-Values broken when used for World Position Offset


I'm getting same issue as this post:


Are there any solution or recommendation?

Product Version: Not Selected
more ▼

asked Feb 01 '17 at 09:25 PM in Rendering

avatar image

Answers.Archive STAFF
2k 212 318 698

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

The question has been closed Feb 01 '17 at 09:27 PM by AndrewHurley for the following reason:

The question is answered, right answer was accepted

1 answer: sort voted first

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.

alt text

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

alt text

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.

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!


temp1.jpg (106.6 kB)
gif1.gif (79.7 kB)
vid3.zip (1.2 MB)
more ▼

answered Feb 01 '17 at 09:25 PM

avatar image

Answers.Archive STAFF
2k 212 318 698

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question