Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changes in UV data #78

Open
qlee01 opened this issue Dec 12, 2023 · 2 comments
Open

Changes in UV data #78

qlee01 opened this issue Dec 12, 2023 · 2 comments
Labels
enhancement New feature or request

Comments

@qlee01
Copy link

qlee01 commented Dec 12, 2023

Hi, one of the updates after 0.9 there seems to have been a change how UV data is utilized; the former version of Enemies Demo used a vertex ID stored in UV0 and some custom HLSL to determine the position on individual hair strands (0-1 from root to tip). With the latest changes, which are also replicated to Enemies demo, the strand UV from the HairVertex are used directly for this. However, this UV does not reliably have same data on all kind of strands, some strands don't seem to go until 1.
Is there any way to replicate the old behavior now, having full range of 0-1 on all strands?
This is critical for good looking simulation.

@qlee01
Copy link
Author

qlee01 commented Dec 12, 2023

I was able to "repair" the function "CalculateHairStrandUV" by unpacking IDs the same way it is done in HairVertex.hlsl. This is suboptimal, as now we are doing some things twice, and I don't want to change anything in Hair package. it would be much better if the StrandUV provided by HairVertex node would deliver correct UV across the full length of strands.

@fuglsang fuglsang added the enhancement New feature or request label Apr 16, 2024
@fuglsang
Copy link
Collaborator

Hi. This will be added soon, pending some additional refactoring work on inputs/outputs of the HairVertex node.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants