06-27-2019, 03:59 PM
Unfortunately there's no way to do that at the moment. It's something the Phoenix devs would have to implement on their end (reading tyFlow groups directly and allowing users to choose which ones they want as input in the Phoenix UI).
One minor workaround is setting up multiple tyFlows, but making successive flows simply import the particles of the first flow using Birth Flow / Update Flow operators (and then setting your different group assignments in those dependent flows). That way all other flows would be dependent on the first one so you only have to modify one flow for all the others to update. That would be a cleaner solution than having multiple identical flows that would all need to be updated individually.
One minor workaround is setting up multiple tyFlows, but making successive flows simply import the particles of the first flow using Birth Flow / Update Flow operators (and then setting your different group assignments in those dependent flows). That way all other flows would be dependent on the first one so you only have to modify one flow for all the others to update. That would be a cleaner solution than having multiple identical flows that would all need to be updated individually.