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

Fix #1725 Texture can now be plugged directly on socket #1726

Merged
merged 28 commits into from
Oct 11, 2023

Conversation

julienduroure
Copy link
Collaborator

Fix #1725 Texture can now be plugged directly on socket

@julienduroure
Copy link
Collaborator Author

If No SeparateColor node found, so take the specification channel that is needed
So export is correct if user plug the texture directly to the socket
Currently on master, the R channel is taken by default.

This still need to be fully tested to be sure there is no regression

@julienduroure
Copy link
Collaborator Author

julienduroure commented Sep 27, 2023

TODO :

  • Crash when texture is plugged on Color, but socket is int (and should be linked to Alpha)

@julienduroure julienduroure added this to the Blender 4.1 milestone Sep 30, 2023
@julienduroure julienduroure merged commit dc4d72f into main Oct 11, 2023
2 checks passed
@julienduroure julienduroure deleted the fix_1725_texture_plugged_directly branch October 11, 2023 09:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Manage texture plugged directly on socket without separate node
1 participant