Hi Bryan,

Last week I noticed a problem, using the FS2Crew FBW A32NX project, with regard to the Baggage Services. When running BEFORE START below the line Checklist,  WINDOWS/DOORS CLOSED reported 'are you sure'. Checking the ECAM-Doors page I found that main door was closed, and Stairs removed, but Cargo Door was still open and Baggage Services still running. Tried to stop the services via PBE, but didn't work.

This morning i repeated the whole procedure, with only JETWAY and BAGGAGE CARTS checked in the FBW Config and all PFE GRD Services unchecked in PBE Config. After the FA message asking if they can close, at about 17 sec before end of the PFE, Stairs are moving and Main door closes, but Baggage Services continue to run. Cargo Door is open and Belt is in place and carts are moving in circles, as usual in MSFS.

Is this a recent bug in MSFS or FS2Crew FBW, or FBW A32NX? I am not sure whether I earlier tested the Baggage Carts in the PFE GRD SERVICES and had the same issue. The only way to stop the Baggage services is via MSFS ATC, Ground  Services, Requesting Baggage Services, and when it has started asking for ending the Services. This is nog really an option for me, because if have switched of the MSFS ATC services. Also manual running the Baggage Services via PBE is nog working, the services also do not stop when you click the button.

I am using recent versions of software, Windows 11, MSFS v.1.24.5.0, FBW-A32NX DEV version3528d3e (Apr 8), FS2Crew-FBW v.1.1.34, -PBE v2.2.22, -RAAS v.1.2.9, FSUIPC v.7.3.2.

I checked the forum for other topics, but didn't find anything, so it looks like it is only me.

Any ideas for a solution, if you need more info, please let me know.

Reinier Nieuwboer

Are you using any other addons at the same time that attempt to control the baggage cart?

Make sure you're not on the ground services page in the FBW's EFB.

 

I just reproduced the issue, and I can confirm the baggage services keep connected. I just made and adjustment, and it will be fixed on next update

Manuel

It appears Asobo changed the baggage cart logic so we can now control when it disconnects.  Before it would auto disconnect.  We'll be updating the various MSFS FS2Crew's as required.

Bryan and Manuel, thanks for your immediate response and solution. I'll install the updates when available.

Reinier Nieuwboer

It looks like the problem I reported above, hasn't been solved yet. I wasn't able to test it earlier then yesterday. I have MSFS and all FS2Crew modules updated to the last version, but bagageservices aren't stopped during the PFE in FBW A32NX Project. Main door is closing, but cargo door stays open, and baggage services are still runnng. During Before Start checklist below the line, Windows/Doors Closed you get a warning.

I noticed that if I ignore the door warning and Connect Tug, in PBE, then Baggageservices stop and cargo door closes, after about a minute. But that should happen during the the PFE script  in FS2Crew FBW A32NX Project.

I use temporarily the FBW Flypad Baggage Service, but it would be better if it is working again in the FS2Crew module. Hope you have a solution.

Reinier Nieuwboer

Hi Reinier,

Please confirm:  Are you using Pre Flight events?  If so, with FS2Crew: FBW or PBE?

 

Hi Byork, 

Yes, I use PFE with FS2Crew-FBW-A32NX, I have unticked all Services in PBE. I am also using RAAS, but that will not influence the services I assume. And I am using both FBW and PBE with button-control.

Please let me know if you need other info.

Best Regards,

Reinier

Hi Byork,

Afer answering your question, yesterday, I did some further testing. When starting again the FS2Crew-FBW, I noticed that all settings were reset to default, this happened only to FBW, not to PBE and RAAS. I inserted back my old settings and did a quick test, and it looks like the problem with the cargo, truck, belt and door, were solved. I didn't however have enough time to look into detail. After the install of the last updates of the FS2Crew modules on May 29, I did 2 Windows 10 updates, an update of the FBW aircraft, and a world update in MSFS. So difficult to track, what wiped the settings in FS2Crew-FBW.

This morning I started a new test, with MSFS and all add-ons open, and watched in External view what happens after starting the FS2Crew-FBW PFE. No other actions in the aircraft, except opening Flypad, and importing Flightplan and Fuel from Simbrief,  to see what happens. No services set in FBW Flypad.

I see the following actions, after starting PFE

~29 Stairs and Powertruck come in, and Walkaround FO starts

~27 Fuel truck appears

+22 FO back, No issues in walkaround, Catering truck appears

+19 Assistant asks if boarding can start, cargo door opens, belt appears, cargotruck comes in and starts loading cargo.

+18 Cargotruck ready and moves away,

+17 Belt removed and cargo door closed, Catering truck moves and door closes.

BUT THEN SURPRISE

+11 Belt comes in 2nd time, cargo door opens and cargotruck starts loading 2nd time.

+10 Cargotruck ready and moves away

+ 9 Loadsheet reported. Cargobelt moving away and cargo door closes.

