Home Creators Posts Import Register Favorites Logout

Videos

  • AGLS_PoseSearch_RootMotion.mp4
  • AGLS_AsynLoadDatabases.mp4
  • AGLS_NewCrawlingLoco.mp4
  • AGLS_HumanAI_NewWalking.mp4
  • AGLS_19_MeleeCombatExample_01.mp4
  • AGLS_19_MeleeCombatExample_02.mp4

Downloads

Some files exceed the archive size limit and weren't saved: 2 files. Please note these limits are in place to keep this site running long term, without costing a fortune. You can favorite the creator though, certain milestones increase the limit.

Content

A large-scale project designed for Unreal Engine 5.7+ that includes mechanics commonly used in adventure games.

⚙️The project is based on C++ (6 C++ plugins), but modifying the source code is not required — changes can be made entirely through Blueprints.

Not all animations are included in the project (list), but they are not required for the project to function.

The project is compatible only with Windows systems. Packaged only on Win 11.

The entire system is NOT replicated.

🏃‍♂️All animations (~ 2.5k files) rigged to UE4 Mannequin, but project include real-time retargeting to UE5 Manny (compatible with Metahuman skeleton structure)

Size to download ~2.5GB zipped

⚠️ NOTE: AGLS is a highly complex and extensive framework. It includes many features that extend the default systems available in the engine. Working with it efficiently and making modifications requires substantial experience with Unreal Engine.

Full Project Demonstration Wideo (AGLS v1.4 version)

Packaged Project DEMO for Windows

Patch Notes from 1.2 to 1.7 (Patreon Posts)

The link to download the project files is at the end of the post content

Informations about animations:

Not all animations are included in the project. 

Animations such as Stealth Finishers or some other finishers come from the UE Marketplace. You don't need to own these animation packs to open the project in the editor. The main consequence of missing animations will simply be poorly looking sequences like attack or some interactions.

⚠️ Note: There have been significant changes regarding animations not included in the project. As of version v1.8, animations from the "Brutal Finishers - Hand and Knife" pack are no longer as essential, and MeleeCombat now uses only 6 animation assets during game from this pack. Despite this, the project still contains additional assets for these animation sequences, as they are planned to be used in future versions. For "Stealth Finishers - Knife and Hand" and "Ultimate Traversal Anims", the situation remains largely the same as in previous versions of the project.

Here’s a list of animation packs not included in the project (not all sequences from the packs are used in the project):

"Stealth Finishers - knife and hand" by RamsterZ

"Brutal Finishers - Hand and Knife" by RamsterZ

"Ultimate Traversal Anims" by RamsterZ

A full list of not included animations sequences used in the project

If you have the necessary additional components, the implementation into AGLS is very simple. You just need to export the required animation sequences to .FBX files. Then, assign the appropriate file names and reimport them into AGLS.

✅ Without these animations, the project will run normally.

🔷Main changes and information regarding version 1.9:

AGLS 1.9, compared to previous versions of the project, may not appear to introduce many new features or significantly expanded systems at first glance. From a gameplay perspective, the main addition is the Melee Combat system, which can now be used by both Enemy HumanAI and CompanionAI. However, I will describe that functionality a bit later, because I would first like to focus on what consumed an enormous amount of my time and turned out to be the most difficult challenge I have ever undertaken while working with Unreal Engine. I am referring primarily to designing a better Motion Matching solution for both the player character and HumansAI. As most of you probably know, Epic Games provides a sample project called the Game Animation Sample Project (GASP), which demonstrates how powerful animation systems based on the Pose Search plugin can be. In GASP, the entire locomotion system is implemented exceptionally well, and it is clear that a tremendous amount of time was invested in its development. Of course, AGLS is heavily inspired by the solutions used in GASP. However, despite multiple attempts to transfer the entire locomotion setup to the UE4 Mannequin skeleton, I was never able to achieve animation selection that was as precise, nor movement that felt as clean and polished.

For that reason, after implementing Melee Combat for HumanAI, I decided to take a much closer look at how Pose Search actually works. I spent roughly two weeks trying to improve the default locomotion system in my project. While I achieved some improvements, the results were never quite as good as I wanted.

It is important to note that the requirements of AGLS differ somewhat from those of GASP, even though the overall integration approach should remain similar.

It is also worth mentioning that the final movement system is intended to be driven entirely by the Motion Matching node, rather than by a combination of Blend Stack + State Machine + Chooser. The latter approach (which is also used extensively in GASP) can produce extremely high-quality locomotion and, in some situations, even smoother results than pure Motion Matching. However, it is also much more difficult to maintain and significantly more time-consuming to develop than a system based primarily on Pose Search Databases.

In the end, I decided to rebuild the entire movement system almost from scratch. To achieve this, I created two major C++ classes:

MovementParamsControlComponent ᶜ⁺⁺

AGLS_Player_AnimInstanceCore ᶜ⁺⁺

The first system/component was designed to provide better control over parameters related to the CharacterMovementComponent. Previously, AGLS handled this functionality in the same way as ALSv4, using a DataTable-based approach. Now, however, each movement preset is stored as a DataAsset, and these assets provide many additional configuration options:

MovementParamsControl_Player is a component attached to ALS_Base_CharacterBP that is primarily responsible for configuring values such as: CMC->MaxWalkSpeed, CMC->Acceleration, CMC->WalkingDeceleration or CMC->GroundFriction.

MPCP performs its updates before the CharacterMovementComponent (CMC) update. In addition, it exposes two important delegates that allow custom code to be executed before the CMC refresh takes place:

I believe that, in the long run, this solution will prove to be an improvement over the previous approach inherited from ALSv4. Below, I have also highlighted the main functions responsible for loading and applying a new Movement Preset.

Another, even more significant change is related to the AGLS_Player_AnimInstanceCore class. Starting with AGLS v1.9, the player character now uses an entirely new AnimInstance class. The new animation blueprint is AGLS_PlayerAnimBP, which is built on top of AGLS_Player_AnimInstanceCore. As a result, the ALS_AnimBP asset has been marked as deprecated as of v1.9, although it remains included in the project.

Completely rebuilding the animation logic was a major challenge, but I believe the effort will ultimately pay off and make the animation framework much more production-ready. I will not go into great detail about AGLS_PlayerAnimBP, as it is a fairly complex asset. However, I would like to highlight some of the most important changes worth noting. First and foremost, the majority of variables are now declared in C++, including the primary animation states, which are represented using Enums.

Note: Unreal allows you to display a list of variables from parent classes. To do this, select the 'Show Inherited Variables' option in the MyBlueprint tab.

This change is quite important when integrating Enum variables that were originally declared as engine assets. A large portion of Blueprint classes, including ALS_Base_CharacterBP, still operate on their primary state values besed on Blueprint Enum assets. For example, to retrieve the list of the most important character states, you would typically call the interface function: BPI_Player_CharacterCore->BPI_Get_CurrentStates() However, in AGLS_PlayerAnimBP, the variables representing these states are now declared as C++ Enums, which are not directly compatible with Blueprint Enum assets by default. However, to solve this, you need to apply a simple transformation to the appropriate type:

Classes related to HumanAI already operate exclusively on Enums declared in C++, so in that case a different interface function should be used to retrieve the state information.

I mention this because the previous ALS_AnimBP relied heavily on Blueprint Enums, whereas the new implementation no longer does. Motion Matching now retrieves PoseSearchDatabases from an entirely new Chooser called AGLS_Player_PoseSearchDatabases, and many systems and functions have also been rewritten in C++.

The new Motion Matching implementation is based on several custom solutions, including:

