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

Filter Node Doesn't support output generated assets #147

Open
RaadDalaq opened this issue Apr 6, 2020 · 0 comments
Open

Filter Node Doesn't support output generated assets #147

RaadDalaq opened this issue Apr 6, 2020 · 0 comments
Assignees

Comments

@RaadDalaq
Copy link

Currently the filter node, will only filter if the asset is actually registered in the data base, for example, if I wanted to generate a couple of procedural materials from incoming textures and then use keyword/regex to split those materials into multiple pipelines (outputs) the node won't register these materials, it seems to have to do with limitations in checking the extension of the incoming asset (it's only relying on it being in the asset database).

thank you.

@hiroki-o hiroki-o self-assigned this Apr 6, 2020
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

No branches or pull requests

2 participants