RichAI clamping inside mesh and prematurely

General
7

Ooookay. I’m back with more useful information. I decided to upgrade to v4.3.35. And whadda ya know, it’s fixed! And I figured out why too, which leads into another question :sweat_smile:

Previously, I had extended the NodeLink2 code to add support for tags, so that only certain seekers could use certain links. So without reverting to 4.2 and using the modified NodeLink2 code, I can’t confirm exactly, but It’s likely that was the issue. This was the previous post about tag support for links.

Anyways! So this clamping issue seems to be resolved, however, I’m returning to my issue of tagging PointNodes. This might be suited for another forum post…

How exactly does tagging point nodes work? I’m using a Recast Graph and Point graph combo. Point graph being required by NodeLink2, and Recast Graph for usual traversal.

       // This runs OnPostScan()
       foreach (NodeLink2 nodeLink in nodeLinks)
       {
           nodeLink.OnPostScan();
           
           // Tag link
           if (nodeLink.startNode != null) nodeLink.startNode.Tag = (uint)Tag;
           if (nodeLink.endNode != null) nodeLink.endNode.Tag = (uint)Tag;
       }

I’m using that code, but no matter what I throw at it… I can’t seem to get my characters to ignore PointNodes. GraphUpdateScene.cs works well for sectioning off portions of my RecastGraph, however, it won’t touch the PointGraph (or if it is, my seekers don’t care).

In my Seeker component, I’ve disabled traversal on every tag except Ground. Then, I’m trying to assign all my PointNode tags to a randomly high layer like 20 for example. No dice, they don’t care and use all PointNodes in the graph.

Sorry to shift topics :sweat_smile: I can move to another post