🟢 CustomTrajectoryGenerating ᶜ⁺⁺

⚠️ PoseSearchDatabasesCollectors ᶜ⁺⁺ (experimental)

I will start with the trajectory-related improvements. In this area, I managed to remove several limitations that normally affect Pose Search. The new trajectory function library addresses three major issues:

The requirement to rely exclusively on CharacterMovementComponent capsule rotation methods such as CMC->bOrientRotationToMovement.

Missing trajectory generation during Root Motion animations.

The fact that Trajectory History is normally 2D and does not capture movement along the Z axis.

For Pose Search to correctly select animations that involve root bone rotation changes, it typically requires the use of the default capsule rotation techniques provided by the CharacterMovementComponent. The biggest issues appeared in cases such as TurnInPlace or RefaceFromStart animations. In GASP, the SandboxCharacter_CMC class continuously orients the capsule toward ControlRotation.Yaw, even while the character is idle. If the RootOffset node were removed from the AnimInstance, the character mesh would rotate with every camera movement, even while standing still. As a result, the desynchronization between GetActorRotation() and GetRootRotation() could reach as much as 180 degrees. The Mover plugin largely eliminates this limitation, but I wanted to solve the problem while still using the CharacterMovementComponent. In the end, I believe I managed to do so. To achieve this, I created the 🔸PoseSearchGenerateTrajectory(Extended) function. It provides significantly more input parameters than the default implementation, allowing for much greater control over trajectory generation. Facing for each sample is calculated differently than the default, or more precisely, for each sample the theoretical time to the given orientation is taken into account, rather than simply copying ControlRotation.Yaw.

The second major improvement is that trajectories can now also be generated from Root Motion. This approach is currently used by HumansAI, where the inputs provided to GenerateTrajectory are the ∂Acceleration and ∂Velocity values calculated by the functions shown below:

Here is an example of Motion Matching in action, where the movement source is a Montage animation:

Another important feature related to Pose Search is an attempt to optimize the databases related to Pose Search databases. By default, every asset accessible to the Chooser responsible for selecting PoseSearchDatabases is referenced through Hard References. My goal was to reduce the number of animation databases that need to remain loaded at any given time. Some locomotion systems, such as Covering or certain movement modes like Jogging, are used relatively infrequently - or sometimes not at all during gameplay. For this reason, the Pose Search Chooser now returns database assets as Soft References. To support asynchronous asset loading, the PoseSearchDatabasesCollector ᶜ⁺⁺ and PoseSearchAllMovementsCollector ᶜ⁺⁺ classes were created, the purpose of which is to catalog PSDs in order to load the entire movement rather than individual PSD.

⚠️ Note: This is a highly experimental approach. The final optimization gains may not be worth the momentary FPS drops during loading. Async loading in a Packaged project is much more efficient than loading from the editor. If you want to avoid this approach, you should create HardReferences to the PSD somewhere in the scene, which will force the engine to constantly store them in memory.

The AGLS_AI_AnimBP class has also undergone major changes. Most notably, a large portion of the Blueprint logic has been replaced with C++. This may provide a modest improvement in animation processing performance. Earlier, I also mentioned the new trajectory-related functionality and the MovementParamsControlComponent ᶜ⁺⁺, both of which are now utilized by HumanAI. The PoseSearchDatabase assets used by HumanAI have been specifically prepared for this character class. Previously, both the player and AI shared the same databases and normalization assets. For v1.9, I decided to separate these systems, allowing the animation frameworks for the two different controller types to evolve independently.

The HumanAI Pose Search assets can be found in: MachingData->Human_AI:

In AGLS v1.9, I also introduced more aggressive LOD levels for the AnimInstance. For example, at LOD3, Pose Search uses a much more limited set of animation databases, which should reduce the amount of work required when searching for the best matching pose. The LOD behavior can be previewed using the console command:

AGLS.HumanAI.Optimization.ForceLodState

There are many more technical changes than the ones described here, but I believe I have covered the most important ones.

What do all of these changes improve?

Overall, the entire locomotion system should benefit from these improvements, including Crawling, Crouching, and the movement systems used by HumanAI. In addition, animation performance should also improve. That being said, it is important to acknowledge that the final animation quality and smoothness are still not quite on the same level as those found in the Game Animation Sample Project (GASP). Naturally, this raises the question: why? Unfortunately, I do not have a definitive answer. Most likely, I still do not fully understand Pose Search well enough to calibrate it with the same level of precision achieved by Epic Games. I also have the impression that the system performs exceptionally well when used with the UEFN skeleton, and that some of its strengths are difficult to reproduce on other skeletons. Pose Search requires well-chosen values ​​of many variables to work, e.g. the number of trajectory samples, their sampling time, data in Channels, etc. However, despite this, I think that overall I managed to prepare a pretty good animation system.

Crawling locomotion example:

HumanAI walking example (LOD0):

Other important changes included in AGLS v1.9:

➊ MeleeCombatComponent implementation for HumanAI and CompanionAI.

Starting with this version, the AI ​​can also engage in melee combat if environmental conditions allow. The default input bindings for the player, when using a keyboard, are:

Melee Attack = key 'V'

Melee Dodge = key 'C'

The default inputs map for a gamepad is as follows:

Example of a 1 vs. 3 combat scenario. In this case, the HumansAI characters do not have any firearms equipped, causing their controllers to attempt to engage the target using the Melee Combat system.

HumanAI ma też możliwość upuszczania oraz podnoszenia broni podczas walki.

Example 2 (Player with CompanionAI) vs 3 fight:

List of smaller changes:

Fixed a bug where a TraversalAction could be interrupted incorrectly when entering Ragdoll.

Improved Dynamic Foot Transitions and Additive Foot Transitions when changing the Overlay State or when the player starts aiming.

Added EarlyStoppingMontage support for interactions such as PickNewRifle and PickNewPistol. This allows interactions to end more quickly when the player provides movement input.

Replaced most animation curves that used EnableFootIK with DisableFootIK. Before the Motion Matching update, the system relied on the EnableFootIK curve, but this occasionally caused blending issues when the "Enable" and "Disable" states overlapped.

Fixed a crash in packaged builds caused by UseRawData when attempting to retrieve bone transforms directly from animations. In packaged builds, access to raw animation data is restricted because animations are stored in a compressed format.

Fixed an issue in packaged builds where interactions could fail if the required asset had not yet been loaded into memory. For example, when attempting to pick up a weapon, pressing 'E' would not activate the initial interaction on the first attempt, requiring the player to press the key twice. As of v1.9, this bug should no longer occur.

██████▶ 𝐀𝐆𝐋𝐒 ᴠ1.9.1 𝐂𝐇𝐀𝐍𝐆𝐄𝐒 ◀██████

Update v1.9.1 was mainly focused on fixing many bugs related to the new Pose Search setup for both the player and AI. This version also includes many other fixes, with the main changes being as follows:

Motion Matching for the player has undergone many major changes:

The BlendStack logic has been updated, with many values in the Steering and Orientation Warping nodes being changed. An additional Stride Warping node [Experimental] has also been added inside the Motion Matching node. Its purpose is to correct foot placement when the animation speed differs significantly from the capsule speed, for example due to collision. Overall, I feel that the new parameters are better tuned to the animations.

The Movement Analysis functions have also been changed, including values such as FacingDelta and IsCircing.

Many PoseSearchDatabase assets have been rebuilt, with major changes applied to the databases in the Spins category, which should improve their matching.

For MovementParamsControl_Player, I have taken Root Motion animations into account, which should improve pose matching after a Montage animation ends

