Bug reports should follow the guidelines outlined in the Bugs thread, specifically, reports should provide all of necessary information to enable me to debug the issue. Please follow the guidelines as stated in the bugs thread and update your post accordingly.

With that being said, from the description you have provided it sounds like this is related to the long-standing "Bug - Flyers are sometimes "laggy" or "jittery" when flying after Homing Pigeon use" bug that is also detailed on that bugs thread.

Being able to correctly handle interrupt behaviour is something that is on my todo list, see this item[trello.com] on the public development sprint board[trello.com] for more information. You can use this to track when this will be supported.

In the mean time, I would advise not interrupting Homing Pigeon whilst it is running, allowing it to complete (ie: the flyer reach its destination flag) before interacting with the flyer in question.

To answer the other half of your question, Homing Pigeon has not really been designed to be used in this manner (as a mechanism for transporting other dinos on the back of the quetz), no testing has been done for this scenario, and so results may be unexpected. This may be something I look at supporting in the future, but it is considered a low priority at the moment given the other issues I am trying to fix at the moment following the v259.0+ breaking patch issues.

When i was fly, i was not using the Homimg pigeon unless you are saying it is still in effect after it gets home and you take the animal out 5 mins later for another run it can still be affected? Understood , good luck, and happy bug squashing!! :-)

Originally posted by Minion:

When i was fly, i was not using the Homimg pigeon unless you are saying it is still in effect after it gets home and you take the animal out 5 mins later for another run it can still be affected? Understood , good luck, and happy bug squashing!! :-)

What I mean is, if you activate Homing Pigeon (either through auto-return, manual recall or manual send to), currently you must let it complete that task before attempting to mount or whistle it. By complete I mean, the flyer lands and you see the second notification message informing you that the flyer has arrived.

If you interrupt the flyer before this happens, then the behavior tree may still be running and leads to the weird janky behavior you have described.

I have an outstanding development task to complete in order to handle interruptions correctly, so until then this is the best usage advise I can give to you.