Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Anyone using Toliss A340

Featured Replies

  • 4 weeks later...

I will be later on tonight - should the standard airbus commands work with it?

(i.e. Push heading select etc...)

James W

 

Banner_FS2Crew_Supporter.jpg

  • Author
  • Commercial Member
53 minutes ago, severniae said:

I will be later on tonight - should the standard airbus commands work with it?

(i.e. Push heading select etc...)

They should, assuming MCE for X-Plane detects the plane as Toliss Airbus, hence my question, we don't have a copy of the plane yet.

A dll named "xmcTolA3X.dll" should handle Toliss A319, A320, A321 and since they also share cockpit switches with A340. the expectation is that there should be no need for a new dllm maybe just an update to "xpmce.exe" to recognize the new plane properly. Thanks

 

 

No problem Gerald, I will test and let you know.

 

I presume I'll need to create my own F/O flows and checklists?

 

 

 

James W

 

Banner_FS2Crew_Supporter.jpg

  • Author
  • Commercial Member
2 hours ago, severniae said:

No problem Gerald, I will test and let you know.

 

I presume I'll need to create my own F/O flows and checklists?

 

 

 

I see, Fuel,  Elec and Hydraulic panels are different, therefore, will need its own folder which doesn't exist right now,.as well as ad-hoc speech commands

The 330 is covered, both JAR A330 & RWD A330, but the A340 is a first.

For now, set "Debug=1" in xpmce.ini and report what information MCE is gathering from the plane. Author, type etc (should see a dialog box).

We'll do a quick update to make sure it's recognized and all Airbus related commands are accepted to get you going quickly.

Also report the aircraft ".acf" file name, I mean "whatever_name_they_gave_it.acf"

Then, we'll probably need a copy to work it out fully.

Thanks

 

 

Hi Gerald,

Indeed, the standard Airbus commands don't work. It also seems like he doesn't set Packs etc... so I guess it'll need the usual MCE magic applying to make it all compatible - always greatly appreciated!

Here is the image:

7Ey8de7.jpg

See file names below - note that there is a standard and normal def version - I used the normal def one (circled)

spacer.png

Happy to test anything you send my way.

Edited by severniae

James W

 

Banner_FS2Crew_Supporter.jpg

  • Author
  • Commercial Member
55 minutes ago, severniae said:

Hi Gerald,

Indeed, the standard Airbus commands don't work. It also seems like he doesn't set Packs etc... so I guess it'll need the usual MCE magic applying to make it all compatible - always greatly appreciated!

Here is the image:

7Ey8de7.jpg

See file names below - note that there is a standard and normal def version - I used the normal def one (circled)

spacer.png

Happy to test anything you send my way.

Thanks.

Right now, it would see the aircraft as an unsupported default plane and won't enable Airbus specific commands such as "pull speed knob", "birdie on" and "xmcgener.dll" is loaded in the sim instead of the required "xmcTolA3X.dll" for Tolisss planes.

Once he knows it's an Airbus from Toliss he should perform better. Only then will we find out the level of control he has on switches and dials.

@FS++

It may not be any use to you, but in case - I just created this, using the official A340 Normal Checklist as reference:

 

If you need any documents, I have the Airbus FCTM, FCOM and QRH handy...


___________________________________________
BEFORE START

[ ]Cockpit Preparation    --    Completed //3
[ ]Gear Pins and Covers -- Removed
[ ]Signs    --    Auto
[ ]A D I R S    -- Nav
[ ]Fuel Quantity    --    Checked
[ ]Takeoff Data        --    Inserted
[ ]Barometer reference    --    Set

___________________________________________
BEFORE START BELOW THE LINE

[ ]Windows and Doors    --    Closed
[ ]Beacon        --    On
[ ]Thrust Levers    --    Idle
[ ]Parking Brake    --    Set

___________________________________________
AFTER START

[ ]Anti Ice        --    As Required
[ ]ECAM Status        --    Checked
[ ]Trim        --    Set


___________________________________________
BEFORE TAKEOFF

[ ]Flight Controls    --    Checked
[ ]Flight Instruments    -- Checked
[ ]Briefing    --    Confirmed
[ ]Flaps        --    Set takeoff flaps //2
[ ]Takeoff Speeds    --    Set
[ ]Autobrake        --    Max
[ ]Signs        --    On //2
[ ]Spoilers        --    arm //2
[ ]Ecam Memo        --    Takeoff no blue //3

