Jump to content

[NOT A BUG] G limiter is based on CHKLIST weight instead of actual weight


Recommended Posts

Posted

The G limiter does not get the correct value. Instead of being based on the aircraft's actual weight, it's based on the weight displayed in the CHKLST page, which is not calculated correctly (this is confirmed by ED and is another bug, most likely related to this one).

 

TEST:

 

Two aircraft with similar weight: One is clean (with more fuel) and the other carries four missiles (with less fuel).

 

A) [Clean], 55% fuel, 31914 lbs in ME (~31950 in the mission) 7.5G

 

B) [2x9M, 2x120C], 42% fuel, 31844 lbs in ME (~36150 in the mission) 6.8G

 

Aircraft A is limited to 7.5G which is correct. Aircraft B is limited to 6.8G, which is not correct.

 

Note that 6.8G to matches the NATOPS chart for 36150 lbs (the wrongly calculated aircraft weight). To me, this confirms that the number is based in the weight indicated in the CHKLST, rather than the actual weight.

 

The attached track demonstrates the bug.

 

The effect this has is that we cannot pull the amount of G that the aircraft is capable of, without pulling the the paddle switch (which can give you more than 7.5G and, if you want to fly realistically, is generally not a good idea).

WeightGLimitTest.trk

WeightGLimitTest.thumb.PNG.d0de270cac03db9a2c6959e1e551e1cb.PNG

  • ED Team
Posted

It is not a bug. FLCS takes weight from mission computer and this weight is displayed in CHKLIST page. So FLCS is working correctly, based on computed weight.

The issue is that computer calculates weight not correctly, but it is different from what is described. And it has been already reported.

Posted
It is not a bug. FLCS takes weight from mission computer and this weight is displayed in CHKLIST page. So FLCS is working correctly, based on computed weight.

The issue is that computer calculates weight not correctly, but it is different from what is described. And it has been already reported.

 

Fair enough. Your statement is likely technically correct.

 

You might be referring to a bug report that I haven't seen. The bug I have seen is this one: https://forums.eagle.ru/showthread.php?t=247311&highlight=weight

It only brings up the symptom in the CHKLST page. The mission computer is not mentioned. In a reply Svend_Dellepude asks "Could I be right in assuming that the FCS G-limiter is also affected by this?". Bignewy says he IS NOT sure, but assumes it (i.e has not tested it).

 

Now I have tested it and provided a track for it, so he can be sure. You're welcome.

  • 2 weeks later...
Posted
It is not a bug. FLCS takes weight from mission computer and this weight is displayed in CHKLIST page. So FLCS is working correctly, based on computed weight.

The issue is that computer calculates weight not correctly, but it is different from what is described. And it has been already reported.

Reported 3 months ago! And nothing so far, only "it's been reported".

 

OP described the bug correctly, what do you mean with "The issue is that computer calculates weight not correctly, but it is different from what is described", that's what OP is saying ???

 

It's a basic function that should have been solved by now instead we're flying at faster AoA speed for 3 months now :doh:.

i7 8700k@4.7, 1080ti, DDR4 32GB, 2x SSD , HD 2TB, W10, ASUS 27", TrackIr5, TMWH, X-56, GProR.

  • 2 months later...
  • Recently Browsing   0 members

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