+ 4 Welcome on board message

+54s Powertruck disconnected and moved

+19s Stairs removed and main door closes

I assume the first cargoloading, at +19m is initiated by FS2Crew-FBW, question is what triggers the 2nd cargoloading (MSFS, FBW?) and has that caused my earlier reported problem?

Anyhow, I will this afternoon first update the FBW aircraft, to the last DEV version, my version is June 5,  then do again a full test, with all my add-ons,with the full Cockpit Preparation, and Checklists in FS2Crew. I will report to you the result later.

Best regards,

Reinier

 

 

 

Hey Reinier,

4 hours ago, Erni49 said:

I assume the first cargoloading, at +19m is initiated by FS2Crew-FBW, question is what triggers the 2nd cargoloading (MSFS, FBW?) and has that caused my earlier reported problem?

The first at +19m is initiated by FS2Crew-FBW. The second FS2Crew-FBW is sending a signal to dismiss, because in previous MSFS updates the cargo truck stayed all the way, so it was neccesary to send a signal to release the cargo, but seems with MSFS recently updates, the cargo is dismissed automatically, so the signal for sending to dismiss, is causing to request it again (know what i mean?). It's what i can see know recently.

Cheers,

Manuel

Hi Manuel,

Thanks for paying attention to this issue. I understand your remark about the second trigger.

I spent yesterdays afternoon and this morning on further testing and I think I found the cause for this issue. My conclusion is that it is not an FS2Crew issue, but a MSFS issue.

It is related to the gate you use for departure. Some gates, one of them is the gate I used for my testflights, are sending the baggagecarts into a never-ending loop. The baggagecarts are running in circles, belt stays in place and cargodoor is not closed. It looks like it takes too long for the  belt to come in the correct position. 
It doesn't make any difference whether you start the baggage services from FS2Crew, FBW-Flypad-Services, or from MSFS-ATC-GroundServices, in all cases the carts keep going in circles and cargodoor stays open. 
Although when the Baggage Services are started from MSFS-ATC-Groundservices, you have an option in the Menu to stop, via REQUEST BAGGAGE SERVICE END. And when you have done that, you can restart the Baggage Services (also with FS2Crew or FBW-Flypad) and the baggage is loaded, belt removed and cargodoor is closed. I have tested this also with the ASOBO A320Neo, with the same result. 

Anyhow, I suggest to remove the second signal in the PFE. On a gate were the baggageservices work, you won't need it. If you're on a gate were the baggageservices do not work, a second trigger doesn't work either. 

I will check the Flight Simulator forum if this bug is already reported, if not I will try to report it.

So for now, two workarounds, for gates that don't work:
1. Find another gate, were baggageservices do work.
2. After selecting in FS2Crew-FBW PFE (you need electricity in the plane), go to MSFS Menu ATC and select GROUND SERVICES, and then REQUEST BAGGAGE SERVICE, wait until the carts go around in a loop. Select then in the ATC Menu REQUEST BAGGAGE SERVICE END. Check if cargodoor closes and now the baggage services will be started in the PFE and ended as they should be.

If you want to test, please start the flight with FBW-Aircraft from the WELCOME screen, WORLD MAP, FROM: EHBK (Maastricht-Aachen), GATE A2-RAMP GA LARGE and Fly. Start FS2Crew-FBW, with alle groundservices selected, and start PFE. Switch to the external view in MSFS. At about 19 min to go, after the message can we start boarding, you will see the baggageservices starting, first the belt searching for a good position, then the carts going around, in a loop. 
When you choose on the same Airport, GATE B1-RAMP GA (LARGE}, everything works ok.

Thanks for your time,

Reinier

Edited June 10, 20224 yr by Erni49
typo

Wow, I would never knew it was MSFS itself. The only way of knowing is making extensive tests as you did. So basicly from our side, we would need to remove completely the second signal to dismiss the baggage cart right?, just to confirm.

This problem has been around for a while and we also were confused why it happened, we thought it was something wrong with our program.

Cheers,

Manuel

Manuel,

Sorry for the delay in confirming, I had some other business then Flightsimulation. As far I have tested, I can confirm, you can remove the second signal. When you are on a suitable gate/parking the first signal will do the job and the second is not needed. 

Another interesting question is which command comes from the MSFS Menu ATC GroundServices REQUEST BAGGAGE SERVICE END, that stops the Baggage Services. I think it differs from the start command.

best regards

Reinier

13 hours ago, Erni49 said:

When you are on a suitable gate/parking the first signal will do the job and the second is not needed. 

Roger that

13 hours ago, Erni49 said:

Another interesting question is which command comes from the MSFS Menu ATC GroundServices REQUEST BAGGAGE SERVICE END, that stops the Baggage Services. I think it differs from the start command.

It's same as the start command, talking about programmatically way, it's just an event.

Cheers,

Manuel