|
Post by andy81le on Aug 16, 2014 16:39:33 GMT -5
Hey guys, stumbled upon a problem with my load map for the Tinmouse 732. I specify a flight via Flight Dispatch (Specify Flight Details) and fill in 120 PAX (max possible). It says that baggage load weight for bags will be added according to the PAX number. When I view the release however it only gives me the weight for the PAX but FSC has not added any bags (see the attached FSC Dispatch Release). Now, I have created a detailed loadmap for the Tinmouse, that specifies passengers seats (Y) as well as cargo holds (G) (See attachments), so I would expect FSC to load bags accordingly. I have removed Absolute Maximum Payload (LB) but still it won't load bags if the Tinmouse is full. I am at a loss here since I am not able to check whether FSC uses the correct ZFW and GW. Any ideas? Another problem I encountered seems to be the conversion from pounds to kgs. Since I am using simbrief that uses 175 lbs for a single PAX, I changed the setting in the items.cfg to 175 lbs. Now, after Adam Ries 120 PAX / 175 lbs each is 21000 lbs. Converted to kgs this should be 9525 kgs (factor of 2.2046). FSC however calculates 8855 kgs. Something is wrong there as well I fear. Attached my items.cfg to this thread as well. Any ideas? Cheers, Andreas release.pdf (33.08 KB) Attachments:Screenshots_FSC.zip (89.03 KB)
|
|
|
Post by Travis on Aug 17, 2014 11:55:18 GMT -5
Andreas, As an "Imperial Weighted American" (LOL) please let me take your numbers and crunch them over the next few days (of my "spouse-enforced vacation"). Do know that weights in our simulators come in only a few flavors - the aircraft (ZFW), the fuel, and the stations - which are ill-defined but thought of as "crew, constants, passengers and cargo." FSCaptain does try to take the "fuel weight" and "stations weight" and to give us reasonable loads... but sometimes there are oddities which we're cataloging and offering corrections for. You've given us enough to chew on, and as the Tinmouse is Dutch's favorite a/c... I'm hopeful that any discrepancies will be corrected in an upcoming 1.5.1 beta build.
|
|