Jump to content

Recommended Posts

Posted

As you will see in the track, the recovery cues for the non sea-level terrain is triggered way to late making the commanded CFIT recovery impossible. It seems that the dive recovery phase trajectory is not being calculated correctly with the system assuming the terrain after the calculated future impact point is at the same altitude. I.e. not accounting for upslope terrain, thus the warnings are triggered too late. 

TAWS.trk

  • ED Team
Posted

Hi, 

we have taken a look and we do not agree with your analysis, if you have public evidence to support your claims please PM me 

thank you

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, PIMAX Crystal

Posted
20 hours ago, BIGNEWY said:

Hi, 

we have taken a look and we do not agree with your analysis, if you have public evidence to support your claims please PM me 

thank you

Then the question is, why did the system in DCS fail? I performed a max performance recovery and still couldn't avoid the CFIT. The system assumes recovery will be less than a max pull to the max available G anyway, so there should be no way the CFIT should've happened unless the calculations were wrong somewhere. "...the TAWS-with-DTED mode and provides protection against varying terrain ahead of the aircraft." Check NFM-00 2.17.4.1

  • Like 1
  • 1 month later...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...