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

Proposal: Autolinkage between "float list output" and "vector/euler input" #1382

Open
Gerstmann-Bradley opened this issue Mar 27, 2020 · 3 comments
Labels

Comments

@Gerstmann-Bradley
Copy link

Currently AN offers autolinkage between "float" and "vector/euler" with combine node. (or "Vector from value" node particularly for "scale")
But this function doesn't seem working for "float list", even if many nodes are vectorized and working through mannual linking.
I mainly tested with "float range"/"create a float list" and "object transform output", "offset matrices" node.

Sometimes I only need to effect certain axis only, using a float to control will improve UI of loop/group/viewport input node, etc.

@OmarEmaraDev
Copy link
Collaborator

But in this case, should we add a Combine Vector node or a Vector From Value node?

@Gerstmann-Bradley
Copy link
Author

But in this case, should we add a Combine Vector node or a Vector From Value node?

Sorry, I don't understand the question.
The current setup in AN is that for "location/translation", a float will generate a "combine vector" node.
but for "scale", it will generate a "vector from value" node.
I don't exactly know whether such an autolinkage is specific to type of input or each node itself, but my expectation is just to allow "float list" do the same behavior as what "float" is doing right now in AN.

@OmarEmaraDev
Copy link
Collaborator

Ah ok, I didn't realize we did socket-based conversion.

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