I expanded several PoseSearchDatabases with additional animations, including, for example, RelaxedRun_Diamonds

The PoseSearchSchema assets have undergone many changes. The key one, however, is AGLS_PSS_Loops, which previously did not index Facing and took capsule speed differences relative to the animation into account to a lesser extent

The “AGLS_Player_PoseSearchDatabases” Chooser itself has also been rebuilt

Fixed a bug related to jumping down from ledges while Crouching. Previously, landing animations were not selected in this case. The issue was caused by DatabaseConstBias and ContinuingPoseBias values being too high

Fixed Pose Search related to TurnInPlace animations. Previously, Steering remained active for too long in relation to the Turn animation, which caused the root bone to slide when the animation was already indicating an idle pose

Added TurnInPlace animations for the Crouching state

Removed the code controlling ActorRotation() from PredictableJumpAction during Montage playback, which means calling LockUpdatingRotation() is no longer necessary. Rotation correction is handled through Motion Warping

RollAction has been significantly rebuilt. A proper Chooser has been added to select the Animation Montage, and Motion Warping has also been implemented to correct the Root Motion trajectory

Added an additional actor, “AGLS_PoseSearchRebuilderForCharacters”, which allows all PoseSearchDatabases for both the player and HumanAI to be fully loaded at once. After the assets are loaded, indexed poses are also rebuilt when necessary. This process may usually be required after making changes to the skeleton or to animations indexed by Pose Search

Added interpolation for the SpineRotation value for both the player and HumanAI when AimingRotation is no longer active. Without this change, an issue occurred during the transition from -90 to 90

pine Aiming control nodes have been reduced to only 3 spine bones. Previously, the Pelvis was also rotated, which I considered unnecessary

Disabled the ability to perform a Melee Attack/Dodge when the player is not in MovementState = Grounded

As with Motion Matching for the player, the “AGLS_AI_AnimBP” class and other assets related to it have undergone some changes aimed at generally improving Pose Search behavior

Fixed an issue related to HumanAI Fall Damage. Previously, after critical fall damage when HealthPoints = 0, the HumanAI death code was not executed. This should now work correctly

For CompanionAI, the code controlling the FocusActor position has been fixed. Previously, at a certain distance between the AI and the player, the BT_Service set an incorrect FocusActor position

Fixed the following error: LogScript: Warning: Script Msg: Attempted to access index -1 from array “NormalizedScales” of length 7 in “UI_WheeledOverlaysMenu.UI_WheeledOverlaysMenu_C”! LogScript: Warning: Script Msg called by: UI_WheeledOverlaysMenu_C

Added many additional descriptions for Blueprint assets

██████▶ 𝐀𝐆𝐋𝐒 ᴠ1.9.2 𝐂𝐇𝐀𝐍𝐆𝐄𝐒 ◀██████

🧩 AGLS v1.9.2 is the result of my continued work on learning and improving the Pose Search system. I still wasn't satisfied with how it performed in AGLS, so I decided to carry out a third full iteration of the Motion Matching implementation.

In the end, I decided to rely more heavily on a single primary Pose Search Channel instead of creating multiple channels based on different animation database types. I also merged several Pose Search Databases into a single main database, adjusted the Steering parameters, and updated parts of the Movement Analysis logic, including functions such as IsPivoting() and ShouldSpinTransition().

🟩 Overall, v1.9.2 introduces significant improvements to the core locomotion system for both the player character and HumanAI. This version also adds Gait Transition animations, such as Walk-to-Run and Run-to-Walk.

I hope this will be the last such thorough overhaul of Pose Search in the project.😤

Other major changes in v1.9.2:

Improved Ragdoll system, including a fix for the bug that occurred when entering Ragdoll while Crawling. Added a Play Rate parameter for Fall animation, as well as rotation interpolation while Ragdoll is active, improving the stability of Physics Constraints for attached equipment such as rifles and pistols.

Improved the Sliding System by increasing friction.

Fixed the HumansAI PatrolingInteractions system. Previously, the configured range of PathPoint indices used for searching Smart Objects was being ignored.

Changed the basis for calculating Aiming Rotation, including Spine Rotation. Previously, DeltaRotation was calculated relative to the Root Transform. It is now calculated relative to the Character Transform, which should resolve the issue of aiming overshooting while the character is moving.

▶ DOWNLOAD PROJECT FILES (v1.9.2, UE5.7) ◀

DOWNLOAD PROJECT FILES (v1.9.1, UE5.7)

DOWNLOAD PROJECT FILES (v1.9.0, UE5.7, No Replication)

▶️ AGLS Tutorials Playlist ◀️

I would also like to mention an important point to keep in mind when extracting the project files. Normally, little attention is paid to the folder in which a project is stored. However, asset paths are subject to length limitations. AGLS contains a large number of subfolders and assets with relatively long names. As a result, storing the project in a directory with a very long path may cause issues during packaging. For example, in my case, the project files are stored in the ':\Unreal Projects\UE5.7' directory. If it were something like ':\Epic Games\Unreal Engine 5.7\Projects\AdventureGameLocomotionSystem\', you might get an error message about the asset path exceeding the maximum number of characters.

Unreal Engine 5.8 Addtive Required Content ⚠️

Download required content for UE5.8.1 engine

If you need additional information related to this engine version and conversion instructions, you can go to this POST

Can it be used for commercial purposes?Yes, but there are certain limitations. Most importantly, distributing project files (in the same way I provide them) is strictly prohibited. For commercial purposes, distribution should only be in the form of a packaged project (preferably in shipping configuration). This means that publication should be done in a format that does not allow easy extraction of AGLS project content. In short, the permitted format would be a compiled program, such as a .exe file for Windows.

It is worth reading the full license of use. You can find it at the link (PDF) or in the attachments under the post.

📄 it is worth taking a look at the documents in the attachments 📄

Information about project packaging.In this version of the project, I left a few folders related to the packaging process I performed on my own computer — these include the 'Binaries' and 'Intermediate' directories for project and plugins folders. If any errors occur during packaging, it’s worth considering completely deleting these directories from the project files. Additionally, in such cases, it’s recommended to use the 'Full Rebuild' option.

Some important Discord threads:

Aiming looking wreid for Rifle overlay

IWALS Documentation (created by Minty and Anarky)

I would also like to mention a small request. Namely, it is about private messages sent on Patreon. I would ask that this method of communication be limited, due to its large constraints. If your question is about the project, please send it on the Discord server, or in the comments under the Patreon post. In other cases, I would suggest an email or possibly via a Patreon mailbox. Please note that due to the large number of messages, I am unable to reply to all of them. Most often I answer questions asked on the Discord server, followed by emails, comments under the Patreon post, and Patreon private messages. Thank you for your understanding.

Files

UE5.7 - Melee Combat System | Player & AI | AGLS v1.9 Presentation

A presentation of the full Melee Combat system implemented for the AdventureGameLocomotionSystem (AGLS) project in version v1.9. This version is still under development and is not currently available for download. In this video, I focused on showcasing combat against HumanAI. From now on, AI can switch to melee combat in certain situations. This state is usually activated when a HumanAI character has no weapon, and it has not been determined that it should enter the "surrender self" logic. Combat scenarios can take place in formats such as 1 vs 1, 1 vs 3, or full battle scenes like 4 vs 4. Regarding changes for the player, the most important new feature compared to v1.8 is the addition of a simple dodge mechanic. Support my work at: https://www.patreon.com/JakubW 00:00 Player vs AI - No Weapons 02:30 Player vs AI - Axe 03:06 HumanAI Surrender self 03:40 Player vs AI - Holding Gun 06:20 1 vs 2 - Examples 07:40 1 vs 3 - Examples 09:05 HumansAI vs Zombies 10:06 3 vs 3 or more - Examples

