AcademySoftwareFoundation / AcademySoftwareFoundation/OpenShadingLanguage
vector2 values are not passing through shader connections
- Dominant language
- C++
- Stars
- 2.3k
- Forks
- 414
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 10
Description
Hi,
I tried several things and I failed to make vector2 values to pass from a shader to another one when connecting them.
I tried with builtin types like vector and color and it works perfectly. I suppose it is because a vector2 is a structure but I didn't try with similar types like vector4 or color4.
What I'm trying to do actually is to extract UV coordinates via a MaterialX texture node like mx_geompropvalue_vector2 and plug it into an mx_image_color. Am I doing something wrong or is it a bug?
I'm using OSL 1.11.8.0 compiled with LLVM 9.
EDIT: actually, the mx_geompropvalue_vector2 code is not even called. So it's like the connection is ignored whereas we don't get any error while setting it.
Thanks in advance!
Nicolas
Contributor guide
Research direction
Reproduce the vector2 connection from mx_geompropvalue_vector2 to mx_image_color using OSL 1.11.8.0 compiled with LLVM 9, then compare it with the working builtin vector and color connections. Done means the vector2 value passes through the shader connection and the mx_geompropvalue_vector2 code is called.
Written by the indexing model from the issue text.
Assessment
- Domain
- compilers, computer-graphics
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100