Okay, I now have access to the Blueprint and can take screenshots. Let's make a tour.
First things first, last time we checked on the discomfort level updating we noticed a small issue, since we only have 3 different levels of scaling for the sensors (how much does each sensor affect the overall stress index value) it meant that every time a new sensor on the same scaling level was trying to play a note the other sensors on the same level were turning it off at the same time, we needed to find a way so that the note signals would only be turn off when all sensors of the same level were off.
for this purpose we modified the Macro a tiny bit. The signal is not being turn off as part of the sensor's macro anymore. Instead, we created a new macro.
This Macro utilizes the "Pressed" boolean array we had made before, and through a "For Loop With Break" node, checks every array variable that represents a sensor within the range of each level scale. By the macro then breaks and doesn't allow the for loop to complete unless all booleans in the range are false, in which case it turns off the note. Since MIDI signals do not overlap with each other, I also decided to send the signal every time one of the values in the range are true, allowing us as well to remove the "Channel" slot from the previous macro.
Talking about macro development, I also simplified the way the events are called to make better use of the "Max Value" int variable we had generated before (also to have more flexibility about when certain effects are triggered) another macro was developed that just multiplies the maximum value for the progress percentage we've decided to use as trigger points and then checks if the current Stress Levels are higher than that trigger point.
Okay, in the last post I also mentioned that I had been charged with adding some of the effects and besides being the ring master (of which I will also make a post later gosh I'm tired) my job for the final week will basically just be helping people put their effects and ideas into the blueprint.
As an example here is the configuration for the lights: As part of its process (and incidentally for what hell it was to try to understand how things worked) we realized that we could make object changes in scene elements by creating a variable that hosts them. For the lights I created an array of Actors (Lights) that in the scene was filled with all light components that we wanted to be dimmed following Vivian's event chart.
Then, and once again, following Vivian's chart, we made 2 distinct paths for the lights to dim since they darken progressively until the very end when the change is much more aggressive. We can call each light as part of the array using a "For Each Loop" and changing the intensity of each light component.
in reference to the current Stress Level.
Other objects like the NDisplay camera that we use to display things in the projector can be triggered utilizing the same system of importing a new variable that contains the object. Here is an example of a process that changes the post processing saturation.
Comments
Post a Comment