Passenger load does not match sim brif data

[jack153]

i have the 737-800 loaded with 184 seats but 214 how is that possible?

[Fiorentoni]

Me too. Had 184 on Simbrief, but 214 in GSX.

[virtuali]

Please check ALL the conditions using Simbrief have been satisfied, Page 60 of the manual.

If you want to check what GSX is doing, just turn on logging, and activate a gate, there's a lot of diagnostic about SimBrief, telling all the possible reasons why your flight plan hasn't been used.

One thing that can be easily overlook is the airplane ICAO type, if you use the default profile for a 737-800 on Simbrief, the airplane code is B738, which is the official ICAO type for the airplane. However, PMDG has set the icao_model in the aircraft.cfg as "737-800", GSX obviously read the icao code from SimBrief *and* the icao code from the airplane, so it expects them to match, otherwise it would think the airplane it's not the correct type.

Unfortunately, the ICAO code in Simbrief airplane editor only accepts 4 characters, so I guess your best option would be editing the aircraft.cfg to read B738, or ask (gently) to PMDG if they would be willing to use the standard ICAO type in the icao_code field of the aircraft.cfg.

[bjratchf]

It looks like the PMDG 737-800 has the incorrect ICAO code listed in the aircraft.cfg- they have it as B737 and 737-700

Correct the entries so they look like this:

[General]
atc_type="BOEING"
atc_model="B737"
Category = "airplane"
icao_type_designator="B738"
icao_manufacturer="Boeing"
icao_model="737-800"

[moxiejeff]

THANK YOU! This has been driving me crazy as well on 738.

[jack153]

It looks like the PMDG 737-800 has the incorrect ICAO code listed in the aircraft.cfg- they have it as B737 and 737-700

Correct the entries so they look like this:

[General]
atc_type="BOEING"
atc_model="B737"
Category = "airplane"
icao_type_designator="B738"
icao_manufacturer="Boeing"
icao_model="737-800"

where should the path to this be?

[virtuali]

icao_model should be "B738", that's the official ICAO code which is also what Simbrief use.

[moxiejeff]

It looks like the PMDG 737-800 has the incorrect ICAO code listed in the aircraft.cfg- they have it as B737 and 737-700

Correct the entries so they look like this:

[General]
atc_type="BOEING"
atc_model="B737"
Category = "airplane"
icao_type_designator="B738"
icao_manufacturer="Boeing"
icao_model="737-800"

where should the path to this be?

Should be the PMDG 737-800 folder in your community folder

[pinolo1978]

sorry, so why it works correctly should I change from "737-800" to "B738"? right?

[virtuali]

Exactly, because that's how Simbrief use, and the two ICAO code must match for GSX know you are using the same airplane type.

[hammertime]

icao_model should be "B738", that's the official ICAO code which is also what Simbrief use.

Thanks for everything so far... To clarify the above though... There are a load of similar inconsistencies across other aircraft/developers, if icao_model is expected to be the icao type code from a GSX / SimBrief integration POV...

Fenix A320 - icao_model =A-320
FBW A320 mod & Default Asobo A320neo - icao_model = "A-320neo"
I can't easily check Asobo's or "Heavy Division's" B78X cos it doesnt have a traditional aircraft.cfg
There are obvious errors in PMDG's B738, so no need to go over that again

Asobo's SDK seems a little ambiguous as purpose of icao_model, and what strings developers should be conforming to

The ICAO model name of the plane. It can be different to the atc_model field. For example the Textron 172 Skyhawk:

icao_model = "172 Skyhawk"

However, there is the icao_type_designator= string, which does seemingly from my admittedly rather layman's perspective, more widely conform to aircraft ICAO standards across all possible aircraft-types (and developers)

PMDG have admitted that the atc_model= and icao_type_designator= strings were an oversight, so can be manually corrected, pending an update from PMDG

https://forum.pmdg.com/forum/main-forum/general-discussion-news-and-announcements/212560-24aug22-pmdg-announces-release-of-pmdg-737-800-for-microsoft-flight-simulator?p=212717#post212717

[virtuali]

However, there is the icao_type_designator= string, which does seemingly from my admittedly rather layman's perspective, more widely conform to aircraft ICAO standards across all possible aircraft-types (and developers)

It's in fact very easy to get confused because all these different naming standard, I said GSX checks for the icao_code but, in fact, that's how it's called in SimBrief, more precisely is the <icaocode> tag in their returned XML for the current dispatch.

However, when checking with the airplane, GSX of course checks the icao_type_designator, as it should be, I took the default A320 Asobo as an example, which indicates A20N (correct) and the Fenix A320 (correct), so I think there's no doubt this IS in fact the official ICAO code for the airplane type.

[hammertime]

However, when checking with the airplane, GSX of course checks the icao_type_designator, as it should be, I took the default A320 Asobo as an example, which indicates A20N (correct) and the Fenix A320 (correct), so I think there's no doubt this IS in fact the official ICAO code for the airplane type.

Brilliant, thanks for confirming this is the property in question when GSX checks SimBrief dispatch.

I'd maybe somehow gotten myself confused when folks started talking about icao_model

[jack153]

this entry change leads to the next error so only 9 pax are loaded so this does not work either

[Fiorentoni]

this entry change leads to the next error so only 9 pax are loaded so this does not work either

This usually happens when the scenery's data is not loaded correctly by GSX or when jetway data and scenery data mismatch. What airport was it and what scenery? Was it a marketplace airport? And if 3rd party, did you exclude the GSX jetways for that airport?