Jump to content

Martin2487

Members
  • Content Count

    117
  • Joined

  • Last visited

About Martin2487

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. The IGLA missile does not explode when it hits an AI aircraft. It flies through the center of the aircraft and continues to fly further up. In the game, the debriefing item shows the hit of an aircraft missile. But there is not the slightest damage on the plane. With an airplane piloted by a player, such a problem does not occur. It has been tested many times and always with the same result. I tested whether this problem occurs with Stinger and there is no such problem. The attached track contains a test with an AI F/A-18 aircraft and a MANPADS IGLA. As can be seen from the record, the mi
  2. This is a disappointment for me and at the same time I find it strange. It is strange for an aircraft to be forced to have a TGP and not be able to obtain the contact sent in this way other than through the TGP.
  3. Although I haven't had a chance to test it yet. But all the time I was afraid that this feature would do something similar to the SPI in SADL on the A-10 which I never really liked. Here I see several problems in integration and usability that were also seen in the video. I was surprised to be able to see TXDSG on AG target from all people on NET Link-16 and not just those I have on the flight. I don't want to see what the SA page will look like on some big mission where it will be performed by more aircraft. So the feature that it's being sent to everyo
  4. Yes, the test was in the air. F/A-18 at an altitude of about 25,000 ft above Senaki.
  5. I performed the test, an airplane in the air above Senaki Airport at an altitude of about 25,000 feet. The same problem. Sentry is not able to transmit the position of the air contact above 140 NM. But here's the problem with not seeing or being out of range on AWACS. If you see his position on the SA page, he sends you his position and altitude + identification. This is called PPLI (Precise Participant Location and Identification). It's one of the datalink messages. So the connection between the aircraft and the AWACS E-3A Sentry is established. It's just not able to send air contacts ab
  6. No. It was a typo error. I corrected it in the text. Thanks for your post. But I use some mods in dcs. I deactivated them and performed a DCS repair. The result is the same. The maximum distance to which the E-3A Sentry is able to send an air track is around 140 nm. E-2D Hawkeye works correctly.
  7. Some time ago I created a thread (https://forums.eagle.ru/topic/230410-investigatinglink-16-sends-contacts-to-a-shorter-distance-than-it-should-be/?tab=comments#comment-4501647) where I wrote that the distance to which contacts are sent via Link-16 is insufficient. This means that AWACS is not able to send a SURV contact at a distance greater than 125 NM from the receiving aircraft (F/A-18). A model situation was used on a map of the Caucasus of an aircraft standing on the ground at Senaki Airport. AWACS transmitted its PPLI (one of the Link-16 messages) but was unable to send a SURV contact t
  8. Ok. And how can you display the SURV contact at a distance of 352 NM in an airplane or how did you find out that you were able to detect it. Is there a way to display this on DDI? The SA page only scales up to 320 NM. Thanks
  9. I did a test on the original mission from which the track is. The AWACS on my mission was the E-3A. I received the first SURV contact up to a distance of 126 nautical miles. This means that the problem still exists here. I exchanged AWACS for E-3D. Now there was a great surprise. Not only was I able to confirm your distance values but I even reached the nominal transmission distance. I obtained SURV contact from AWACS E-3D at a distance of 320 NM. The target flew in a parallel course with AWACS so that the test was not affected and it was easy to determine the distance for transmission. R
  10. The checklist page shows a different weight of GBU-32 than in ME. In the mission editor, the weight of GBU-32 is 1030 lbs. In aircraft, the checklist page shows the weight of GBU-32 531 lbs. Evidence Two screenshots from ME. The first is an aircraft without ammunition on pylons. The weight is 36775 lbs. The second screenshot shows an aircraft with one GBU-32 on the hanger. The weight is 37805 lbs 37805 - 36775 = 1030 lbs https://i.imgur.com/JbHhndC.jpg https://i.imgur.com/LV9B9jo.jpg Next are two screenshots from the aircraft displays. The first is the weight of the air
  11. If I want to get the TGT waypoint using the HUD, the AGR should be activated automatically. This is not happening. As can be seen on the track AGR does not activate when I give priority to the HUD (sensor switch FWD). Activation does not occur automatically even if I select a weapon in CCIP. I chose a cannon for the track. As soon as I put the sensor switch forward (on the HUD), the AGR must be activated automatically to measure the slant range and radar ground elevation. It should be automatic. In the current state, it is necessary to select the weapon and press the sensor switch FWD again an
  12. I sincerely hope not. 100 nautical miles is quite a bit. AWACS simply cannot fly so close to the combat zone. And we don't have another sensor (SURV) that would contribute to the Link-16 network in DCS. Even an aircraft carrier does not contribute to the network. I wonder how it is with the transmission distance of Link-4 at F-14 in DCS (from AWACS to plane)? I don't have this plane so I can't test it.
  13. It is strange. However, the TWS radar mod in DCS performs NCTR. . On the radar screen in the TWS is the item named NCTR(boxed). So if according to your message the TWS radar can't do NCTR. So there is a bug that has a different name? "NCTR is available in radar TWS mode". Because as I wrote, if I move the radar cursor in TWS at a distance below 25 nm to the target, the HAFU symbol on the host will change. The only information that can be changed according to the ROE matrix is NCTR (an aircraft that is marked as a hostile in the library). I also don't understand why the topic is marked as Co
  14. If I want to do NCTR in TWS the SA page will not show the aircraft type. The HAFU symbol is assigned correctly, but the aircraft type is not displayed even though it is in the NCTR library of the aircraft. The track is attached. Track
×
×
  • Create New...