Simplifying Level Flow

Simplifying Level Flow

baileysan
Enthusiast Enthusiast
588 Views
3 Replies
Message 1 of 4

Simplifying Level Flow

baileysan
Enthusiast
Enthusiast

I have a model with four triggers, each of which I want to do the same thing, basically turning on six lights.

 

Before i start connecting the remaining three triggers, is there a better way to lay this out? How can I group the triggers to say if either one is triggered, do this action? How can I group the lights to say when triggered, all turn on?

 

Ultimately I'd like to add more lights, and sequence them differently, but just these six are getting too messy for me.

 

Capture.PNG

 

 

 

Reply
Reply
0 Likes
589 Views
3 Replies
Replies (3)
Message 2 of 4

Shanii2
Collaborator
Collaborator

You can do this in a couple of ways..  

1) create an encapsulated flow subroutine note and save it in your scripts then You can simply plug in the inputs to carry out task there are tutorials of Using flow subroutine in Stingray learning series of 'SERVO' and in help docs to..  You simply copy all nodes and paste them in external flow editor and plant the input and output switches to make it self-sustainable flow node..

2)  The second option you can do is utilizing the Entity systems. If what you are trying to do is part of a system your designing and want it to work efficiently regardless of what it is.  You can create and entity for this you can create a special unit or object for it mesh, lights etc in dcc tool and bring in to create an entity . you can control entity by assigning it several tags and property inputs, data, unit, flow, script , transforms, shading environment and other stuff. you can create a data type variables for entity to receive inputs and consolidate the entire within the entity's flow script, so no matter where you might need to reproduce the system, it only requires one time effort and you can effectively and independently use it to create several subsystems for driving your App or Game functionality.  

 

For Example. 'You create a system where a person opens a door and when he enters. The lights near door turn on, and a ceiling fan in that room turns on. Now to instead of replicating and re-implementing flow nodes for all the rooms and Doors. you can just create an entity system in which's flow script you take the input of door unit, its animation and sound events, some inputs of triggers of room, and lights and 2-3 data holding entity properties and named respectively for the desired task, and so you can create entire logic within the entity's flow and only receiving the required inputs for the level or locality.  And then you can simply replicate it where you want once it starts working as expected regardless of what u have in the surrounding. You just create an independent subsystem, which you duplicate over,

Reply
Reply
0 Likes
Message 3 of 4

baileysan
Enthusiast
Enthusiast

@Shanii2 wrote:

there are tutorials of Using flow subroutine in Stingray learning series of 'SERVO' and in help docs to..  You simply copy all nodes and paste them in external flow editor and plant the input and output switches to make it self-sustainable flow node..

 


Can you provide a link to the series, google isn't able to help me for that. Also, is there an example of the input and output switches you could share? Thanks!!

 

Reply
Reply
0 Likes
Message 4 of 4

Shanii2
Collaborator
Collaborator

You need to see the said Youtube tutorials And dive in help docs on how to use. Flow subroutine node, and how to compile a complex logic into One Node. 

Stingray learning series 

You need to see all of tuts in these series and also the begining tutorial.

You need to grasp basic knowledge before you start complex

Reply
Reply
0 Likes