{"id":350,"date":"2024-09-01T17:21:49","date_gmt":"2024-09-01T17:21:49","guid":{"rendered":"https:\/\/willkolb.com\/?p=350"},"modified":"2024-09-01T17:22:34","modified_gmt":"2024-09-01T17:22:34","slug":"less-project-more-game","status":"publish","type":"post","link":"https:\/\/willkolb.com\/?p=350","title":{"rendered":"Less Project More Game"},"content":{"rendered":"\n

Today I decided I needed to start making this an actual “game” rather than just focusing on the asset side of things. To start I made a simple arena:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Essentially a bunch of walk-able pathways and two towers in the center. The goal was to essentially stress out the AI by putting a bunch of stuff in the way. This succeeded and I had to re-write a bunch of the AI tasks (luckily not the base ai tree too much). <\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

Now the ai flow is:<\/p>\n\n\n\n

1.) Check if it needs to reload
2.) Start fighting
3.) If it has ammo, try to move to a “strafeTarget” (i.e. a tactically relevant position) , if it doesn’t have one or can’t move to said target just generally move towards the target.
4.) Wait a few seconds to let some bulletsfly(firing timing happens in the patrol bot logic, not the ai logic)
5.) If you have ammo find a new tactically relevant position to stand in

In addition I have the AI and the patrol bots doing line traces from either the intended target position to the character to see if it can hit the shots it’s aiming for, or if it needs to move. <\/p>\n\n\n\n

The big struggle today was setting up the AI settings for unreal, which in general are a real pain. I’m worried I made it basically unplayable on cheaper PC’s but I’ll need to get a build together for testers before I start optimizing. The way unreal’s AI works (and I think uniity is pretty similar) is by setting up a grid of points, then using an “navigation agent” to handle how pathfinding works. This navigation agent is a primitive object (I assume a cube but I’m not 100% sure) that is placed along projected paths to check if it’s possible to move to the target location. If unreal\/unity Didn’t have this concept you’d hit a bunch of issues with the AI trying to navigate it’s body through a bunch of pinhole sized paths. So to handle cornering a bit better I started messing with the AI agent size: (Nav agent height near the bottom)<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

However, I quickly found out that A.) You need to change it int he “navigation Mesh” settings:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

also, AND that if you don’t have dynamic re-generation on Unreal just starts saying that the nav mesh needs to be rebuild (and I wasn’t sure how to do that…). So I had to check the “FORCE REBUILD” guy and set the “runtime generation” to dynamic.<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

This biggest hit here will be performance but again I’d rather rush a build, have it run like crap then optimize as needed.<\/p>\n\n\n\n