I can not figure out what I’m doing wrong, both the Character and Pawn I made, using the same controller and behavior tree, will not move an inch. I’m using a small “random points in a box”, 50 on all sides with an origin of the AI. I tried it with a random point in a navigable radius and even just telling it to go to a set vector location. It will not move. There is a Don’s nav mesh around it, I’ve tried both, neither of them will get either the character or the pawn to move. Does this work in 4.23?
Hey @ Have you watched the YouTube video the author supplied? Do you have a movement component on the pawn? Is the point located in an object that is an object defined as an ‘obstacle’ in the DonManager properties? Is the DonMesh around the entire area from start to finish? Did you enlarge the DonManager area byusing the object’s transform (increasing scale) or did you use the X Y and Z properties in the DonManager to enlarge the area? Did you change the voxel size?
Enable debug path drawing on the move node in behavior tree and check console log for warnings from plugin
One other thing: if you’re using the behavior tree FlyTo node, are you using the custom event provided to link to AddMovement?
Hello!
It’s seems like the author abandoned that thread, but I still gona post a question, because the documenation is quite minimalistic and it’s a last thing I have to do before digging deep in a source code.
My main problem is that the navigation mesh is NOT updating when you scale the obstacle down. I’ve looked through comments and found a parameter named CustomCacheIdentifier of function ScheduleDynamicCollisionUpdate, which can probably resolve the issue, but the description of it is quite obscure and I still havened managed to use it correctly. I tried to set different values of that parameter for differetn scales, but it hadn’t helped. Setting bReloadCollisionCache to true seems also to have no effect.
Thanks in advance!
Hello,
I have used this plugin successfully in 4.22. When you say “The navigation mesh”, what do you mean? When you say “obstacle”, are you referring to an object that is defined in the array of obstacles attribute on the DonNavigationManger?
There is no navigation mesh as far as I know. The DonNavigationManager is just a volume of sorts and is adjusted using its properties, not the transform’s scale. There is an X, Y, Z size, as well as a voxel size that fills the given XYZ size of the volume.
Can you post more information, screenshots with arrows pointing to things? I’d like to help since I have a fair amount of experience with this plugin.
-Erol
Thank you for the response! I recorded a 2-minute video to represent an issue:
Hi @Dain_Torson , what do you see if you turn on Show Collision when moving the BP_Fan with BP_Fan start in up position and then start in down position? Does the collider move with the fan? It is difficult to see what is really happening with limited information, and the behavior acts as if the collider to the BP_Fan is not moving when the fan starts in the down position. In other words, when the BP_Fan starts in down position, the behavior of the Pathfinding algorithm seems to see the collider is still in down position even though the mesh is In up position.
Few questions:
- How many colliders are on BP_Fan? Since I do not know if this is some Blueprint made from code, I can only guess that only the cube has a collider.
- For all collision entries on the blueprint, what are the profiles of each collision entry?
- What collision types are listed in the DonManager obstacle type array?
- What collision types are listed in the DonManager safe to ignore array?
- Since I cannot see the DonManager volume in the level, I’m assuming it encompasses the same area no matter if start the game with AutoEnabled = true or AutoEnabled = false on the BP_Fan. Is this correct?
Few things I noticed:
- @1:26 in the video, there are outputs to the log that seem to be exactly what you have commented out in code. Is that log entry coming from somewhere else you have not shown in the video?
- I thought I remember in the video the author put on YouTube for instructional purposes, that if there is a collison found during ScheduleDynamicCollisionUpdate, that one has to re-run SchedulePathFindingAlgorithm. I see that you’re calling the ScheduleDynamicCollisionUpdate but I can’t see if you’re handling the delegate return that fires if there is a collision found in the current path solution. If that delegate fires, I believe you have to rerun a pathquery once more to get a new path. While we can agree that the dynamic collision update and new path finding query works when the gate starts up, we need more information to truly find out what is happening in the background.
Here is the youtube video for the introduction and some information about the plugin. https://www.youtube.com/watch?v=6Tr_K551zvI&t=781s Specifically, he talks about these delegates @ around 30 or so minutes. While the video mainly talks about and shows Blueprint nodes, it makes no difference as the C++ code should be handled the same way.
See what you can find out and please post back if you still have issues, or if you fixed it. I’d really like to continue helping if I can.
All the best!
-Erol
Thank you for your feedback, @erol_demirci ! There is another video I’ve recorded:
There pathfinding query is rerun in the next tick after the previous pathfinding query ended.
Hi, when can we expect an update for UE 4.24+ ?
Need update to 4.24 ASAP!
Hi @Golden4o and @vlad3r08 what is the issue you’re seeing in UE4.24 with this plugin?
@Dain_Torson I have not had a chance to look at your new video. Any new findings since you last posted sir?
@erol_demirciyou just need to update the plugin so when we start the project it won’t tell us that it is for 4.23 and if we want to load it anyway.
Hey @Golden4o I am not sure if your response was to me because of some confusion.
Unfortunately I am not related to development or official support of this plugin. I just try to help people with this plugin since the developer abandoned it long ago and I have some elementary experience with it. I am not affiliated or can help in any way as to how this plugin interfaces with Unreal Engine. That is something we must do as a community, or, the developer must do on their own.
Or, perhaps I am incorrect and you meant something different?
-Erol
In the Epic Marketstore it’s saying I can’t install it as it’s max supported version is 2.23.
Now I want to ask if there is any access to the source files so we might patch it?
The plugin is sounds that it might be good for some occasions and see this as a real shame if the author hasn’t released the source code if he decided to just abandon it.
I have some experience in c++ and am a dev by day in c# .Net for 6 years.
Currently I’m working on a somewhat complex project in Unreal in C++ so I’ve built some exp in it and would give it a go for sure to upgrade it if given the chance.
Hi @vlad3r08 ,
I understand you can’t install it in 4.24, I have not yet tried to do that as I am currently on 4.22. You can install 4.23 and install the plugin and get the source in the following folder: On a standard windows install: ProgramFiles\EpicGames\UE version\Engine\Plugins\Marketplace\DonAINavigation.
-Erol
@VSZ I have packaged the plugin for use in 4.24. I did NOT thoroughly test it, but it does work in my project. Please let me know how to proceed (do you want me to upload it somewhere?)
-Erol
Can you please upload it and share it with us?
I have created a 4.24.1 version of the plugin that works with the Example project in the past I offered to share it but I’ve long since misplaced it and no longer using that version of the engine. As pre the following recommendation its best to learn how to compile it yourself so you can keep yourself up to date.
I do not think it is a good idea to post a marketplace item, despite the license, in modified form, here on the forums, without attempting to consult the author, or at least consulting with Epic Games. The properties in the descriptor file I see you kept in tact, which in fact, is support information, as well as a link to the market place item (which is NOT supported under 4.24).
Why not post the process to which individuals can build on their own which removes rules to be broken here, and you inspire/educate/empower others to learn. WinWin.
This package may not work with different locales/setups as you built this using your own locale.