To clarify, no part of a pawn’s locomotion is handled by this plugin. After solving a path, it simply hands all movement logic over to your pawn via AddMovementInput so your pawn’s movement component is the right place to investigate issues like this. In any case, glad to hear it was solved.
By “destroy path” I’m guessing you mean the black lines that depict a solved path? If so, you just need to disable the relevant debug option from the Fly To node’s Query Params (all the visualize solution flags need to be turned off).
For your second question you’ll have to check the logs and see what error message is being shown. If your drone can’t fly after being spawned it is indicative of some other fundamental issue; it has nothing to do with the previous bot’s path (which are just debug lines)
Thank you 