Context: MG HJET 2020 market place loaded in 2024 either through market place transfer or via community version
Bug description: MG HJET 2020 market place loaded in 2024 exhibits elevated fuel burn , almost 3x the amount in MSFS 2020, It seems like JET_density_on_FF doesn’t properly translate when running in 2024 environment , this doesn’t occur if package is natively built in 2024 environment
Repro steps: run 2020 version of MG HJET in 2024 , observe fuel burn not changing as a function of altitude
I tested version 2.1.2 of your package and I have similar results on MSFS 2020 1.38.2.0, MSFS 2024 1.2.11.0 and SU1 beta 1.3.22.0.
In all cases, JET_density_on_FF table was used and was impacting fuel flow at high altitude.
Can you elaborate on your test conditions and what data you obtained? What was the ambient density value when you have abnormal values?
@FlyingRaccoon
We have identified new information that changes our understanding of the problem. The issue is not related to MSFS 2020 vs. MSFS 2024, nor is it caused by the previously mentioned table.
Instead, the problem appears to be specific to Marketplace-streamed packages. When the aircraft is streamed via the Marketplace, fuel burn is approximately 4–5 times higher than when the same package is installed locally as a Community package.
During earlier testing, we distributed the 2024 builds to our beta team exclusively as Community packages, and fuel consumption behaved as expected. As we were preparing for a native 2024 release, this led us to believe the issue was confined to the legacy HJET package built for 2020. particularly since reports were only coming from users running the streamed Marketplace version.
However, we have now begun distributing the same builds to our beta team through Marketplace ingestion, and the issue immediately reappeared.
The attached images demonstrate the discrepancy under identical conditions, same altitude, same ISA, Same N1:
Marketplace-streamed package: ~2800 PPH (this is maximum fuel flow allowed as per engine.cfg)
@FlyingRaccoon
update : this is possibly related to the presence of a comment line underneath the JET_density_on_FF_table in the engines.cfg
I tried ingestion without this comment and fuel burn seems fine on streamed package.
is it possible that the ingestion conversion/encryption gets thrown off by comments?
will further verify with our testers.
That is precisely what I was looking at.
I think this is the source of the issue, this is correctly read when using the normal parser but goes wrong when read from fsarchive.
You just confirmed my theory
I’ll report this to the team in charge of ingestion tool so this can be handled or detected earlier.
This topic has been automatically closed after 60 days of inactivity since it was marked as fixed.
If there is important new information about this same report, you can use the “Request reopen” button below to ask the moderation team to review it again.
For other issues or broader discussion, please open a new topic in the appropriate category.
