PART 1:

Preparation for the presentation and familiarization with the capabilities of Lens Studio, including its strengths and weaknesses.

PART 2:

Raw code build

1. System for full body tracking. Constants and Variables:

• onFoundTrigger, onLostTrigger: Events triggered when full body tracking starts or stops.

• MAX_BODY_SIZE, CENTER, MIN_LOST_FRAMES: Constants for defining maximum body size, the centre point, and minimum lost frames.

• FULL_BODY_IDs, MAIN_POINTS_IDs: Arrays holding IDs of different body points used for tracking.

• FullBodyTracking Function:

  • Initializes tracking for each body point defined in FULL_BODY_IDs.

  • Creates a special 'Hip' point as the median of the left and right hips.

  • Includes methods for checking if the main body points are being tracked and for calculating the body size.

• Tracking State Machine:

  • Defines different states (NONE, TOO_CLOSE, TRACKING) for the tracking system.

  • Implements a state machine pattern to handle transitions between these states based on tracking data.

• Event Bindings:

  • Binds functions to different events (TurnOnEvent, UpdateEvent, FaceFoundEvent, FaceLostEvent) to handle changes in tracking state.

• State Change Callbacks:

  • Functions like onTrackingEnter, onTrackingExit, and onTooCloseEnter are called when the state machine transitions to a new state. These functions handle events like triggering custom actions or showing/hiding hints.

• BodyPoint and MedianBodyPoint Functions:

  • Define classes for individual body points and a median body point (like the 'Hip' point) to facilitate tracking and position calculations.

• StateMachine Class:

  • Implements a state machine with functions to add states, set the current state, and get the current state.

• Helper Functions (debugPrint, checkInputs):

  • Provide utility for debugging and checking if necessary inputs and scripts are set up correctly.

2. Defining and detecting custom body gestures based on the positions and rotations of various body parts.

Constants and Bone IDs:

• FULL_BODY_BONE_IDs: Lists the IDs of bones (body parts) used for gesture recognition (like arms, legs, spine).

• VEC2_UP, PI: Defines a vector pointing upwards and the mathematical constant π (Pi).

• Pose Library:

  • A collection (PoseLibrary) of predefined poses with specific angles for different bones. Users can add custom poses by recording and copying angles from the logger.

• Bone Function:

  • Defines a Bone class to represent each bone with start and end points, and a parent (for hierarchical bone structures).

  • Includes methods for tracking and calculating the rotation of each bone.

• Bone Initialization:

  • Creates instances of the Bone class for different body parts like upper arms, forearms, upper legs, lower legs, and spine, using points from the FullBodyTracking object.

• Pose Detection Functions:

  • getCurrentPose: Calculates the current pose by getting the rotation of each bone.

  • printPose: Prints the current pose to the console if the body is being tracked.

  • poseFromJson: Creates a pose object from a JSON string.

• Pose Matching:

  • isMatchingPose: Checks if the current body pose matches a given pose within a specified threshold.

  • getDifference: Helper function to calculate the angular difference between two angles.

• Gesture Recognition:

  • getGestureFrames: Retrieves a sequence of poses (a gesture) from the pose library.

  • Utilizes the predefined poses to recognize specific gestures based on the current body posture.

• Helper Functions and Initialization:

  • debugPrint: Utility function for logging messages.

  • Initialization for the tap event to trigger printPose and setting up API methods for external access.

3. Movement or gesture recognition:
Initial Setup:

• CENTER: A constant representing a zero vector, likely used as a reference point.

• Variables for tracking movement start, delays, and keeping pose times.

• Check if the necessary components (FullBodyTracking, behaviorSystem) are available.

• Movement Type and Gesture Handling:

  • Determines if the movement is a multi-frame gesture (more than one gesture in sequence).

  • Selects the appropriate matching function based on script.moveType (e.g., gesture, touch screen trigger, distance check).

• Gesture Matching:

  • The getMatchingFunction function returns a closure that encapsulates the logic for checking if a current movement matches a predefined gesture or other criteria (like touching the screen or distance between points).

• Update Event Binding:

  • Binds the OnUpdate function to the UpdateEvent, which is likely called every frame or at regular intervals.

• Update Logic:

  • Check whether the current movement or pose matches the predefined criteria.

  • Handles the logic for starting and ending movements, including delays and gesture sequence handling.

  • Updates curFrameIndex to track progress through multi-frame gestures.

• Start and End Functions:

  • start: Triggered when a movement starts, sending custom triggers and initializing variables.

  • end: Triggered when a movement ends, sending completion triggers and resetting variables.

• Gesture Matching Logic:

  • isMatchingGesture: Checks if the current pose matches the current frame of a gesture sequence.

• Debug Printing:

  • debugPrint: Utility function for logging messages, controlled by a debug flag.

4. Actions trigger various visual and animation effects:

Initial Disabling of Trigger Objects:

• Iterates over script.triggerObjects and disables each of them. This is likely a setup step to ensure that the trigger objects are inactive until a specific event occurs.

• OnTrigger Function:

  • Activated when a certain trigger is detected.

  • Enables all script.triggerObjects.

  • Starts animations for each object in script.triggerTweens using global.tweenManager.

  • Plays animated textures in script.triggerAnimatedTextures.

  • Initiates particle effects in script.particleBursts.

• OnTriggerEnd Function:

  • Handles the logic for what happens when the trigger ends.

  • If there are any tweens (animations), it starts the fade-out animation and calls OnTriggerEndTweenEnd upon completion.

  • If there are no tweens, it directly calls OnTriggerEndTweenEnd.

• OnTriggerEndTweenEnd Function:

  • Disables all script.triggerObjects.

  • Stops any animated textures in script.triggerAnimatedTextures.

  • Stops particle effects in script.particleBursts.

• Behaviour System Integration:

  • Checks if global.behaviorSystem is available.

  • Adds custom responses to script.startTrigger and script.endTrigger, linking them to OnTrigger and OnTriggerEnd functions, respectively.

• Debug Print Function:

  • A utility function, debugPrint, for logging messages to the console, likely for debugging purposes.

PART 3:

Adjusting and refining the 3D Try-On Pack available from the Lens Studio Asset Store and investigating the potential for incorporating external 3D models.

PART 4:

Incorporating the 3D models supplied by the artists and meticulously adjusting the trigger points.

PART 5:

Preparation of the Portfolio.