AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
![]() ![]() Yes, you may have 10-20 less virtual 'butts' in seats but your plane will still operate at the weight setting that everything is calculated as being. Let PFPX generate a ZFW with your custom seating configuration and then manually input the ZFW in TOPCAT. PAX + bags + freight = weight (it rhymes!). So, If I load the Delta config at it's max of 269 pax but the PMDG model will only support 234, TOPCAT does not convert the additional pax weight as cargo or freight. Continuing the example, the PMDG 77L is in a very much less dense seating that many r/w airlines (again, like Delta). TOPCAT tries to read the weight from PFPX. PFPX and TOPCAT don't generate an error, though, because pax = weight and the ZFW < MZFW so everything is in accordance, until. However, I started seeing the error when my config in PFPX (modeled after the r/w seating) placed more passengers than the FSX model can handle. Sometimes, if the airline operates with less seats than the aircraft model has as default, this works out okay, e.g., Delta Air Lines uses a less dense seating arrangement on its 76Ws than the Level-D model has allocated so I don't have a conflict. I have been a little anal-retentive about making my planes in PFPX match their rw airline configs. I think I may know what's sometimes causing the ZFW to be incorrectly transmitted from PFPX to TOPCAT.Īre you using a custom seating arrangement or passenger load total in PFPX or TOPCAT? ![]()
0 Comments
Read More
Leave a Reply. |