___________________________________________
BEFORE TAKE OFF BELOW THE LINE

[ ]Takeoff runway    --    Confirmed
[ ]Packs        --    As Required

___________________________________________
AFTER TAKEOFF CLIMB

[ ]Landing gear        --    Up //2
[ ]Flaps        --    Retracted //2
[ ]Packs        --    On

___________________________________________
AFTER TAKEOFF CLIMB BELOW THE LINE

[ ]Barometer reference    --    Set

___________________________________________
APPROACH

[ ]Breifing    --    Confirmed
[ ]ECAM Status        --    Checked
[ ]Seatbelt Signs    --    On
[ ]Minimums        --    Set //3
[ ]Barometer reference    --    Set
___________________________________________
LANDING

[ ]Autothrottle        --    As Required
[ ]Ecam Memo        --    landing no blue //3
[ ]Signs    --    On
[ ]Landing gear        --    Down //2
[ ]Spoilers        --    armed //2
[ ]Flaps        --    Set
[ ]Cabin    - Ready

___________________________________________
PARKING

[ ]APU bleed        --    On
[ ]Engines    -- Off
[ ]Radar and P W S        --    On
[ ]Seatbelt Signs    --    On
[ ]Exterior Lights    --    As Required
[ ]Fuel Pumps        --    Off
[ ]Parking Brake Chocks    --    As Required

___________________________________________
SECURING THE AIRCRAFT

[ ]TCAS        -- Off
[ ]A D I R S        --    Off
[ ]Oxygen        --    Off
[ ]APU bleed        --    Off
[ ]Emergency Exit Lights --    Off
[ ]No Smoking        --    Off
[ ]Seat belt sign    --    Off
[ ]APU            --    Off
[ ]Batteries        --    Off

James W

 

Banner_FS2Crew_Supporter.jpg

  • Author
  • Commercial Member
19 hours ago, severniae said:

@FS++

It may not be any use to you, but in case - I just created this, using the official A340 Normal Checklist as reference:

 

If you need any documents, I have the Airbus FCTM, FCOM and QRH handy...


___________________________________________
BEFORE START

[ ]Cockpit Preparation    --    Completed //3
[ ]Gear Pins and Covers -- Removed
[ ]Signs    --    Auto
[ ]A D I R S    -- Nav
[ ]Fuel Quantity    --    Checked
[ ]Takeoff Data        --    Inserted
[ ]Barometer reference    --    Set

___________________________________________
BEFORE START BELOW THE LINE

[ ]Windows and Doors    --    Closed
[ ]Beacon        --    On
[ ]Thrust Levers    --    Idle
[ ]Parking Brake    --    Set

___________________________________________
AFTER START

[ ]Anti Ice        --    As Required
[ ]ECAM Status        --    Checked
[ ]Trim        --    Set


___________________________________________
BEFORE TAKEOFF

[ ]Flight Controls    --    Checked
[ ]Flight Instruments    -- Checked
[ ]Briefing    --    Confirmed
[ ]Flaps        --    Set takeoff flaps //2
[ ]Takeoff Speeds    --    Set
[ ]Autobrake        --    Max
[ ]Signs        --    On //2
[ ]Spoilers        --    arm //2
[ ]Ecam Memo        --    Takeoff no blue //3

___________________________________________
BEFORE TAKE OFF BELOW THE LINE

[ ]Takeoff runway    --    Confirmed
[ ]Packs        --    As Required

___________________________________________
AFTER TAKEOFF CLIMB

[ ]Landing gear        --    Up //2
[ ]Flaps        --    Retracted //2
[ ]Packs        --    On

___________________________________________
AFTER TAKEOFF CLIMB BELOW THE LINE

[ ]Barometer reference    --    Set

___________________________________________
APPROACH

[ ]Breifing    --    Confirmed
[ ]ECAM Status        --    Checked
[ ]Seatbelt Signs    --    On
[ ]Minimums        --    Set //3
[ ]Barometer reference    --    Set
___________________________________________
LANDING

[ ]Autothrottle        --    As Required
[ ]Ecam Memo        --    landing no blue //3
[ ]Signs    --    On
[ ]Landing gear        --    Down //2
[ ]Spoilers        --    armed //2
[ ]Flaps        --    Set
[ ]Cabin    - Ready

