Client 2.4 Beta
Moderator: FSAirlines Staff
Re: Client 2.4 Beta
FYI - It does it with 2.3.3 too! Max cargo capacity listed as cargo weight in the Client. So when we hit change we are just tossing out baggage and not packages? There's 2800 lbs of "extra cargo" (baggage) that is not paying cargo. If you are going to keep this complex system, you need to make that it's own line in the Client called Pax Bags or something.
added more: OR make sure the baggage weight adds in with the passenger weight so if you bump a passenger, you get their bag to go with.
added more: OR make sure the baggage weight adds in with the passenger weight so if you bump a passenger, you get their bag to go with.
- joefremont
- FSAirlines Developer
- Posts: 3852
- Joined: Tue May 16, 2006 5:46 am
- Location: KSFO
Re: Client 2.4 Beta
You can't remove packages from the client, but you can bump the general cargo or passengers (poor passengers, always getting the short end of the stick).
The baggage is not included in the cargo weight, but instead in the passenger weight, the passengers always get there bags when they get off the plane.
The baggage is not included in the cargo weight, but instead in the passenger weight, the passengers always get there bags when they get off the plane.
I've sworn an oath of solitude until the pestilence is purged from the lands.
Re: Client 2.4 Beta
What I am saying is the passenger bags are showing up as general cargo in the Cargo line.
added: My max cargo generic and packages together was 13,034. But the Client is showing the cargo at 15,844 which can only be the passenger bags added in. I did the math and it's 55.174 lbs per passenger.
added more: so I only had 297 generic cargo.
But the way the Client reads, I would think I could dump up to 2058 lbs of "cargo" with the CHANGE tab before it stops at the package cargo of 12,786.
added: My max cargo generic and packages together was 13,034. But the Client is showing the cargo at 15,844 which can only be the passenger bags added in. I did the math and it's 55.174 lbs per passenger.
added more: so I only had 297 generic cargo.
But the way the Client reads, I would think I could dump up to 2058 lbs of "cargo" with the CHANGE tab before it stops at the package cargo of 12,786.
Re: Client 2.4 Beta
OK I just landed KABQ and the flight report says I got paid for 3058 cargo + 12787 packages = 15845 total. The pre-flight briefing only allowed me to load 12,787 worth of packages as the max cargo with this pax load was 13,034. So I got paid for 2761 lbs of passenger bags as generic cargo.
Flight LAS1231 5-11-20 20:19
It is NOT a Client issue! I used the 2.3.3. So it is something in the system prior being sent to whatever Client is being used.
FSX-SE Win10
Flight LAS1231 5-11-20 20:19
It is NOT a Client issue! I used the 2.3.3. So it is something in the system prior being sent to whatever Client is being used.
FSX-SE Win10
Re: Client 2.4 Beta
Maybe FSA is like real airlines now and charging bag fee's?
- joefremont
- FSAirlines Developer
- Posts: 3852
- Joined: Tue May 16, 2006 5:46 am
- Location: KSFO
Re: Client 2.4 Beta
Are you saying the cargo amounts in the report are not matching the cargo in the flight? This may require some investigating.
I've sworn an oath of solitude until the pestilence is purged from the lands.
Re: Client 2.4 Beta
OK, I have been crunching some numbers and something is going on with pax bags and packages.
How hard would it be to add a separate field for pax bags?
Is it supposed to be part of the 224 pax weight?
I assume the bag weight of 55 per pax comes off the cargo capacity as well?
If these assumptions are correct ..... numbers are not adding up:
CRJ7 Flight May 8, 2020 LAS3423 Pilot Sam S. ALL WEIGHTS IN LBS
Generic Cargo: 2306 + Packages: 3527 + pax bags (56@55ea) = 8913 Capacity of the cargo hold on a CRJ7 is 6614
Pax weight - bags = 9464 Max payload on CRJ7 (ZFW-DOW=MPL) is 18,801 payload this flight 18,377 so we were 424 below MZFW yet over capacity in the cargo hold by 2,299 lbs. I must have something wrong in how I calculate all this. Nothing is adding up.
Here's another interesting tidbit: 6614-3527 packages = 3087 just about the weight of pax bags at 55 lbs each (3080). So the pre-flight planner is calculating the bag weight prior to cargo loading.
How hard would it be to add a separate field for pax bags?
Is it supposed to be part of the 224 pax weight?
I assume the bag weight of 55 per pax comes off the cargo capacity as well?
If these assumptions are correct ..... numbers are not adding up:
CRJ7 Flight May 8, 2020 LAS3423 Pilot Sam S. ALL WEIGHTS IN LBS
Generic Cargo: 2306 + Packages: 3527 + pax bags (56@55ea) = 8913 Capacity of the cargo hold on a CRJ7 is 6614
Pax weight - bags = 9464 Max payload on CRJ7 (ZFW-DOW=MPL) is 18,801 payload this flight 18,377 so we were 424 below MZFW yet over capacity in the cargo hold by 2,299 lbs. I must have something wrong in how I calculate all this. Nothing is adding up.
Here's another interesting tidbit: 6614-3527 packages = 3087 just about the weight of pax bags at 55 lbs each (3080). So the pre-flight planner is calculating the bag weight prior to cargo loading.
- joefremont
- FSAirlines Developer
- Posts: 3852
- Joined: Tue May 16, 2006 5:46 am
- Location: KSFO
Re: Client 2.4 Beta
Hi Sam, I ran the numbers on that flight and your right it had too much cargo. When the flight started it was supposed to zero out the general cargo as the baggage plus the packages would fill the space. Will investigate more.
I've sworn an oath of solitude until the pestilence is purged from the lands.
Re: Client 2.4 Beta
Hopefully the fix will be "going forward" and not retroactive to all flights or airlines with 3rd party financial departments like ours will have to add some "misc adjustment" figure to once again balance with FSAirlines. Trying to retroactively fix every flight will be impossible.
- joefremont
- FSAirlines Developer
- Posts: 3852
- Joined: Tue May 16, 2006 5:46 am
- Location: KSFO
Re: Client 2.4 Beta
Oh no, I have no intention of going back and fixing flights. When I do that its been because VA's were deprived of revenue rather than getting extra, or if VA's were intentionally exploiting a loophole which I don't see in this case. I was doing some flights over the weekend testing and my flights did not have this problem, but then the baggage plus the packages did fill the space, that may be an avenue of inquiry to persue.Cat wrote: ↑Wed May 13, 2020 5:14 pm Hopefully the fix will be "going forward" and not retroactive to all flights or airlines with 3rd party financial departments like ours will have to add some "misc adjustment" figure to once again balance with FSAirlines. Trying to retroactively fix every flight will be impossible.
I've sworn an oath of solitude until the pestilence is purged from the lands.
Re: Client 2.4 Beta
Perhaps listing the bags as a 3rd payload field?
'non revenue / non changeable'
much like the new 'crew weight'
'non revenue / non changeable'
much like the new 'crew weight'
Re: Client 2.4 Beta
This is just an FYI, it is not critical to operations:
For some reason the client does not read the exact sim weights correctly.
The Zero Fuel Weight is off by 4 lbs and the Takeoff weight is off by 2 lbs.
Also the price for fuel is showing as "initial fuel" and not "additional fuel". I am assuming that is for spacing only in the Client and the actual fuel billed is for additonal fuel and not the fuel already paid for and in the tanks.
For some reason the client does not read the exact sim weights correctly.
The Zero Fuel Weight is off by 4 lbs and the Takeoff weight is off by 2 lbs.
Also the price for fuel is showing as "initial fuel" and not "additional fuel". I am assuming that is for spacing only in the Client and the actual fuel billed is for additonal fuel and not the fuel already paid for and in the tanks.
- joefremont
- FSAirlines Developer
- Posts: 3852
- Joined: Tue May 16, 2006 5:46 am
- Location: KSFO
RC4
Hi Flyers, I have just released 2.4-RC4. The changes in it included.
- In the client inflight debug screen it now shows the current sim rate, distance and bearing to destination airport.
- Several changes to try to reduce in flight aborts.
- Autosave disabled for MSFS 2020.
- Changes in sim rate displayed as messages in MSFS 2020.
- If pilot attempts to close the client when the flight is active it will display a message box to confirm the change.
My current plan is that I am waiting for MSFS 2020 to be released before releasing the official 2.4.0 stable client. As soon as I can test with the final build I will get the client out. I have been testing the client on the closed beta and so far it is working well.
If you have been keeping track you will notice there was no RC3, that was because it was a version I built with extra debug so I could try to figure out some of the in flight aborts pilots have been getting.
- In the client inflight debug screen it now shows the current sim rate, distance and bearing to destination airport.
- Several changes to try to reduce in flight aborts.
- Autosave disabled for MSFS 2020.
- Changes in sim rate displayed as messages in MSFS 2020.
- If pilot attempts to close the client when the flight is active it will display a message box to confirm the change.
My current plan is that I am waiting for MSFS 2020 to be released before releasing the official 2.4.0 stable client. As soon as I can test with the final build I will get the client out. I have been testing the client on the closed beta and so far it is working well.
If you have been keeping track you will notice there was no RC3, that was because it was a version I built with extra debug so I could try to figure out some of the in flight aborts pilots have been getting.
I've sworn an oath of solitude until the pestilence is purged from the lands.
Re: Client 2.4 Beta
Clicking IGNORE seems to work tho.
NOPE now I'm "locked out"
Re: Client 2.4 Beta
DUHHHHH BLONDE MOMENT
NEVER TRY TO INSTALL THE CLIENT WITH THE SIM RUNNING JEEPERS CREEPERS - BASICS 101 - MY BAD
I had to do a full computer reboot and then all was fine.
There is nothing wrong with the installer package.
NEVER TRY TO INSTALL THE CLIENT WITH THE SIM RUNNING JEEPERS CREEPERS - BASICS 101 - MY BAD
I had to do a full computer reboot and then all was fine.
There is nothing wrong with the installer package.