Currently the AssetGenerator node assumes that only a single asset will be used to generate another, for example, materials assume only a single texture input, but that's not usually the case, I did implement my own node to do this but it would be better to just assume a more scalable solution.
Currently the AssetGenerator node assumes that only a single asset will be used to generate another, for example, materials assume only a single texture input, but that's not usually the case, I did implement my own node to do this but it would be better to just assume a more scalable solution.
Thank you.