Comments

Skilly

Thanks a lot ❤️❤️

INTIAMAUTA

Let's try it, your work is appreciated, thank you

Jony

Th3Cleaner @Unrealnewb

Hi, this newest build is so good! I really like the extra time on mechanics. Question: if I want to add visual inventory, do I build from the current or add a new one? and I am sure there is that "one" place to start, Open component and wire in new... thanks for any guidance

JafeerYoung

replace with 1.9 plugins + open the project file in notes and enable the plugins

Jakub W

Hi. Regarding UE 5.7 built from Source Code, I do not have much experience in this area. I have never used that distribution myself, so it is difficult for me to determine why the AGLS code does not work with the Source Code version when, in theory, they are the same engine version. I also assume that the issue is occurring on Windows. As far as I remember, up until UE 5.6, AGLS could be launched using a Source Code build with relatively few required fixes. However, at some point something changed significantly in the engine, and AGLS was no longer compatible. I do not know whether this was caused directly by changes on my side or by modifications within Unreal Engine itself. Unfortunately, I am also not familiar with the exact workflow for opening existing projects in a UE5 Source Code build. For example: - When you select AGLS in the Unreal Project Browser, does the engine prompt you to compile the C++ code? - Is it necessary to convert or rebuild AGLS as a C++ project? - Do the plugins need to be installed in the engine directory rather than the project directory? - At what exact step does the issue occur? There are many things I don't understand, so I can't help much.

INTIAMAUTA

The project is going very well, what do you think about adding non-aggressive AI NPCs, for example, escaped animals or humans for missions or vendors?

Jakub W

Hi. Well, I think it depends on many factors, but I’ll try to highlight the things that are worth paying attention to. First and foremost, it is a good idea to design your modifications to AGLS in a way that allows asset replacements and updates to remain compatible. This can make future upgrades—for example, from v1.9 to v2.0—significantly easier. As a general rule, I recommend implementing custom systems in new components and child classes whenever possible. This gives you the ability to override functions declared in both C++ and Blueprints (provided that they are public, and in the case of C++, they use the BlueprintNativeEvent macro). In the video below, I demonstrate several examples of how changes can be implemented without significantly altering the core AGLS structure. Of course, this approach will not be possible in every situation, but in many cases it can be very useful. In the context of 'visual inventory,' unfortunately, I don't know what the default assumptions are for this system. I assume it's primarily related to Widgets. In this case, AGLS doesn't have a single main component managing Widgets, and instances are created primarily in the ALS_Base_CharacterBP and ALS_Player_Controller classes during BeginPlay. Because of this, I think you could either extend the existing Widget Blueprint classes or create entirely new widget assets, depending on your requirements.

Jakub W

Thanks for the feedback. As for what I would still like to try adding, neutral AI is something I have planned. However, at the moment I am only considering this system in relation to HumansAI. I probably will never work on animal AI.

HASHIR RAHEEL

bro that's awesome but i can't make character shoot at me in new level and even i can just hand fight them not gun fight can you please help me

Jason Wathen

First sorry so long: Your project has almost everything I want, I have used it for a very long time. The only request I have or improvement I think would make this perfect is adding weapon system like Advanced Thirdperson Shooter has. Dual wield weapons and multiple weapons slots to use. The dev for ATPS has a tutorial to integrating with ALS V4 but I do not want to try it with your project and destroy something I can't fix. If it is possible to add that type of weapon system let me know I do not mind paying more than the monthly Patreon to get that done. https://www.youtube.com/watch?v=uIkFkYBt9xY&t=33s Video linked is an older project it has been updated but this gunslinger style is what I need with your project. Animation is not my strong point at all.

Jakub W

⚠️ Important information. I am currently working on fixing several bugs and improving some parts of the project. This primarily concerns the new Motion Matching system. There are a few areas that still require adjustments. As a result, v1.9.1 should be released soon, and I would recommend downloading it once the files become available :)

Jakub W

Hi. It’s worth reviewing the list of tutorials related to AGLS (link included in this post). If you created a new level, it requires some initial setup. For example, if you created a child class from 'ALS_AnimManBP', then for the AI to react to instances of that class, you must include the class name in the ActorTags. There is a tutorial covering this in the playlist. The issue could also be caused by something else, such as incorrectly configured collisions. If a TriggerBox or another invisible object has its collision type set to WorldStatic, WorldDynamic, or Pawn, then a trace performed by the ShootingSystem will return InitOverlap as true. The PDF file "AGLS Basic Informations" contains more details about this topic. Pay close attention to the collision settings in your level, as well as the NavMesh configuration.

INTIAMAUTA

Hi Jakub, Unreal Engine 5.8 has just been released. Will you explore its compatibility with this version?

Jony

The download link for the files for 1.9.1 is for the Demo and not for the project.

Jakub W

Ohh, forgive me for that mistake. It should be fine now.🤦‍♂️

Thisisme Mario1

Hello Jakub, I'm using and supporting AGLS and you since 1 year . As you can imaging I did lots of work on my game, I created and merged tones of codes /anim into the current ALS_AnimBP and in the ALS chara BP (horse riding, ninja fluid, ropes climbing, pole climb, wall riding, etc ). So I'm worried to read that ALS_AnimBP will be deprecated starting 1.9. I really like the melee combat AI , if I keep the current ALS_AnimBP / als character and merge the 1.9 will it work ? I will see if I can merge everything into the new AGLS_anim BP, but it's clearly not a trivial amount of work, probably 4/6 weeks, and If I can't manage to do it I'll have to stop upgrading... definitively which would be a shame really. Until now I added all my code to a child bp of the ALS_anim_BP so I guess the reparenting won't work as you change significantly the BP ? As always thank you very much for your work.

Jakub W

Hi, Thanks for your interest in my work. Regarding your question and concerns, I completely understand the issue. A completely new AnimInstance is a fairly drastic change, but I simply had to make that decision for several reasons. I came to the conclusion that it would be easier for me to start from scratch, especially with a C++ class serving as the base for the new AnimBP architecture. Additionally, I was having such significant problems with PoseSearch configuration that I almost convinced myself there was something wrong with ALS_AnimBP itself (although, of course, that was probably not the real issue). Migrating to the new AnimBP would have been much easier if your previous code had been implemented using techniques such as BlueprintAnimationInterfaces, and if you had previously created a child class derived from ALS_AnimBP and extended your code there. Animation logic related to systems such as horse riding, for example, could likely be simply "injected" into either: LinkedAnimLayer(Locomotion_GameplayLogic), LinkedAnimLayer(PostRootOffset) This is the approach I used for the Swimming System, which means integrating it with the new base AnimInstance class takes only a few minutes. However, if you did not use these kinds of solutions when implementing your own modifications, then you'll have to decide for yourself whether upgrading to AGLS v1.9.1 makes sense. If your primary interest is Melee Combat, you could try integrating it into an older version of AGLS. However, I suspect that the biggest obstacle in that case would be the C++ code, which would likely require some modifications and adjustments. Swimming animations logic example: https://snipboard.io/xbS093.jpg

tygra78

Yeah, I'm also waiting for plugins update for 5.8

Thisisme Mario1

I'll try to the limit of my knowledges ... hoping will be enough. Thank you for answering , I really think of you as a kind of genius in your field and I've been working with some famous companies out there. Cheers

