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"

MoveToLocation call fails to project the location to the navmesh

Hi!

I have a MoveToLocation call that sometimes fails to project the location to the navmesh even though there are navmesh over the whole level.

If there are "too big" height differences between the location and the navmesh the call seems to fail to project the location to the navmesh.

The problem is that I only know where I want the pawns to go in the XY plane. The Z axis is there for cosmetic purposes only.

What's the recommended way of solving this? I understand that one can raycasts against the landscape but is it really necessary to involve the collision system to get proper movement locations? Or can you somehow change the max distance MoveToLocation uses to project the location to the navmesh or is this just a bug?

Product Version: Not Selected
Tags:
more ▼

asked Nov 21 '14 at 04:34 PM in Bug Reports

avatar image

undercover
838 123 111 138

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

1 answer: sort voted first

The easiest and quickest way would be to modify NavigationSystem::SupportedAgents to extend DefaultQueryExtent, specifically its Z component. This extent is used in navigation queries, like finding start and end locations during pathfinding.

You can find these settings in Project Setting's.

We have a fix coming in soon that will solve this problem for all character-based navigation, but that's not in yet.

Cheers,

--mieszko

more ▼

answered Nov 21 '14 at 04:45 PM

avatar image

MieszkoZ STAFF
7.3k 223 57 412

avatar image undercover Nov 21 '14 at 04:59 PM

Okay, thanks a lot!

avatar image undercover Nov 24 '14 at 02:43 PM

Do I need to somehow link these settings to the actual actors/agents or is it just an array of settings that must be supported in the navigation system? If not how would I do that?

avatar image MieszkoZ STAFF Nov 24 '14 at 04:11 PM

SupportedAgents is meant to hold "types" of your agents, and any agent querying navigation at runtime is automatically assigned one of those types. Mind that currently for every supported agent a separate navmesh instance is being created.

avatar image undercover Nov 25 '14 at 12:30 PM

Okay, I see. Thanks again!

(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