This situation arises when you use the "useCustomFlapLeverParameter=1" option in the AB_ND_GDI.ini file.

As for the background as to how I discovered this, I have the Thrustmaster Airbus Quadrant and Add-On, and I bought 3rd party custom detents for the thrust levers and spoilers.  There is "official" Aerosoft guidance for tweaking the throttles in AB-ND_GDI.ini so as to support the new (more realistic) locations of the "climb" and "flex" detents.  The problem is, you have to disable support for the Quadrant in the Aerosoft configurator, and that "broke" my flaps.  But when I used the line above (default is set to 0), FS2Crew didn't work properly with respect to the flaps.

In the meantime, I've been able to get it to work well enough with custom detents set up through FSUIPC, which work well enough when extending at least (retracting, I can't figure out how not to skip over Flaps 2 for some reason).  It's annoying, but considering I usually never touch the lever myself anyway, it works well enough for the rare occasion the FO becomes incapacitated.  Still, thought it might be helpful to report in case for some reason it's not a known issue.

The call outs are sounded but no action.

I have the following issue and do not know how to resolve it:

When running FS2Crew with the Aerosoft A320 Pro and UGX in parallel then there are some flow duplications: There is ground crew interaction (e.g. engine start, disconnect) within the FS2Crew Airbus software while UGX is covering the same / similar flows

Is there a way to suppress the ground crew communication within the FS2Crew Airbus product?

Thank you very much for your help in advance.

Tilo

FS2Crew for the AEROSOFT AIRBUS PRO (P3D V4 and V5) has been updated!

To obtain this free update, login to your FS2Crew account, click "Completed Orders", re-download and re-install.

If you purchased from a 3rd party vendor, please wait for them to update the file on their server.

There is no stand-alone update installer.

Updates are built into the main installer only.

Change Log:
 

Version 4.3

Release Date: 1 April 2021

• Fixes issue discovered with the TO CONF Button code that could result in spurious ECAM messages at the end of the flight.

Version 4.2

Release Date: 9 March 2021

• TO Config button code updated to account for recent changes in the Aerosoft Airbus host aircraft.

Version 4.1

Release Date: 27 June 2020

• New P3D V5 install option.
• When UGCX is running, the voice command: "YOU ARE CLEARED TO DISCONNECT AND GO TO HAND SIGNALS" will now trigger properly and the mode will advance to the next mode as per the manual.

Version 4.0

Release Date: 21 April 2020

• TCAS switch in Button Control fixed.  During runway entry procedure, "TA" should now appear on the ND.

Version 3.9

Release Date: 5 April 2020

• Big change!  In Voice Control only, the NEW PROCEDURE is to call for the Before Start Checklist to the Line, then run then Before Start Procedure, and then call for the Before Start Checklist below the line.
• The FO's "I'm out for the walkaround" audio will no longer trigger during shutdown flow in the A330 model.
• Flight Director voice command updated.
• ADIRS voice command fixed.
• During descent, the FO will set his ND range to 10NM instead of 80.
• Support for ALT OFF on the TCAS Panel in the 330 model.
• FO will set 2000 in transponder during his shutdown flow.
• During his runway line up flow, the FO will no longer automatically set terrain on the Captain's side in the A330.
• Weather radar logic updated.
• FO will now set Predictive Windsheer on/off when entering and vacating the runway.

Version 3.8

Release Date: 20 March 2020

• Fuel Pumps Off in A330 models fixed for the shutdown flow.
• Flight Director voice command now triggers both FD's to be off / on.
• If performing a Flaps 3 landing in the A330, GPWS Landing Flap 3 no longer selected.
• Pack controls updated for the A330.
• FO's now selects his Chrono On when announcing "Takeoff", and Off during his after landing flow.
• If using Voice Control, your Speech recognizer can now be set to ENGLISH - US, UK, AU, CA or IN.
• Pax boarding sound no longer plays in the 330 model because you can't hear it from the cockpit.  
• Glide slope deviation call out triggers loosened,
• FO's will now adjust his ND range at 10,000 feet and when reaching cruise.
• During the 10,000 climb flow, the FO will select Airport on his side.  He will select CSTR during his pre-flight flow, and re-select CSTR on his side during his 10,000 feet descent flow.
• During the runway entry flow, the FO will now select Terrain on his side and select Weather Radar on.  He will turn off weather radar during his after landing flow.
• You can now say just "Below the line" instead of "XXX below the line" in Voice Control.
• You can now call the FA by pressing the FWD FA button on the overhead in the 330.
• In A330 models, door knocking sound removed when FA brings food/drinks.
• 1000 foot call during the approach now references the Radio Altimeter.
• Now you can "left click" the audio test button to reset audio system if your FS2Crew audio ever drops.
• TO trim setting refined, but it will never be 100 percent accurate.
   

