Does FastGeo break navigation meshes?

Hi, I’m hoping for a sanity check. Does the FastGeo Streaming plugin work with navigation meshes? We’re seeing it appear to produce an invalid nav build. Is it just us experiencing this?

Hoping for any insight you may have.

[Attachment Removed]

Steps to Reproduce

  1. Start with a map that uses nav mesh.
  2. Add FastGeo to the map’s World Settings transformer stack.
  3. Build navigation using the Build menu option “Build Paths”.
  4. PIE on that map. Excessive runtime nav-mesh building occurs.
  5. Remove FastGeo from the transformer stack.
  6. Build nav.
  7. PIE. Runtime nav build is minimal.
    [Attachment Removed]

Hi there,

Thank you for the repro steps. I’ve been able to test this a bit and I haven’t actually seen any significant difference in build times. Nor have I had any issues with an invalid nav build.

Could you provide a bit more info that could help me reproduce this issue? e.g PC specs, a minimal repro project and/or additional/more granular repro steps.

Hopefully with a bit more info we can figure out if this is only happening on your end.

Cheers,

- Louis

[Attachment Removed]

Hi Louis, thanks for responding. So, I was at the beginning of an investigation into our nav issue (a topic not in my wheelhouse), and I was hoping for just a quick sanity check - which you’ve given me: clearly FastGeo is expected to work with nav, and there isn’t some major known issue.

Given that, I didn’t want to respond until I’d put some more effort into it. After educating myself a bit more, I now believe our problem stems from an engine modification we made to nav relevancy some years ago. FastGeo mirrors the nav relevancy logic of actor components in its own FastGeo components. Our modification is, of course, absent there. I believe this leads to a discrepancy in navmesh built from actor components which is then used in-game with FastGeo components.

Our thinking now is that we no longer need that engine change, and that we should excise it entirely to return to UE standard nav relevancy, then retry FastGeo.

-- Steve

[Attachment Removed]

That’s great to hear & I’m glad I could assist you with the sanity check!

I will mark this case as resolved.

[Attachment Removed]