Jump to content

Leanscrush

Frozen-Inactivity
  • Content Count

    6
  • Donations

    $0.00 
  • Joined

  • Last visited

Posts posted by Leanscrush


  1. 1 hour ago, RXP said:

    @Leanscrush ok the bug is identified and I'm sorry for the confusion, I've had XPlane in mind, where the 'simvar' equivalent is in weight and we do convert based on fuel density. However, in FltSim the simvar reads in volume and we unfortunately let slip the convertion code in. Therefore, your GTN (and GNS V2) reads the correct value times the density.... This will be fixed in the next updated, most likely after the holidays now.

    Thank you for the great support Jean-Luc!

    • Upvote 1

  2. 1 hour ago, RXP said:

    All in all, the fuel values (like Quantity and Flow) are just read from the FltSim SDK simvars. The only operation going on is conversion from/to weight/volume when necessary, all based on fuel density, using the actual internal GTN (or GNS) fuel density tables to match the Garmin readout values.

    I'd suggest you compare the readouts with a default aircraft first, like the B58, and validate the values. It is possible third party aircraft 'trick' the underlying FltSim engines to make their readouts closer to expected, at the expense of false underlying simvar readouts. It also possible there is a discrepancy (or a bug) in our code when doing the conversions (hence the suggested test above), or in theirs (reading simvars with non matching units for example, or interpreting the simvar values wrongfully).

    I tried with the default baron, but still having the same problem. 

    pybQLel.jpg

    • Upvote 1
×
×
  • Create New...