Today was my first flight with the new update, everything went fine until I landed … After I landed and the FO did his checks there was a new message in the ECAM saying T/O speeds not set … When i parked up at the stand after a few mins i had all these warnings going off and could not turn them off  … i will get a screenshot next time, ... I did another flight without FS2CREw and had none of these errors... any chance i can revert to 4.1 at all please?

Quick question,im sure if i wasnt dreaming that the FO used to press the TO config button

when completing the checklist,i cant remember having to do that myself but now i have to.

Airbus A318/319/320/321 PRO it happens on all of them.Using button control,i stand to be corrected

if im wrong.

With Thanks

Gary Jones.

A quick question.

Is it possible to adjust the Pre-Flight time from 30mins to a longer time? I know shorter is possible.

I could have sworn on start up of the main panel I have seen T+45 but that quickly reverted to T+30mins.

Thanks

Mark

I had something weird happen to my FS2Crew v4.1 

Everything working OK for months, but elected to accept the latest Aerosoft update 1.4.2.0 today which released last week.

When I jumped in the cockpit I found key "N" would no longer bring up the main FS2Crew panel.  I checked the A3xx Configurator and Voice Control was enabled.

Tried key reassignment to "N". No joy.

Uninstalled and re-installed FS2Crew. Same problem . No main panel.

Looked into Panel.cfg and found FS2Crew entries missing.

So I have added them in manually. And now everything works with the "N" key.

So I am not sure what is going on.

On further investigation I suspect FS2Crew updated my pre-existing P3Dv4 panel cfg not the v5 version of panel.cfg based on the date/time stamp of when I ran the FS2Crew installer today.

I definitely selected the P3Dv5 install path for FS2Crew not the P3Dv4 path and this is evidenced by the FS2Crew Uninstaller being located in the v5 main sim folder. dated today.

So I  can not explain why panel.cfg is not being updated with the FS2Crew entries now in P3Dv5.

My set up is as follows:

Drive 😧 Aerosoft A320 installed in P3Dv4 which is in the Aerosoft  subfolder of the main v4 sim folder. All panel.cfg files show todays date of the re-install.

Drive G: For P3Dv5, my set up is a little different. I have moved the Aerosoft A320/321out of the main sim folder and into a separate Addons folder I created. Panel.cfg shows date of Dec 2020 for other A320/A321 variants .

From what I can see the FS2Crew installer is editing the wrong panel.cfg in the wrong sim when 2 installations of P3D are detected.

Was able to reproduce the same issue and by running FS2Crew installer for v4.1 the P3Dv4 folders are being updated, not v5.

Note: I did not select to update my FS2Crew for P3dv4 this time. Also my Aerosoft A320/A321 for P3Dv4 I did not update either. The installed version is 1.4.1.1

Any thoughts on why the panel.cfg for v4 is being updated , not v5? I have some screenshots Ic an share with you of the installer that indicates I am performing an install into P3Dv5.

Thanks

Mark

Got one small problem, when i descend past 10000 feet the FO will switch on the landings lights as he normally would, you can see on the top panel that he has moved the landing lights switch to the on position, however if i go to external view the lights aren't actually on, but if i re toggle the switch myself then they come on.

I'm using p3dv4 hf3.

latest aerosoft a330 update.

latest fs2crew update.

Thanks.

See this post!

Any ideas on how to remedy?

Thanks.

I hope someone can help. 

Thanks.

Thanks

Rich

The one that I keep noticing is that the FO seems unable to extend/retract their tray reliably. I notice this especially prior to takeoff. As we do Before Takeoff Checklist below the line, he tries to push the tray back in, and it moves slightly but then gets stuck and the sound of it retracting loops continuously until I click it myself, whereby it retracts normally. Then, after takeoff at 10,000', the FO tries to pull it back out and the same thing happens. It doesn't move, but the sounds starts playing continuously until I click it myself and then it pops out just fine. He seems able to move it at other times without issue.

This never happens in the 320 series. That series works flawlessly (that I can see).

Thanks for the continued support.

Thanks

Rich

