reported George TADS stuck if you order to scan a point after forward area search.

[Czar]

Sorry if my english is not up to par to report this because I'm not familiar with the terminologies with the different tracking and pointing methods.

If you order George to search the area, in this case "forward area", then slave him to a point before ordering him to scan for targets on that point. The TADS/George will get stuck in a looped glitch. It wasn't like this prior to the latest patch, I think, but definitely there is a bug.

Shown here in a unlisted video (youtube). Need the link to access or watch it embedded here:

The track file came from the flight on the video.

Track and mission file attached bellow. Simple Caucasus mission in air start made in mission editor.
The issue can be shown on the track or verified in less than 2 minutes.

Steps to reproduce:

1. Forward area search.
2. Point, using the button you order George to fire a weapon - > Slaving George to the current point of interest, in this case Waypoint 1 where there are a few armored vehicles).
3. Search, using the same button above, after TADS is slaved to the POI (waypoint 1 in this case).
4. Glitch occurs like George is changing TADS FOV indefinitely while scanning the forward area at the same time.

This does not occur if you order George to slave the TADS to a point from a fixed TADS or with TADS somewhere else but searching the forward area.

Scan at point after forward area search bug.miz Point Bug.trk

Edited yesterday at 12:50 AM by Czar

[BIGNEWY]

thank you, we have reproduced and reported to the team.