___________________________________________
PARKING

[ ]APU bleed        --    On
[ ]Engines    -- Off
[ ]Radar and P W S        --    On
[ ]Seatbelt Signs    --    On
[ ]Exterior Lights    --    As Required
[ ]Fuel Pumps        --    Off
[ ]Parking Brake Chocks    --    As Required

___________________________________________
SECURING THE AIRCRAFT

[ ]TCAS        -- Off
[ ]A D I R S        --    Off
[ ]Oxygen        --    Off
[ ]APU bleed        --    Off
[ ]Emergency Exit Lights --    Off
[ ]No Smoking        --    Off
[ ]Seat belt sign    --    Off
[ ]APU            --    Off
[ ]Batteries        --    Off

Get new patch

For now, Fo will see it as an A320.

Manually add/replace files as per folder structure.

Add folder <a340> to \My Documents\Multi Crew Experience\Myvoicescripts\Copilot\Aircraft\ folder

Suggested checklist above will be default. Thanks

Feel free to build more ad-hoc flows, inluding suggestions for upcoming trigger commands to handle items that FO has yet to be trained on for A340

 

Thanks Gerald, I will try it later tonight.

Regarding the flows & procedures, the format of them is largely the same as the a320 family, as Airbus tends to use very similar procedures across the fleet, obviously there will be changes for number of engines, fuel tanks etc...

 

I will try and get some time over the next few days to put some suggested flows together - time to dig into my FCOM!

 

James W

 

Banner_FS2Crew_Supporter.jpg

Hi Gerald,

Unfortunately the patch doesn't seem to make any difference, copied in the files twice to be sure, but it doesn't appear to be detecting the A340 properly - None of the Airbus specific commands appear to register, and I note that it didn't default to the provided checklist, rather defaulting to the generic airbus one..

Best,

James

James W

 

Banner_FS2Crew_Supporter.jpg

  • Author
  • Commercial Member
44 minutes ago, severniae said:

Hi Gerald,

Unfortunately the patch doesn't seem to make any difference, copied in the files twice to be sure, but it doesn't appear to be detecting the A340 properly - None of the Airbus specific commands appear to register, and I note that it didn't default to the provided checklist, rather defaulting to the generic airbus one..

Best,

James

Will double check. Most important file to replace, "xpmce.exe". Latest is V1.5.7.8 in the current patch

 

11 hours ago, FS++ said:

Will double check. Most important file to replace, "xpmce.exe". Latest is V1.5.7.8 in the current patch

 

Just checked the files in the patch - noted that the dll file contained was the 'xmcjarA3X.dll' - Would it not be the 'xmcTolA3X.dll' - I could be barking up the wrong tree! haha

James W

 

Banner_FS2Crew_Supporter.jpg

  • Author
  • Commercial Member
45 minutes ago, severniae said:

Just checked the files in the patch - noted that the dll file contained was the 'xmcjarA3X.dll' - Would it not be the 'xmcTolA3X.dll' - I could be barking up the wrong tree! haha

The "xmcJarA3X.dll" is intended for JAR A320 & A330.

Someone unrelated to this thead has reported an issue with those planes (via e-mail) following aircraft update, hence the need to update it.

The "xmcTolA3X.dll" cannot be blindly updated as one needs to work out the new elements that control say something like "apu battery". For that would need a copy of the plane. For now, we are banking on the fact it's very likely Toliss is using the same elements that control common switches in A320 in A340 as well. I mean taxi lights, FCU buttons and dials so that you can get that part going for now. Later when eveything is accounted for, FO will control almost every working switch on any panel at which point it will be deemed fully supported.

We found why the plane wasn't recognized. Turns out, this time Author changed from "Gliding Kiwi" (with space) to "GlidingKiwi" without space. That's right, a simple thing like that may cause MCE not to recognize the plane anymore, as you can't assume any A320 is from Toliss. There are many out there.

Waiting for colleague to update the file and will advise when it's ready for download.

 

Thanks Gerald, as usual, your customer support is A+.

I wish a few other devs would follow your example...

James W

 

Banner_FS2Crew_Supporter.jpg

Archived

This topic is now archived and is closed to further replies.

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.