Christopher Nascimento

Although you made it clear that the project is only for Windows, I decided to try to get it to work on a Mac somehow… and actually, it was pretty easy. Below is a step-by-step guide to the changes that can be made to extend the project’s compatibility to Mac, so that other Mac users can also support the project’s development. * (Jakub) The changes in step 2 alone are enough to ensure that future versions of the project will be compatible with Mac, without affecting distribution on other platforms, I believe. --- (Mac users only) Make sure you have Xcode (App Store) and the Xcode Command Line Tools (Terminal.app > xcode-select --install) installed! 1. Set up the Xcode project (Mac users only): 1.1. Right-click on the .uproject file > Generate Xcode project (or Services > Generate Xcode project); - If nothing happens: open Terminal and run the code below, verifying that the ENGINE_SCRIPT path is correct and updating the PROJECT_PATH according to your AGLS project (right-click on the .uproject file, hold down the Option key > Copy “AGLS.uproject” to Pathname): ENGINE_SCRIPT="/Users/Shared/Epic Games/UE_5.7/Engine/Build/BatchFiles/Mac/GenerateProjectFiles.sh" PROJECT_PATH="/Users/YOUR_USER/Path/To/AGLS v1.9.1 UE5.7/AGLS.uproject" sh "$ENGINE_SCRIPT" -project="$PROJECT_PATH" -game 1.2. Run the created .xcworkspace. Xcode will open, configured for the project; 1.3. Change the project scheme from “AGLS > My Mac” to “AGLSEditor > My Mac”. 2. Enable compatibility: * The Xcode compiler is more restrictive than the Windows compiler, so you'll need to make a few adjustments to ensure the plugins compile successfully. 2.1. Navigate to ‘/Plugins/JakubCableComponent/Source/JakubCableComponent’ and update the ‘JakubCableComponent.Build.cs’ file (line 18): // PrivateIncludePaths.Add("CableComponent/Private"); PrivateIncludePaths.Add("JakubCableComponent/Private"); 2.2. Navigate to ‘/Plugins/JakubAnimNodes’ and update the “WhitelistPlatforms” in the ‘JakubAnimNodes.uplugin’ file (lines 22 and 31) by adding “Mac” to the list: "WhitelistPlatforms": [ "Win64", "Linux", "Mac" ] 2.3. Navigate to ‘/Plugins/JakubCableComponent/Source/JakubCableComponent/Private’ and update the ‘JakubCableComponentBPLibrary.cpp’ file (line 8): //#include "..\Public\JakubCableComponentBPLibrary.h" #include "../Public/JakubCableComponentBPLibrary.h" 2.4. Navigate to ‘/Plugins/ClimbingNavigation/Source/ClimbingNavigation/Private’ and update the ‘AISense_BetterSight.cpp’ file (line 621): //return FTraceHandle::FTraceHandle(); return FTraceHandle(); 2.5. Navigate to ‘/Plugins/CombatCore/Source/CombatCore/Private’ and update the ‘DyingSequencesDatabase.cpp’ file (line 299): //FLinearColor TextColor = FLinearColor::LerpUsingHSV(FLinearColor(0, 1, 0, 1), FColor(1, 0.0, 0.6, 1), ForColorLerp); FLinearColor TextColor = FLinearColor::LerpUsingHSV(FLinearColor(0, 1, 0, 1), FColor(1, 0, 0, 1), ForColorLerp); 3. Xcode > Project > Build (Command + B, Mac users only). 3.1. After building, run the .uproject file by double-clicking it. 3.2. Enjoy!

Jakub W

Wow. Thank you very much for this information. I’ll try to take a closer look at your observations and implement the changes you suggested. If the aspects you mentioned really were the source of the problem, then it means I was unnecessarily avoiding this area more than I should have 😅. Thanks again

Jakub W

Hi, As for the equipment system, AGLS currently allows the player to store up to three pistol models in their inventory. However, this requires having a backpack, which you may not want to use. A system exactly like the one shown in the video you sent does not currently exist in AGLS, because I deliberately chose to approach a similar feature in a somewhat different way. I do plan to add a similar mechanic for rifles, and the intended workflow would be similar to how pistols are currently handled. Will I implement something practically identical to what is shown in the video? At the moment, it’s difficult for me to say. Here is a video demonstrating the Pistol Switching system: https://youtu.be/8suMBya6LBw?si=n0f3Qwy37K1oBSM9&t=508

Dai Tianqi

It seems to break the HoldHostage and StealthFinisher system. Nothing happen when I click left mouse button when Finish or HoldHostage UI prompt shows.

Galen

Hello Jakub, Any chance of getting a retarget of Quinn similar to Manny_BetterRetarget so that female characters don't look like bodybuilders?

Ebony Cobb

How do I use the melee combat? I notice that when I am in the gym and I left click, he doesn't swing.

Vincent Nihouarn

Hi, First, I really want to thank you for your work on IWALS. It is an incredibly impressive project. The amount of features, options, and systems you have built into it is honestly amazing, and it is clear that a huge amount of work went into it. I also want to say that I did not just try it quickly. I used IWALS seriously for months while building a demo, and it helped me a lot to get the functionality I needed at the time. That said, I wanted to share some constructive feedback about why I do not think I will continue using it as the base for my next projects, at least for now. For me, the main issue is not the feature set. The feature set is actually one of the most impressive parts of IWALS. The issue is more the overall feeling of basic locomotion and traversal. Compared to Epic’s Game Animation Sample with Motion Matching, moving through the world in IWALS does not feel as fluid, freeing, or satisfying to me. In the Epic sample, simply running around, jumping, climbing, and navigating the environment feels very smooth and pleasant. With IWALS, I often feel that the basic movement is a bit more clunky, even though the system has many more gameplay features. For example, jumping does not feel very satisfying to me. I am not completely sure why. Maybe the character slows down slightly before jumping, or maybe the jump height and distance feel too restrained. I tried to increase the jump parameters in the Character Movement Component, but it only seemed to affect the standing jump, not the moving jump. I looked through the Character Blueprint, Animation Blueprint, animations, and related logic, but I could not clearly find where to tune that behavior. I had a similar feeling with free climbing. When reaching the top of a cliff or ledge, it can be difficult to get the character to actually climb over the edge and continue walking. Sometimes the character seems to look for another handhold instead of committing to the climb-up/mantle transition. I was able to improve it a bit by adding a simple plane at the top of the cliff, but even then it often took a few tries before the character climbed up properly. So, from my perspective as a user, I think IWALS could benefit a lot from a polish-focused phase. Instead of adding more features for a while, I would personally love to see more focus on making the core locomotion feel really good: running, jumping, climbing, crouching, crawling, moving through tight spaces, and generally navigating the world. My ideal version of IWALS would be something where the basic locomotion feels closer to Epic’s Game Animation Sample, while IWALS keeps all the extra gameplay systems and traversal features you have built. I realize this may be a huge architectural change and not something simple to do, but as a user that is the direction that would make IWALS much more usable for me. Another thing that would help a lot is a simplified top-level control layer for artists and designers. Since many Character Movement Component values seem to be overridden by blueprint logic, animation logic, or functions, it can be difficult to know where to make simple gameplay changes. For example, it would be very useful to have clear high-level parameters like: Can Jump Can Crouch Force Crouch Can Sprint Allow Running Jump Height Jump Distance Climbing Enabled Crawling Enabled That kind of layer would make it much easier to control locomotion behavior with trigger volumes or gameplay logic. For example, entering a volume could disable running, force crouch, disable jumping, or modify movement behavior without needing to dig deeply into several blueprints and animation systems. I also think clearer documentation and a more standard controller/keyboard mapping would help a lot. Because IWALS includes so many features, it is sometimes difficult to know what actions are available or how to trigger them. A more familiar third-person/open-world controller layout would make the system much easier to approach. To summarize my feedback: IWALS is extremely impressive and feature-rich I used it seriously for months in a demo For my next projects, I am moving away from it mostly because the core locomotion does not feel as fluid and satisfying as Epic’s Motion Matching sample I would personally prefer fewer new features for now and more polish on the basic movement experience More documentation and simplified high-level control parameters would make the system much easier to modify and use in real projects Of course, I may be missing obvious things. I am not an expert on every part of the system, and maybe some of these controls already exist and I simply did not find them. So please take this as user feedback, not as a harsh judgment. I really appreciate the work you have done. IWALS is already very impressive. I just think it could become much stronger by focusing more on polish, clarity, and the feel of core locomotion.

