The absolute state of the Tactical demo

[Cheo]

Hello, I just tried to give the Tactical add-on for BD Pro a first tonight and... I think this video speaks for itself.

This is absolutely unacceptable, especially considering that this is a new version we have to pay for as well and that the original had a working demo. Maybe the tasks in themselves don't have any bug and the issues are just at the demo level, but I'm sure as hell not going to start toying with this without evidence that it works first. Please fix this ASAP.

 

[Justin]

This is absolutely unacceptable, especially considering that this is a new version we have to pay for as well and that the original had a working demo. Maybe the tasks in themselves don't have any bug and the issues are just at the demo level, but I'm sure as hell not going to start toying with this without evidence that it works first. Please fix this ASAP.

Please tone it down a bit. There are many things that can be different with your configuration and this is one of them. I see that you're using Unity 6.2 and was able to reproduce the same results with version 2.0.9 of the AI Navigation package. With the version of AI Navigation used by Unity 2022.3 (1.1.6) it works correctly:

Watch Tactical | Streamable

Watch "Tactical" on Streamable.

streamable.com

I looked into it and this is a bug in the AI Navigation package. No position is being set on those agents but they are still moving. I will report the bug to Unity.

 

[Justin]

I was playing with it some more and it's a difference between how the AI Navigation package handles obstacles. I found a workaround that works with both AI Navigation 1.1.6 and 2.0.9. I'll submit the new demo scene with the update of the Tactical Pack that will be released with Behavior Designer Pro. This was demo scene specific with no code changes.

Thanks for letting me know.

 

[Cheo]

I took another quick look myself and that's right, I acknowledge that it works in 2022.3 and that it may be hard to keep track of all of Unity's package updates. Nonetheless, I do want to point out that the issue was also there in 6.0 which is an LTS as well, and one would expect a recent asset they just bought to work on a supported version like 6.2, not to mention that this is far from the first time this is happening - so I know I was harsh, but please understand my frustration. In any case thanks for looking into this.