Range/Endurance AOA

[Swift.]

As written in NATOPS [paragraph 7.2.8], best range is approximated by flying 4.2 AOA and best endurance by flying 5.6 AOA.

 

In DCS these AOAs are not what is shown when flying the recommended Mach for best performance from the FPAS. These AOAs are also not shown when flying the rule of thumb of 250 for endurance and 300 for range.

 

The relatively large difference between the shown AOAs and these numbers from NATOPS, could be caused by an error in the FPAS calculation, or in the HUD indications. Either way I would request that the AOA behaviour for range and endurance is verified in the upcoming FM updates.

[Harker]

I suspect that part of the reason the FPAS is messing up is because there's something wrong with the altitude calculation in the Hornet. I'm not saying that this will solve the FPAS issues entirely, buy it's related.

 

For a lot of things, the displayed barometric altitude is ignored and the "real DCS altitude" is used (that you can see with F2). The FPAS is one of those things. This makes no sense, since the bsro altimeter is the aircraft's only altitude source.

 

You can check that by flying at FPAS optimum altitude. The OPTIMUM and CURRENT Mach should now be the same, but in DCS, it's not.

 

Also, if you set up a baro altitude floor, the ALTITUDE ALTITUDE warning will trigger not when your altimeter (or HUD) pass it during descending, but when your "real DCS altitude" passes it.

 

I'm preparing a bug report for this.

[fagulha]

I suspect that part of the reason the FPAS is messing up is because there's something wrong with the altitude calculation in the Hornet. I'm not saying that this will solve the FPAS issues entirely, buy it's related.

 

For a lot of things, the displayed barometric altitude is ignored and the "real DCS altitude" is used (that you can see with F2). The FPAS is one of those things. This makes no sense, since the bsro altimeter is the aircraft's only altitude source.

 

You can check that by flying at FPAS optimum altitude. The OPTIMUM and CURRENT Mach should now be the same, but in DCS, it's not.

 

Also, if you set up a baro altitude floor, the ALTITUDE ALTITUDE warning will trigger not when your altimeter (or HUD) pass it during descending, but when your "real DCS altitude" passes it.

 

I'm preparing a bug report for this.

 

Thank you.

F.