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

Arbitrary uv texture lookup on V-Ray Standalone/V-Ray for Maya is not implemented. #3

Closed
petermcevoy opened this issue Aug 21, 2017 · 3 comments
Labels
Milestone

Comments

@petermcevoy
Copy link
Collaborator

The function tl_eval_texmap_mono_lookup in vray_thunderloom.cpp is not implemeted.
This means that there will be problems when varying yarnsizes non-uniformly, such as with a changing texture. I can't find a way to achieve this sort of lookup using the V-Ray APIs.

See my question on the ChaosGroup forums for more info: https://forums.chaosgroup.com/forum/v-ray-for-maya-forums/v-ray-for-maya-sdk/76255-texture-lookup-with-uv-on-non-bitmap-textures

See the implementation of tl_eval_texmap_mono_lookup in vray3dsMax/3dsMax/Eval.cpp for how it works in V-Ray for 3dsMax.

@sharktacos
Copy link

May I ask what the purpose of the arbitrary uv texture lookup is? What functionality does this provide?

@petermcevoy
Copy link
Collaborator Author

@sharktacos This is needed to correctly handle yarnsizes which are controlled with a texturemap.

The shader needs to be able to look up the yarnsize of the neighbouring yarns in order to handle the varying yarnsizes correctly, that is, read the texture at uv coordinates that are not the current sampling point.

@sharktacos
Copy link

Understood, thank you.

@petermcevoy petermcevoy added this to the v1.0.0 milestone Sep 28, 2017
petermcevoy added a commit that referenced this issue Sep 30, 2017
petermcevoy added a commit that referenced this issue Feb 27, 2018
github issue #3


Former-commit-id: 69e4736
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants