Interceptor stops flllowing UFO, just hovering.

[Zar Nivop]

On Win 10:
Interceptor goes to predicted interception location. When it gets there, spot on the UFO, it just stays there... Have to re-issue interception command. 

[Zar Nivop]

I suspect this has to do with a specific bug in the "fly to projected location" algorithm. It seems the algorithm doesn't take into account the time between the issuing intercept command and the actual interceptor takeoff. that explains two things - why the 1st (and only the 1st) location the interceptor flies to lags behind the UFO, and that when issuing additional interception command all is OK. If I'm right an easy fix will be automated 2nd intercept command taking place after the takeoff..

[R1dO]

What version of openxcom are you using?

I just tied to reproduce this from an old build (somewhere at the end of 2018) and the most recent build.
In both cases the interception goes fine, no need to reissue the command (tested using the option "Predict UFO trajectory" and without that option).

Also what do you mean with: just stays there
* Does it follow the ufo when it moves around?
* Does it stay on the spot of the predicted location?

And for how long does it stay there (seconds, minutes, hours)?

Those answers might help us help you

[Zar Nivop]

Version: nightly (the one that fixing the RTL text problem) 28/6/19

The interseptor stays at the 1st waypoint it aimed to get (predicted location). I didn't check for how long.

The interceptor status is still "intersepting UFO x"

I attach 3 savefiles

[Zar Nivop]

Tested for how long it hovers. When the UFO changes its course the interceptor stops hovering and move to the current and correct intercetion point.

I found in the bug tracke similar issue, several years old

[R1dO]

I just loaded your saves. With neither of them i could reproduce the behavior you described.

Perhaps your installation is borked in some way (darn gremlin critters).

Try removing openxcom fully, do not forget to backup your saves and (optionally) the config file, and reinstall it from a fresh download. See if that helps.

[Zar Nivop]

I'll try remove - reinstall. Be back with results.

[Zar Nivop]

The problem persist.

Did remove + deleted everything except save files (config file deleted too)

Installed the latest

And.... see for yourself:  https://www.dropbox.com/s/2zqci98hz7js283/bandicam%202019-07-06%2016-54-30-536.mp4?dl=0

[R1dO]

Good that you showed the video. It clearly shows the steps how to reproduce the error you are experiencing.

Unfortunately though, i still cannot recreate it on this machine. Might be a windows related error, something i cannot help you with. Sorry

[Zar Nivop]

I moved to OXCE, which don't have this feature anyways...

If you wish (I'm not sure it worth the trouble on your side) I can make the faulty OXC available - I already 7Zipped it.

I don't think it's windows-related, I saw a bug report (in bug tracker) with the very same problem on Linux.

[R1dO]

There is no need to make the faulty .exe available (won't run under linux anyways).

But you are always free to attach a zip for anyone that is interested into taking a look.

[Docent]

I have exactly the same problem. it is very annoying

[Docent]

The problem is that the interceptor is planning a trajectory at the time of take-off from the base. But for a few more seconds he just hovers above the base, and during this time the UFO manages to overcome a certain distance. If the interceptor had planned the trajectory a second after gaining speed, this problem would not exist.

[Meridian]

I've said it many times, but I will repeat myself.

That feature is just one big bug, completely beyond redemption. Do yourself a favor and don't use it.