Search Unity

  1. Welcome to the Unity Forums! Please take the time to read our Code of Conduct to familiarize yourself with the forum rules and how to post constructively.
  2. The 2022.2 beta is now available for testing. To find out what's new, have a look at our 2022.2 feature highlights.
    Dismiss Notice
  3. We are updating our Terms of Service for all Unity subscription plans, effective October 13, 2022, to create a more streamlined, user-friendly set of terms. Please review them here:
    Dismiss Notice
  4. Have a look at our Games Focus blog post series which will show what Unity is doing for all game developers – now, next year, and in the future.
    Dismiss Notice
Dismiss Notice
Submit bug reports tagged with #Beta2022Win_Unity when you encounter unknown issues while testing the 2022.2 betas for a chance to win a year of Unity Pro. For more information, have a look at our Beta Sweepstakes Announcement.

NavMeshLink bug: OffMeshLinkData.offMeshLink returns null

Discussion in 'AI & Navigation Previews' started by Candescence, Jul 11, 2018.

  1. Candescence


    Aug 26, 2014
    While there has already been an issue filed on this in the repository, it's also an issue that's gone unnoticed and unaddressed by the Unity devs for months and directly impacts the usability of NavMeshLinks.

    If you want to get, say, the area of an NavMeshLink, you're basically up a creek without a paddle. As far as I can tell from looking at the code, it seems Unity's navigation system currently doesn't take in NavMeshLink data as manually-created off mesh link data.

    So, if you're planning on using NavMeshLink data in your code, don't use them until this bug is fixed, use the old OffMeshLink script instead. It's more of a pain, however.

    I love the new Nav Mesh Components, and it pains me to have to highlight this problem, but it's a big oversight that really needs to be addressed.
    Last edited: Jul 11, 2018