Jakub W

Stealth Finishers are triggered with the 'V' key. Hold Hostage should also be available when you're holding a knife, aiming, and pressing the 'V' key. However, the Hold Hostage system does not work very well, as it hasn't been developed or maintained for quite some time.

Jakub W

Hi. By default, the ALS_Manny_CharacterBP class includes two implementations of meshes based on the UE5 Skeleton: Manny and Quinn. By pressing the 'M' key, you can switch between these models, with each using a different default OverlayState pose. If you want to further improve the overall retargeting, you can duplicate the IK_UE5_Mannequin_Retarget asset and then apply the copy in Manny_BetterRetarget_AnimInst. You can also try applying an additional additive pose in the AnimGraph to further correct the character's pose.

Jakub W

By default: MeleeAttack = 'V' key, MeleeDodge = 'C'

Jakub W

Hi. Thank you for your interest in my work and for taking the time to share your feedback. I'll try to respond to the points and questions you raised. Before I do, however, I'd like to clarify one important thing. In your feedback, you refer to the project as AGLS, not IWALS. IWALS is one of my older projects that I originally started for UE4, and it was based on ALSv4. After reading your feedback and thoughts, it's hard for me to disagree with the points you raised. From my perspective, though, some aspects look a little different. Starting with the core locomotion system - Stand Walk, Stand Run, Crouch Walk, and so on. I completely agree that, compared to GASP, the smoothness and stability are not nearly as impressive. There are several reasons for this, and I mentioned the most important ones in this post. AGLS is still built around the UE4 Mannequin skeleton, which naturally makes the project less practical in some situations. I deliberately chose to stay with that hierarchy because of my animation source files and my other projects that are based on AGLS. Designing a Pose Search system completely from scratch is an enormous challenge that requires a great deal of experience (even when GASP is available as a reference). For v1.9.1, I tried as hard as possible to get the locomotion quality closer to GASP, but I wasn't able to fully achieve that goal. The new Pose Search implementation in v1.9.1 was probably the most difficult task I've ever worked on, and I spent an enormous amount of time on it. Despite all my efforts, I couldn't reach the same quality as GASP. In fact, I eventually came to the conclusion that Pose Search performs exceptionally well only with the UEFN skeleton or within the GASP project itself. I'm not aware of anyone who has implemented a custom Pose Search system from scratch that reaches that same level of quality. Of course, AGLS required a different approach in many areas, which also meant I had to write a large number of C++ functions related to Motion Matching specifically for CharacterMovementComponent. I recommend reading that post carefully to better understand the challenges I faced. The word "satisfying" can also be interpreted in many different ways. In my opinion, that aspect should ultimately be the responsibility of the game developer, whereas I am not actually developing a game. AGLS should be viewed more as a framework or layout than as a finished game sample. I also don't want to spend months focusing on a single feature, such as jumping. AGLS is also my personal learning platform. As it evolves, I use it to expand my knowledge of Unreal Engine. I'm not a professional animator, and animation is honestly not something I particularly enjoy working on. Because of that, it's perfectly fair to say that the jumping system - especially Predictable Jumps - can feel stiff. To significantly improve the overall quality of that system, high-quality animations would be essential, along with multiple animation variants. I simply can't meet every expectation, because I feel I would eventually stop making progress altogether. I try to design mechanics with a high level of detail while maintaining a certain gameplay feel. At the same time, I intentionally make compromises because I'm not creating a complete game. I also don't have extensive experience as a gamer myself, so you'll have to forgive some of the stiffness and limited responsiveness of the mechanics I present. One area where I do think I could improve is providing a simpler way to control the player's core gameplay mechanics. As you mentioned, parameters such as Can Jump, Can Crouch, or Force Crouch would definitely be useful. That's something that could realistically be implemented through an Actor Component or an Interface. Regarding the default input bindings, I also agree that this aspect is largely dependent on the developers of the final game. My own configuration certainly isn't ideal or particularly intuitive—probably in part because I've never really played games with a gamepad. Fortunately, Input Bindings are, in my opinion, one of the easier aspects of the project to customize. To summarize, I agree with many of the points you made. As I mentioned earlier, I'm still developing AGLS entirely on my own, and I continue to treat it as a way of expanding my knowledge of Unreal Engine. Sharing the projects I work on is simply the result of that effort, with the hope that they can help others build their own gameplay systems instead of having to create everything from scratch. I hope I understood your feedback correctly, and that my response also makes my perspective clear. Best regards.

Vincent Nihouarn

Thank you so much for taking the time to give me such a detailed answer. What you said makes a lot of sense. All of it, honestly. Like I suspected, there is so much work involved in what you are building, and I clearly do not understand half of it. Haha. I understand better now why some things work the way they do, and I really appreciate you taking my comments seriously, especially the idea of maybe providing a simpler way to control some of the core mechanics. I also totally understand your lack of interest in purely animation-related work. I am kind of the same way, so that makes sense to me. So thanks again for your answer and for all the work you do. Your project is still the best locomotion/adventure game framework available for Unreal. I guess I was just being a bit greedy because I wish it could do everything perfectly for my specific needs. Haha. Thanks again!

Jason Wathen

Thank you for the reply, I have been using your system for sometime. I am familiar with the pistol system and backpack. Was just looking for logic to add dual shooting and shoot from hip. Like a quick shot system. Either way love the project and looking forward to your future work.

Jason Wathen

Hello, I have a question about changing the mesh on the fly using “C” where is that information stored? I would like to use it to help with a character selection screen.

ali faruk külte

The game starts with constant stuttering but clears up afterwards; have you tried pre-caching or populating the derived data cache?

TryHarder

Hi just downloaded 1.9.2 and just run the demo scene the AI's legs are folded under themselves when they crouch and the player crouched aim with rifle is all over the place too, am missing something?

TryHarder

So I've downloaded v1.9.0 v1.91 and v1.92 and in all using 5.7.4 the AI with a rifle are sunk in the floor with their legs folded under them when crouching, is there something I'm missing? Thank you.

Jakub W

Hi. Thanks for your interest in my work. Regarding the features you'd like to add to the project - namely dual shooting and shooting from the hip - there isn't a single correct implementation approach, but I can suggest a few things that are worth considering. If you'd like to change the weapon's default poses, you'll most likely need an additional Overlay State animation (I assume that's what you mean by shoot from the hip). For example, the ALS_Props_Rifle_AK-47_Poses asset contains a collection of poses that are blended based on various variables such as GaitWeight, Stance, and RotationMode. You would need to create a similar set of poses (probably multiple sequences depending on the rifle type, just as AGLS does), making sure to account for the IK bones while animating. After that, you would need to configure the layering animation curves and finally blend the new animation into the existing Overlay logic, most likely in the ALS_OverlayState_Rifle asset. As for the term Dual Shooting, unfortunately I'm not entirely sure what you mean, so I can't really suggest a specific implementation approach for that.

