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

UV scroll component should belong to the material not the node #121

Open
keianhzo opened this issue Sep 14, 2022 · 3 comments
Open

UV scroll component should belong to the material not the node #121

keianhzo opened this issue Sep 14, 2022 · 3 comments
Labels
Backlog P2 Address when able

Comments

@keianhzo
Copy link
Contributor

Is your feature request related to a problem? Please describe.
uv-scroll in hubs is applied to the material no per object but in the Blender Add-On it is related to the node.

Describe the solution you'd like
It would make more sense that the uv-scroll component belongs to the material category more than the node.

@keianhzo keianhzo added the P2 Address when able label Sep 14, 2022
@keianhzo keianhzo changed the title UV scroll component should beling to the mateiral not the node UV scroll component should belong to the material not the node Sep 20, 2022
@keianhzo
Copy link
Contributor Author

keianhzo commented Dec 8, 2022

Closing as this would require changes in both hubs and the add-on and it's not going to happen any time soon.

@keianhzo keianhzo closed this as completed Dec 8, 2022
@j-conrad
Copy link

j-conrad commented Dec 8, 2022

I understand this isn't happening soon, but it's worth pointing out the following:
If I have 2 objects, each with the same material, it's currently possible to put a UV-Scroll component on both of them, each with different settings.
In this case, it would be very difficult for a user to understand which object takes precedence since BOTH objects will take on the properties (speed, etc.) of ONE of them.

@j-conrad j-conrad reopened this Dec 8, 2022
@j-conrad j-conrad closed this as completed Dec 8, 2022
@keianhzo
Copy link
Contributor Author

keianhzo commented Dec 9, 2022

That's a fair point. I'm going to reopen it, I think it's worth fixing the multiple materials affected issue and moving it to the material.

@keianhzo keianhzo reopened this Dec 9, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Backlog P2 Address when able
Projects
None yet
Development

No branches or pull requests

2 participants