I have run into a small problem here with my Sim PD3v4.5 while using the A330 MCDU Checklist Flow & FS2 Crew. It was noticed that while using the A330's MCDU Checklist Flow and the FS2 Crew panel been active it's causing some type of interruption that affects the MCDU Checklist Flow smoothly. I normally use the FS2 Crew not fully through for voice command only for the "Pre-Flight Event Count Down" and the "Clear Left" options since the Aerosoft products checklist call outs are included and must be used to advance any actions through any flights. What's taking place here its that while using FS2 Crew the A330 MCDU first Checklist call out "Cockpit Preparation Checklist" it only reaches the second item and quicks working totally. I have tested with both options (FS2 Crew active and inactive) that was the outcome noticed. While FS2 Crew was inactive the A330 CL Flow worked perfectly. After consulting for a few days with the Techs at the Aerosoft Forum in that regards and provided me a few instructions to isolate the problem,they have advise me to seek assistance with FS2 Crew techs and see if this problem has been reported previously. Any thoughts please?

Regards,

Fernando R.

my F/O frequently leaves the A330 flight deck hastily when arriving at a gate or stand immediately after finishing the parking checklist. He pretends to "go out for a walkaround".

Honestly I don't really trust him anymore as I am pretty sure he is just blowing a kiss to the pax sitting on 1C. Every time he returns to the flight deck literally less than 2-3 seconds later, he is happily announcing "I am back from the walkaround - everything looks good"  as though nothing had happend. 

Maybe one should teach him to leave the flight deck only  after asking for permission to go for a walkaround and maybe one should teach him to do the walkaround on the second leg as diligent as he does before the first leg of the day, too. 

Best regards, Björn 

Small issue, but still.

//Jonas

Protokollname: Application
Quelle:        Application Error
Datum:         03.02.2020 11:30:21
Ereignis-ID:   1000
Aufgabenkategorie:(100)
Ebene:         Fehler
Schlüsselwörter:Klassisch
Benutzer:      Nicht zutreffend
Computer:      XXXXXX
Beschreibung:
Name der fehlerhaften Anwendung: Prepar3D.exe, Version: 4.5.13.32097, Zeitstempel: 0x5d8abf93
Name des fehlerhaften Moduls: FS2CrewAirbusButton.gau_unloaded, Version: 1.0.0.86, Zeitstempel: 0x5e181f55
Ausnahmecode: 0xc0000005
Fehleroffset: 0x0000000000033e0b
ID des fehlerhaften Prozesses: 0x21a0
Startzeit der fehlerhaften Anwendung: 0x01d5da6d5b099986
Pfad der fehlerhaften Anwendung: C:\Prepar3D v4\Prepar3D.exe
Pfad des fehlerhaften Moduls: FS2CrewAirbusButton.gau
Berichtskennung: fb951c13-eb37-49fc-9fcb-04df3362aa2b
Vollständiger Name des fehlerhaften Pakets:
Anwendungs-ID, die relativ zum fehlerhaften Paket ist:
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2020-02-03T10:30:21.098605900Z" />
    <EventRecordID>7233</EventRecordID>
    <Channel>Application</Channel>
    <Computer>XXXXXXX</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Prepar3D.exe</Data>
    <Data>4.5.13.32097</Data>
    <Data>5d8abf93</Data>
    <Data>FS2CrewAirbusButton.gau_unloaded</Data>
    <Data>1.0.0.86</Data>
    <Data>5e181f55</Data>
    <Data>c0000005</Data>
    <Data>0000000000033e0b</Data>
    <Data>21a0</Data>
    <Data>01d5da6d5b099986</Data>
    <Data>C:\Prepar3D v4\Prepar3D.exe</Data>
    <Data>FS2CrewAirbusButton.gau</Data>
    <Data>fb951c13-eb37-49fc-9fcb-04df3362aa2b</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

The FO will set flaps 1 and 2 when requested, but will not set flaps 3 or full when either:

• loading mid-flight from a save file (and then cycling forward to the appropriate flow)
• attempting a 2nd approach after a go-around (and cycling forward to the "landing" flow)

Everything has always worked perfectly for the initial landing attempt.  Also, the green bar shows that the system is "hearing" the commands.  This only seems to happen on subsequent landing attempts.  It's as if the FS2Crew system gets reset and recognition of those commands is dependent on some action that's not being performed because its flow is being skipped.

Looking for some guidance on the following.

Just updated FS2Crew to v3.5  in P3Dv4 today and loaded the Airbus A320 Professional aircraft. Audio is working fine except when running the Speaker test, I did not hear any differentiation between left and right headphones.

Both left and right audio test appears to come from both left and right headphone channels at same time.

The Airbus Configurator is set to my Headphones source and I have Voice set to ON, DSP set to ON, LK set to ON and HS set to ON in the config panel.

Any thoughts?

BTW: I loaded the PMDG 747 QOTSII and ran the FS2Crew Speaker test there and I do hear correct differentiation between left and right channels, so it appears my general headphone set up and functionality are OK.

Any thoughts?

Regards

Mark