Jakub W

By default, the 'C' key triggers a Melee Dodge. Runtime SkeletalMesh switching can be triggered with the 'M' key. This logic is located in ALS_AnimMan_CharacterBP → EventGraph. However, this method works by using 'Set Master Pose', which is only suitable when the Skeletal Meshes that have same bones hierarchy and proportions

Jakub W

Hi. I assume you're referring to the stuttering that occurs while playing in the editor, correct? If that's the case, then yes—this is expected behavior. The FPS drops are caused by Async Loading. AGLS loads many assets into memory only when they are actually needed. This includes, among other things: • Overlay State AnimInstances • Blueprint Abilities • Pose Search Databases • HumanAI Characters and Controllers and many other assets. This approach helps reduce overall memory usage, but during the loading process you'll notice temporary FPS drops. In the editor, this usually happens only once during the initial loading phase. Unreal Editor does not automatically unload previously loaded assets during normal operation, even when the Garbage Collector runs. If you'd prefer to avoid this behavior, you can create hard references to those assets somewhere in project/level. This forces the engine to keep them permanently loaded in RAM. In a packaged build, Async Loading is significantly faster and is usually unnoticeable. Of course, loading speed also depends on your hardware, including CPU performance, storage read speed, and other system characteristics.

Jakub W

Hi. I've never encountered this issue before, and no one has reported a similar problem to me. To better understand what's happening, it would be helpful if you could provide screenshots or a video demonstrating the bug. You can post about it on the Discord server.

TryHarder

Hi thank you for the reply yes I've posted in Project talk on Discord and I'm working through it, it's very odd, but I'm going to try to replace the animations with ones posted on discord and see if that fixes it.

Jorgects

Hey Jakub, awesome work! As a small note, I've been dabbling with a version of AGLS 1.9.2 in 5.8 and I've been finding issues with MetaSounds of the footsteps system, with missing sounds and logs pointing towards missing MetaSound graph registries. LogMetaSound: Error: Could not find graph with registry graph key 'External_None.72ADD4064ACFB1629270438A32A2C1B3_1.0, /Game/Audio/Foley/MetaSounds/MSS_FoleySound_Run_Dynamic/MSS_FoleySound_Run_Dynamic, 257677'. Weirdly, this errors only start occurring the second time PiE is triggered. I've found that changing the var au.MetaSound.DisableAsyncGraphRegistration to true fixes the issue with the audio playing correctly always. However, this produces MetaSounds to not load asynchronous and possible hitches occurring when a new sound is required. Hoping this can help with your porting to 5.8 if it comes at some point!

TryHarder

I re-imported the FBX's for rifle crouch pose from the discord post and it all works now! Still don't know what caused the corruption.

Jakub W

I understood that the problem had been fixed. Now that you've mentioned it was related to an animation, I remembered that I've actually encountered a very similar issue before. In my case, it happened once on a different computer after extracting and opening the project. It appeared that one of the animation assets had become corrupted, and after reimporting it, everything worked correctly again. Unfortunately, I don't know what causes this. Whether it's a problem of file compression, decompression, or initial compression of the animation sequence when running the project, it's hard to say.

TryHarder

Yep that's what I did in the end, re-importing the Rifle Crouch assets fixed it all good now thank you!!!

Sam Yazdi

Is there a recommended workflow for replacing the AGLS weapon meshes? Can I keep the AGLS skeleton and just replace the visible mesh?

Carl Brar-Pohl

hey, where can i find documentation about the project ?

Jakub W

When it comes to Skeletal Mesh or Static Mesh props, there are several ways you can approach the problem. For skeletal weapon meshes, I recommend importing your new model into an existing Skeleton asset. For example, AGLS includes a skeleton asset called 'AK-47_Skeleton'. A single Skeleton asset can be shared by multiple Skeletal Meshes. You can export the existing AK-47 mesh as an .FBX file and use it as a reference when adapting your own weapon model so that it remains compatible with the same skeleton. I also recommend storing your new mesh, materials, and textures outside of AGLS's default folder structure. This will make it much easier to replace files when updating to future versions of AGLS. Once your new mesh is prepared, you can simply assign it in the RifleAssetsDataTable. You may also find this tutorial helpful, as it demonstrates how to add a new weapon type: https://youtu.be/2Z2ZOevM1tA?si=hWUqrKfZIF87Fecv The tutorial is somewhat outdated, but the workflow for preparing and importing the weapon mesh is still relevant. I should also mention that I'm currently working on major changes to the weapon system in AGLS. Many assets may change as a result, but replacing the weapon mesh itself shouldn't become significantly more difficult.

Mega Verse

ah, i see that it works with keyboard inputs-- doesnt work well with the controller

Muh Nurdin

hi Jakub W. I joined as a member here to try out the project you’ve created. I’m very impressed with this project, but there are a few things I’d like to know more about. I’ve tried downloading the V1.9.2 version of the project, but I’m actually using the UE 5.6 engine. When I tried it, I encountered an error with the plugin. Does the latest version you’ve developed, V1.9.2, work properly with UE 5.6? Or is it specifically designed for UE 5.7/5.8? And actually, there’s a project with version 1.7.0 that’s compatible with UE 5.6, but I don’t think its features are as comprehensive as those in V1.9.2. That’s why I’d like to ask about this. Thanks .

Jakub W

Hi. Starting with AGLS v1.8, the project is available only for Unreal Engine 5.7 and later. Unreal Engine does not support backward compatibility, so there is essentially no way to open, for example, AGLS v1.9 in UE5.6. For Unreal Engine 5.6, the latest available version of AGLS is v1.7.

Muh Nurdin

Ahaaaa okkey thanks🥳.

ysk91

Hey Jakub is there any tutorial about how to change the charachter? For example the ALS_AnimMan_CharacterBP in the ZombiesDemonstration map? i tried to change it with my charachter from iclone can be exported to ue5 skeleton and it works also but the weapons and other stuff is not on the hand its always on the floor. After that i tried also just go to ALS_AnimMan_CharacterBP choosed BodyMesh under Skeletal Mesh Asset choosed my own charachter. turned off AnimMan visibility. And right clicked on my charachter in content browser and Assigned Skeleton to ALS_Mannequin_Skeleton and i got an alert that bones are missing. When i continue and accept a Message appears: FAILED TO MERGE BONES: This could happen if significant hierarchical changes have been made, e.g inserting a bone between nodes. Would you like to regenerate the skeleton from this mesh? ***WARNING: THIS WILL INVALIDATE ALL ANIMATION DATA IS LINKED TO THIS SKELETOM***

Tibor Bertók

Hello.Would it be possible to add RPG elements like sword combat, shield, etc… like the assassins creed games or witcher style. I’m trying to add some things to it, but it is very difficult without breaking the files. Can you make a tutorial on how to add new combat moves or weapons? Or just implement these things in the new update? 😀😊

Jakub W

