discwalker Posted February 25, 2019 Share Posted February 25, 2019 Tracks show the 2nd AWACS landed to Anapa in the MFD rather than the 3rd active orbiting under Novorossiysk. At ends i taxi near the 2nd. (In command second should land to Novorossiysk.) I was on the server (104th) as a client in the active time of the 2nd AWACS, I escorted that until that landed. (When 2nd slowed down enough the 3rd activated by a trigger.) In the early seconds of the 3rd activation the icon of the 2nd on the MFD is constantly rotated while that on the ground stopped. Then I escorted for a long time the 3rd. In this unwanted awacs mode finding the current awacs is harder. Without any indication in the datalink to it. 8_Op_Fire_Shield_V4.1-20190224-213202AWACS3shows2nd-j11a.trk 18MB https://drive.google.com/open?id=1U-DJbKB_jsLBU1YAz8SJWoT8qRe-3iPm 8_Op_Fire_Shield_V4.1-20190224-210244AWACS3shows2nd-su27.trk 18MB https://drive.google.com/open?id=1KlJ3iJzQNfrWBRFl_64XnYTwDOgCamca Tracks are replayable now with 2.5.4.27430 Another noticeable thing is the DOUBLE messages from awacs3. Bad to ear. My client players and I couldn't reproduce this with 3 sequentially air spawned AWACSs. GTX 1070 8GB, 16GB DDR3, W8.1 on SSD, DCS on another SSD Link to comment Share on other sites More sharing options...
Recommended Posts