Attachment Not Found
bind export affects principle shader
3017 4 2
-
- Nicolas Heluani
- Member
- 280 posts
- Joined: Dec. 2015
- Offline
-
- Nicolas Heluani
- Member
- 280 posts
- Joined: Dec. 2015
- Offline
Ok, I solve part of the issue….
Apparently the issue happens when bind exporting the data outside of the material.
if I bind export it inside the principle shader everything is peachy…
I already reported it as a bug, as we should be able to bind export data outside as to properly use the power of the new material context….
Apparently the issue happens when bind exporting the data outside of the material.
if I bind export it inside the principle shader everything is peachy…
I already reported it as a bug, as we should be able to bind export data outside as to properly use the power of the new material context….
-
- JasonSlab
- Member
- 1533 posts
- Joined: March 2020
- Offline
-
- Richard Costin
- Member
- 101 posts
- Joined: May 2006
- Offline
-
- Nicolas Heluani
- Member
- 280 posts
- Joined: Dec. 2015
- Offline
JasonSlab
Yes this is a bit of a issue with the new MAT context, connecting binds to the shader as a property of sorts is a good idea.
Yep… The new MAT context is an awesome system.
So requiring to incorporate AOVs into each shader will kind of defeat that purpose.
I think this problem happens only when dealing with packed primitives and point color so I already report it as a bug:
bug #86507
-
- Quick Links