Hi. Unfortunately, I don't have a great deal of experience with the problems like this, but I'll try to suggest a few possible solutions and point out some things worth considering. First of all, AGLS is still based on the UE4 skeleton hierarchy, which means it uses only 3 spine bones. If your character has exactly the same bone structure, you can try importing your new Skeletal Mesh into the existing Skeleton asset. However, this method requires the skeleton hierarchy and bone proportions to match exactly. Also pay close attention to the IK bones, as they are essential for the system to function correctly. In addition, the AGLS Mannequin skeleton includes extra bones such as 'attach' and 'backpack', which are also important. Another option is to import the mesh as a new Skeleton and then use Master Pose. This approach is relatively simple to set up, but it's also quite limited and somewhat outdated. The best solution would be to use Real-Time Retargeting with IK Rig and IK Retargeter assets. This is the approach I demonstrated in the ALS_Manny_CharacterBP class, where it significantly simplifies the process of integrating MetaHumans. Epic Games continues to invest heavily in developing this part of the engine.

Corey Fry

Thank you a lot, I did have a question tho. I cant seem to find where i would change the footstep sound, my landmass makes metal stepping noises so I was trying to figure out how to switch it back to dirt?

Jakub W

Hi. Unfortunately, I'm not able to prepare a tutorial at the moment showing how to add a completely new Overlay State. The entire implementation (including the animations and props) can be quite complex and requires a solid understanding of the engine. However, I can give you a few key pointers that you should keep in mind. First of all, adding a new enum value to ALS_OverlayState may not be the best approach. There are a huge number of references to this enum throughout the project, which would require manually reviewing each one. Instead, you could reuse one of the currently unused enum values, such as Masculine or Injured. Using Find in Blueprint, you can search for the enum name to locate all of its references: https://snipboard.io/HgvyRf.jpg You'll also need to create a new Animation Blueprint class for your new Overlay State. You can use assets such as 'ALS_OverlayState_Rifle' or 'ALS_OverlayState_Knife' as references. For everything to work correctly, you'll need the appropriate pose animations. These animations must also include the IK bones. By default, the position of held props is driven by the 'ik_gun' bone. The Equip and Unequip animations are a separate topic. If you're only supporting transitions between Default→Sword and Sword→Default, then you'll only need two animations. Supporting additional transitions, such as Sword→Bow, requires dedicated transition animations for each case. For the Default Overlay State, you can add the unequip animations in the UnEquipProp(State) class: https://snipboard.io/kiYegE.jpg You can register your new Animation Blueprint in OverlayStatesData: https://snipboard.io/ykmpnN.jpg As for prop management, it is handled by the StateTree named ST_OverlayAttachPropsLogic: https://snipboard.io/TpbgF9.jpg

Jakub W

Hi. The Footstep sounds are unique for certain Physical Materials. The sounds for specific surface types are selected within the corresponding MetaSound Source class. When BP_AnimNotify_FoleyEvent->SpawnFoleyEvent() is called, it performs a Line Trace, which returns the Surface Type Enum converted to int index and passes it to the instantiated MetaSound. The MetaSound Source (MSS) classes that use different sounds based on the assigned Physical Material have names with '_Dynamic' suffix. https://snipboard.io/Z4yrAM.jpg https://snipboard.io/WnRZAh.jpg

JafeerYoung

gotta use the knife, aim (right click) then left click

Tibor Bertók

Thanks, this makes sense for the equipped Sword Overlay. For the actual attacks, should the attack montages and melee trace be handled independently from the Overlay State? Also, can weapon transitions be routed through Default to avoid creating a dedicated animation for every weapon pair?

ItalianNightmares

Thank you, i will try that, seeing some video on youtube and your work is AMAZING! If my game will land on Steam it's only for you. Respect from Italy!

ItalianNightmares

Hi, First, I really want to thank you for your work on IWALS. It is an incredibly impressive project. I am facing a problem with the XBOX Controller. When i am climbing the button A doesn't work, in fact the character doesn't jump on the other ledge. The climbing only works with keyboard. Can you help me? Or someone has faced the same problem?

Jakub W

Hi. You're right - when climbing, the Gamepad input doesn't allow the jump action to be performed. Fortunately, the fix is fairly simple. The issue is that the Execute 'Started' pin is not triggered when the button is released, and that behavior is essential in this case. The solution is to handle the deactivation from the 'Triggered' event instead. https://snipboard.io/ukmDcQ.jpg

geim an

hey im running into a lil problme trying to export the zip file, towards the end some files refuse to download giving me an too long error and i dont really know how to fix it

Jakub W

Hi. If you're still experiencing this issue, pay close attention to the location where you're extracting the files. The path to the project directory should be as short as possible. Also, keep in mind that different decompression programs may have different maximum path length limits. I mentioned this issue in this post below the project download link.

Tim Schröder

Hello Jukub, we are awaiting version 2.0 of agls.

Galen (edited)

Comment edits

2026-09-18 17:00 Enter the path of any Metasounds folders in Project Settings > Metasounds > Directories to Register. Basically, UE 5.8 tightens the way some things are handled: "Unreal Engine 5.8 relies heavily on explicit configuration for automated registration and data-driven configuration workflows. If specific directories are missing, the registry skips them or fails to fully pull them into global class pickers."
2026-09-04 23:14 Enter the path of any Metasounds folders that you're using in Project Settings > Metasounds > Directories to Register. Basically, UE 5.8 tightens the way some things are handled: "Unreal Engine 5.8 relies heavily on explicit configuration for automated registration and data-driven configuration workflows. If specific directories are missing, the registry skips them or fails to fully pull them into global class pickers."

Enter the path of any Metasounds folders that you're using in Project Settings > Metasounds > Directories to Register. Basically, UE 5.8 tightens the way some things are handled: "Unreal Engine 5.8 relies heavily on explicit configuration for automated registration and data-driven configuration workflows. If specific directories are missing, the registry skips them or fails to fully pull them into global class pickers."

zeroDay

Hello Jakub I am working with AGLS1.9.2 in UE5.8. But I’m running into this issue where my character bullets can’t hit the Enemy AI and the AI cant fire back, but enters the alert state. Any advice will be greatly appreciated. Though all mechanics work well in your example levels. Thank you

SKD007

Error 0x80010135: Path too long DebugHash_45953976b6ad066260371b0458df375a8cb8eb9a 71a7803b1fe47a60f77d68fd Type: File Date modified: 1/18/2026 2:19 PM Size: 0 bytes

Darksorck

I made it run on linux but unreal on linux is a pain in the ass.

Jakub W

Hi. Does the issue you described occur in the default AGLS project scenes, or does it affect your own scene? If it only happens in the latter case, it is most likely due to an incorrect collision channel configuration for the actors in the scene. Shooting issues are often caused by the player or an AI being located inside a volume-type object, such as a trigger box. By default, these can block the shot's trace. To start, I recommend reviewing the notes in the 'AGLS - Basic Project Informations' file. You can find the download link in the post footer. That document contains information about the shooting issue and how to attempt to fix it.

zeroDay

Thank you Jakub,I took a look at the document you mentioned. I happened to have 2 volumes around the map, changed their collision to destruction and it worked.

Guru Prasad

Hey Jakub, Hope you are doing great. Getting this error after lauching engine . Any help would be appreciated. The following modules are missing or built with a different engine version: ClimbingNavigation HelpfulFunctions JakubAnimNodesTool JakubAnimNodes CombatCore CombatCoreEditor GraphDebbuger IWALS_AbilitySystem JakubCableComponent Would you like to rebuild them now? After rebuild getting this : AGLS could not be compiled. Try rebuilding from source manually.

Thisisme Mario1

Hello there ! I saw a few months ago that you mentioned that in UE5.8 the AI is broken, (statetree problems) is it still the case ? Asking because I was planning updating to the latest version but I'd wait if it's still broken. Thank you for your answer.

Shaune Greenidge

Appreciate you sharing this knowledge Chris. Very helpful