|
Post by Lucas on Aug 15, 2014 13:58:55 GMT -5
Ok Travis.
Little update: I even set 116000 lbs in Absolute Max. Payload window in "Aircraft Characteristics" tab -> it also did not help.
|
|
|
Post by japo32 on Aug 16, 2014 10:11:33 GMT -5
Ok.. I know how to solve!!! the Airbus laod map that is in the library is BAD!!!! it is not well filled.. still there are numbers to fill!!! the units and size ones!!! that are cero and must be numbers... Those were my AAXE load maps... and I can now see that they are OLD and do not account for the Detailed Loading! If you can PM / email me the ones you've done, I will update the others... and perhaps add some 318/319 load maps too. ahhhh sorry.. I only made that one. The 320CFM one... and the numbers are over there. Others has to be made, but I guess once people know how to do them it will be fast to make. The problem with other planes is know which is the capacity in cargo (the maximun one). Well I guess is unlimited, because you can put an universe in a point as said in physics big bang theory. LoL!!
|
|
|
Post by Lucas on Aug 31, 2014 5:18:52 GMT -5
Hi Travis,
...any news in connection with my above problem?
Best regards, Lucas
|
|
|
Post by Travis on Aug 31, 2014 10:52:33 GMT -5
Hi Lucas, This is currently Dutch's #1 source of frustration. I think it's the main problem that's preventing an alpha release. When I know something, you will too.
|
|
|
Post by Lucas on Aug 31, 2014 13:19:14 GMT -5
Ok. Thanks for info, Travis. ...everything by me (sorry Dutch)
|
|
|
Post by Dutch Owen on Sept 1, 2014 15:56:18 GMT -5
Yes, Travis is right, I have had several cases of negative payloads generated and continue to see them. It would seem that would be easy to track down. but in fact as I trace it through the generator produces positive numbers but something later down the line punches a negative in there.
This can't be ignored because it's probably a "bad pointer", one of the worst things to find in a C++ program because it can originate in a section of code completely unrelated to the part that's getting smashed. Usually, it results in a crash which is fairly easy to find. The ones that don't crash but keep going, having messed up random pieces of data, are the worst. They are rare. It looks like we have one here.
I will find it. This will be the third such in the history of FSCaptain if I remember correctly, one during late Beta and the other after the release of 3.0.
Dutch
|
|
|
Post by Lucas on Oct 22, 2014 4:00:45 GMT -5
Dutch, 1.5.1 solve it. Thanks! Anyway, one more thing... [v 1.5.1, aircraft: PMDG777] When I want to set more than 234 passengers in Dispatch, I get warning that max PAX is 234, although, in Aircraft charcteristic there is 301 in „Passengers seat” box. Why? I also paste screen of Load Map of this aircraft: Note that in Optional Overrides normally there is 234 in „Passengers seat” box, but when I delete this value and want to Apply changes I get communicate as above (and after press OK, the same communicate for each station) – after last "OK" Load Map window closed but when I enter to Load Map of this aircraft again, 234 (in Optional Overrides) still exist. However, there is the truth, that PMDG programmed their 777 to take only 234 pax (via FMC loader).
|
|
|
Post by Travis on Oct 22, 2014 11:00:46 GMT -5
Lucas,
That error box means you need to set a value in each "Limit" textbox. Just multiply "Units" and "Size" and place the result in the "Limit" for each station.
The reason you see the "Max PAX is 234" is that your load map only has 234 seats. You'll have to increase some of the stations' sizes to squeeze more units... uh, passengers... onboard. (That is, as long as the PMDG systems allow you to do so... If you say that you have 300 PAX @ 170 lbs each, but PMDG only stacks in 234 @ their weight, you would likely have to reconcile the numbers each time.)
And for now I'd advise you to stick with 170 lbs for the FSCaptain PAX... I know that internally that value is used in a few places to make calculations... and this is a point that I would like to change in the future... I'm just not certain what the best path to take would be.
|
|
|
Post by Lucas on Oct 22, 2014 15:10:30 GMT -5
Simply I want to make a flight PMDG777 with more then c.a. 60000lbs payload (which is calculated for 234 pax). But now I can add extra Cargo weight in Dispatch (Dutch rapaired it and there isn't negative values ) - so, I think I'm at home...
And for your last sentence -> do you suggest that should I enter 170 in load map (as a size of pax station) for each aircraft I fly?
|
|
|
Post by Travis on Oct 25, 2014 0:21:19 GMT -5
And for your last sentence -> do you suggest that should I enter 170 in load map (as a size of pax station) for each aircraft I fly? If you're using the FSCaptain "autoloader" then I would say to definitely use 170lbs for the PAX weight.
If you're using another mechanism to load your aircraft, then I would say you should use your own judgment on what to do. If your numbers are all good and the ACARS does not ask you to "reconcile" your Dispatch & your Aircraft weights, then do nothing. On the other hand, if you have to repeatedly "reconcile" your weights, then adjust your FSCaptain weights (in your FSCaptain load maps) until you achieve harmony.
|
|
|
Post by Lucas on Oct 25, 2014 5:49:48 GMT -5
Understood. Thank you Travis.
|
|