# GASP Integration ## Character meshes {% hint style="info" %} **Note:** Compatible with GASP **5.4**, **5.5**, **5.6**. Add the latest Tactical Shooter Pack to your GASP project before starting. {% endhint %} First, we need to create a base for our integration. Duplicate the **BP\_TacticalShooterCharacter** (**KINEMATION/TacticalShooterPack/Blueprints**):

This will be our main player blueprint. Open it up, go to **Class Settings** and inherit it from the **CBP\_SandboxCharacter**:

Next, select the "Mesh" and set its animation blueprint to **ABP\_SandboxCharacter** and skeletal mesh to **SKM\_UEFN\_Mannequin**:

{% hint style="info" %} **Note**: The "Mesh" skeletal component will generate a motion-matching pose (full-body movement), which will be blended with our tactical animations. {% endhint %} Set **Visible** to **false** and **Visibility Based Anim Tick Option** to **Always Tick Pose and Refresh Bones**:

Always update animation, even if mesh is hidden.

Now we need to add a skeletal mesh for our character model. Let's call it "Player" and parent the **Camera** component to it:

Camera is a first-person camera component.

In the **Camera** settings, set its parent socket to `FPCamera` and reset its transform:

Find the `GetPlayerMesh` interface function and return the new "Player" skeletal mesh component:

Return the "Player", not the default "Mesh".

{% hint style="success" %} **Tip**: This interface function is used by weapons and animation blueprints to play animations, so make sure to provide the correct reference here. {% endhint %} ## Cameras The second step is to properly set up cameras in our player blueprint. If you use GASP 5.5 or 5.6, make sure to use this code snippet to disable other cameras:

The **Camera** attached to **Player** is the main first‑person camera. Deactivate all other cameras that may be active at game start. If you are on 5.4, then simply set all other cameras' `Auto Activate` property to **false**:

## Inputs The next step is to properly update GASP inputs at runtime. Open the `Update Player Movement` function (it's called on **Tick**):

Find some place at the end of the function, and set the value of the Gait property based on Movement State:

{% hint style="success" %} **Note**: `Gait` is from **GASP**, and `Movement State` is a **Tactical Shooter Pack** property. {% endhint %} Then, we need to update `bWantsToSprint`, `bWantsToWalk`, `bWantsToAim` and `bWantsToStrafe` properties. {% hint style="info" %} **Note:** The setup differs between **5.4** and **5.5/5.6**; refer to the images below. {% endhint %}

5.4 version also requires the Update Rotation function to be called.

## Animation blueprint Now we need to create an animation blueprint (ABP) that will combine motion-matching pose and animations from the **Tactical Shooter Pack**. Create a new Animation Blueprint using the **UE5 Manny** skeleton from the pack:

Go to the Event Graph and use this snippet for initialization:

{% hint style="success" %} **Tip***:* Obtain a reference to your player Blueprint here. {% endhint %} In the **Anim Graph**, add a **Retarget Pose From Mesh** node. Set the `Retarget From` to **Custom Skeletal Mesh Component**, and `IK Retargeter Asset` to **RTG\_UEFN\_to\_UE5\_Mannequin**:

After that, bind the `Source Mesh Component` using the "Mesh" property from the player blueprint.

Next, add the ABP\_TacticalShooter\_UE5 linked anim instance and blend it with the retargeted pose:

{% hint style="info" %} **Tip**: Feed the retargeted pose into **Base Pose**, and Tactical Shooter animations into **Blend Pose 0**. {% endhint %} ## Parkour adjustments To properly blend parkour animations, we need to adjust our layering. First, create 2 cached poses:

**UpperBody** carries Tactical Shooter animations; **MotionMatchingPose** carries full‑body motion. Next, add a new **Layered Blend Per Bone** node:

Add a **Blend by Bool** node and plug the layered result into **True:**

This will blend between parkour and normal poses using the `DoingTraversalAction` boolean from our character blueprint. Finally, blend the result with the "MotionMatchingPose":

--- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://kinemation.gitbook.io/tactical-shooter-pack-unreal/tutorial/gasp-integration.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.