picture No.1 and No.2 shows that passenger numbers does not match what I set on FMC.
Of course they don't match, the passenger number set in the FMC is an internal variable only known to the airplane, so GSX can't read it, which means when you set the passenger number based on Payload, is an ESTIMATE, which as clearly explained in the manual, is done by dividing the payload by 220 lbs.
If you want the number to match, you should use SimBrief AND set the same number of passengers in the PMDG FMC, because the PMDG FMC is not automatically integrated with SimBrief so, even if GSX WILL read SimBrief, it's your responsibility to set the same number in the PMDG FMC, if you want them to "match".
And simbrief way, it always tell me SimBrief aircraft doesn't match MSFS aircraft
That's ANOTHER completely different issue, which has been discussed so many times on the forum that it's basically impossible to read the forum and not being able to find it, I'll repeat it again for the 100th time:
- The PMDG 738-800 has B737 icao_type_designator, which is the icao code for the -700, so you need to edit the aircraft.cfg and change it to the correct code, that is B738. The -600 and the -700 are fine.
and another issueGPU requested, it will show up but not functional
This has been asked and answered so many times on the forum as well: the GSX GPU cannot affect the PMDG electrical system, which has its own internal simulation, so you need to use the PMDG GPU instead.
by the way, from a longer distances, every suitcases will be disappear. so does sunshine glasses on the by-pass pin guy
That's exactly what is supposed to happen with a properly optimized product. Lower LOD levels enters in view to keep the fps up, by removing unnecessary things, like sunglass on "longer distances"
