x

Search in
Sort by:

Question Status:

Search help

  • Simple searches use one or more words. Separate the words with spaces (cat dog) to search cat,dog or both. Separate the words with plus signs (cat +dog) to search for items that may contain cat but must contain dog.
  • You can further refine your search on the search results page, where you can search by keywords, author, topic. These can be combined with each other. Examples
    • cat dog --matches anything with cat,dog or both
    • cat +dog --searches for cat +dog where dog is a mandatory term
    • cat -dog -- searches for cat excluding any result containing dog
    • [cats] —will restrict your search to results with topic named "cats"
    • [cats] [dogs] —will restrict your search to results with both topics, "cats", and "dogs"

Nav modifier component broken in blueprints

The nav modifier component in blueprint is broken, in 4.7.6 they worked like the normal nav modifier volumes. At the moment the nav modifier component will only work if "Can Ever Affect Navigation" is checked to true and if the "Pawn" or "Vehicle" collision response is set to block in the root component of the blueprint. If you try changing these settings in a child the editor will either crash or you won't be able to compile the blueprint anymore, changing the settings back doesn't matter, you will still get the error.

If you don't have those set you will get this error in the output log, LogNavOctree:Warning: Can't add node [NavModifier] - parent [Box] not found in octree!

Product Version: UE 4.8
Tags:
more ▼

asked Jun 21 '15 at 04:52 PM in Bug Reports

avatar image

Tekoppar
31 4 5 7

avatar image Adam Davis STAFF Jun 21 '15 at 07:31 PM

Hi Tekoppar,

Have you tried this in a clean project with no additional content or is this limited to one project? What specific steps are you taking that reproduce this on your end?

avatar image Tekoppar Jun 21 '15 at 08:13 PM

Happens on new projects too.

New blueprint class > actor > add box collision > add nav modifier = Nav mesh won't change until you change the collision settings of the components.

For the crash it seems to be caused by changing the collison settings, toggling the "Can Ever Affect Navigation" on/off and moving a component. I also get the semi permanent holes in the navigation bug when I do this, where if I set the collision so the navigation mesh rebuilds and toggle the "Can Ever Affect Navigation" to off and move the blueprint. The hole that was built by the moved mesh will be kept there until I restart the project.

link text

crashreport.txt (2.6 kB)
avatar image Adam Davis STAFF Jun 21 '15 at 09:25 PM

Hi Tekoppar,

I haven't been able to reproduce the crash, however I was able to reproduce the navmodifier error in which the navmesh will not change. I've entered a bug report, UE-17437 to be assessed by the development staff. Do you have any steps I can take to reproduce the crash? Additionally can you upload the crash logs? The link you provided is the callstack. To get the logs, go to \Unreal Projects\PROJECTNAME\saved\logs. Thank you!

avatar image Tekoppar Jun 21 '15 at 10:10 PM

I've found a consistent setup with a project. Heres a video I recorded of the setup; https://dl.dropboxusercontent.com/u/9876544/Desktop%202015.06.22%20-%2000.04.36.02.mp4 and the project I used; https://dl.dropboxusercontent.com/u/9876544/MyProject.rar

(comments are locked)
10|2000 characters needed characters left
Viewable by all users

1 answer: sort voted first

Hi Tekoppar,

I was able to reproduce this and have entered a bug report, UE-17468, to be assessed by the development staff.

more ▼

answered Jun 22 '15 at 07:39 PM

(comments are locked)
10|2000 characters needed characters left
Viewable by all users
Your answer
toggle preview:

Up to 5 attachments (including images) can be used with a maximum of 5.2 MB each and 5.2 MB total.

Follow this question

Once you sign in you will be able to subscribe for any updates here

Answers to this question