stride3d / stride3d/stride

Navigation-related stuff references Nav. groups when Nav. settings are missing

Open
#1,378 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
C#
Stars
7.8k
Forks
1.2k
Avg merge
2d 17h
Merged PRs (30d)
49

Description

Release Type: Official Release

Version: 4.1.0.1459

Platform(s): Windows (in-editor)

Describe the bug
When a user adds Navigation component and/or NavigationMesh asset he is able to select the default New group navigation group that is present in the default project navigation settings, and because there are no navigation settings added to GameSettings by default it results in an error:
Ability to select navgroup
When you press on a navgroup when nav settings are not added nothing is changed and those errors appear:
Errors

To Reproduce
Steps to reproduce the behavior:

  1. Create a default project
  2. Add a navigation mesh and/or nav. component
  3. Add a new item in navigation groups
  4. Select a New group from the dropdown of the item

Expected behavior
Select one:

  • Upon adding a navigation mesh or navigation component the correspoding settings should be added automatically
  • Upon an attempt of adding a navigation mesh or navigation component a warning or an error that no navigation settings was found should pop up
  • Dropdown of availalble items should not list items of the section that wasn't added

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the issue in a default Windows in-editor project using a Navigation component or NavigationMesh asset, then inspect how navigation groups are populated when GameSettings has no navigation settings. Done means selecting or adding navigation items no longer produces errors, either through automatic settings, a warning, or by hiding unavailable groups.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
game-dev
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.