Jump to content

Dynamic checklist (clist.txt) for the MU-2 Marquise (v2.1.0 or later) for X-Plane 12

Recommended Posts

Hello   :)

I propose you a dynamic checklist for this superb MU-2 Marquise V2.1.0 (or later) by TOGA simulation, for X-Plane 12.
This script is to be used with the Sparker's Xchecklist v1.50 plugin or later (for X-Plane 12).
I used the datarefs to the maximum in order to automate and make more user-friendly the use of this checklist.

You can download this checklist here :

Good use  :)


Link to comment
Share on other sites

Hi, @Goofy

I am really surprised! :o
Just yesterday I published the update of the checklist that I did a few months ago, as you can see: 

Maybe you didn't realize it or maybe your checklist is much better than mine and you've decided to publish yours for the good of the community.
Or perhaps simply, you had been doing it for a long time and you did not want so much work to be wasted. :)
In any case, it would have been desirable if you had contacted me to reach an agreement and thus one of the two of us would have saved a few hours of dedication.
Anyway, you are the teacher and I am the student, so I will try your checklist and use the one that seems best to me.
I encourage others to do so. Competition is always good, right?

Link to comment
Share on other sites

Posted (edited)

Hello @MANOLO  :)
When I use a new aircraft, I always do its dynamic checklist. It's a good way for me to explore the features offered by an aircraft and also to learn how to use it properly. I could of course reuse checklists already made by other members (like your good checklist), but this would be a "passive" discovery of a new aircraft for me.
When my dynamic checklists are done, I find it useful and friendly to share them, even if other checklists exist. It offers choice and everyone can choose according to their desires   :)

No competion for me   ;)

Edited by Goofy
Link to comment
Share on other sites

Hi, @Goofy and all,

I have been using and reviewing your checklist and you have obviously proven to be the best specialist doing this type of checklist, my congratulations. It's something I already knew... :)
Allow me now to specify some aspects that improve my previous checklist:

- ATC call reminders are included
- Specifies that the battery test should be done before/without connecting the GPU
- The mention of the Panel Light test is included
- The HSI (Att Button) test is also included, which I had not discovered existed
- The SRL test is included
- The need for FSB and No Smoke notices is indicated
- The autopilot test is included in STBY
- Remember the possibility of putting on headphones, which is very practical if you get tired of so much noise... :D
- The procedure to use Continuous Ignition that you have applied is for me the correct one and the one that is used in other similar planes, although it is not the one described in the POH.
- The cabin pressure check and adjustment is better than the one described in the POH, again.

But above all, above all, the aesthetics, readability and the order of your checklist is very good and pleasant, just as you are used to.

Well, after so many praises, in my next communication will come the "failures" and suggestions. ;)

  • Upvote 1
Link to comment
Share on other sites

Posted (edited)

Hi and thank you @MANOLO  :)

In the checklists, I'm trying to make it more ergonomic. Don't go off in all directions on the cockpit, but follow a more logical sequence (itinerary) of actions, easier to remember.

I have another version not yet published.

You can add in my dynamic checklist:
- Preflight" checklist, just before the cockpit panel light test, you can add the overhead panel light switch test (there is a dedicated switch for this on the OVH):

Note: some dataref linked to light switches are not necessarily set to "1" when they are active. If they are ON during the day, they take the value "1", but at night some light switches take a value greater than "0", but less than "1" (about 0.3...) when they are set to ON at night. This is why the DRF test is performed on a value ">0" and not "=1" to test whether the switch has been activated. This way it will always work day and night.

sw_item_c:\green\Overhead panel IND LT TEST switch|\yellow\TEST:xscenery/mu2b60/manips/overhead_ind_lts_test_button:>0


- In the "Before Taxi" checklist: add the altimeter setting for the pilot and co-pilot (QNH). Major omission on my part:

sw_item_c:\green\Pilot altimeter|\yellow\SET QNH:sim/cockpit2/gauges/actuators/barometer_setting_in_hg_pilot:><0.001
sw_item_c:\green\Copilot altimeter knob|\yellow\SET QNH:sim/cockpit2/gauges/actuators/barometer_setting_in_hg_copilot:><0.001

- When the aircraft is flying at high altitude, the inside/outside PSI DIFF is not 6.0 PSI, but 6.1 PSI max. So you need to correct the value of the corresponding dataref to 6.15 in the "Climb" and "Cruise" checklists, otherwise the two checklist points may not be validated automatically if you're flying at high altitude:

sw_item_c:\green\Pressurization DIFF PSI|\yellow\CHECK < 6 PSI:sim/cockpit2/pressurization/indicators/pressure_diffential_psi:<6.15


Nice aircraft, very pleasant to use. Thanks to the author   :wub:

Edited by Goofy
Link to comment
Share on other sites

Hi, @Goofy and all,

The overhead lights test had also gone unnoticed by me, so thanks again.
Yes, I had realized the need to adjust altimeters before takeoff and the pressure difference <6.0 Psi, but I ignored it until now by increasing the cabin pressure altitude, it's better that way.;)

As I explained in my previous email, I have carried out a detailed review and I indicate below the corrections that I would make to your checklist and some observations.

- Max and Econ Speeds must be expressed in KTAS and not in KIAS.

- Pilot Communications Door, it is a small window on the pilot's side that is perfectly simulated in this plane and is worth use it. It opens before starting engines.
sw_item: Pilot Communication Door|OPEN:xscenery/mu2b60/manips/ticket_door_toggle:1
- Power Levers must be in the Ground zone, the margin you have set is too narrow and must be widened.
sw_item: Power levers|BOTH GROUND IDLE:(xscenery/mu2b60/anim/left_power_lever_position:0.30|0.45)&&(xscenery/mu2b60/anim/right_power_lever_position:0.30|0.45)
- The check of free movement of the Yoke and pedals would be better if it was done with all the axes and not just with any one.
sw_item: Yoke Roll Control|FREE MOVEMENT:(xscenery/mu2b60/anim/yoke_roll_ratio:1)||(xscenery/mu2b60/anim/yoke_roll_ratio:-1)
sw_item: Yoke Pitch Control|FREE MOVEMENT:(xscenery/mu2b60/anim/yoke_pitch_ratio:1)||(xscenery/mu2b60/anim/yoke_pitch_ratio:-1)
sw_item: Rudder Control|FREE MOVEMENT:(sim/flightmodel2/wing/rudder1_deg[10]:<-10)||(sim/flightmodel2/wing/rudder1_deg[10]:>10)

-Roll Trim. Traditionally, since its first version in 2009, this aircraft showed a very pronounced tendency to turn to the right, it was a very typical characteristic of this model. In this version in XP12 this effect is not as pronounced but it is still noticeable and a slight trim to the left is convenient.
sw_item: Roll Trim Set|Takeoff 1/8 LEFT:sim/flightmodel/controls/ail_trim:-0.15|-0.1

- Before starting the motors, it is necessary to check that they are ON LOCKS and only if they are not, the Unfeathered procedure is used. A remark like this would be helpful:
sw_item: Propellers|ON LOCKS
sw_itemvoid: **NOTE**|If the propeller is feathered, place the Power Lever in REVERSE
sw_itemvoid: **|and hold the Unfeather Switch until the blades reach the lock position.

- The ignition process is so beautiful that it is worth detailing it better, checking when the Starter light should turn on and off, if the SRL Fail warning disappears or if the RPM that is achieved is adequate. With these sentences you achieve all that:
sw_item: Ignition and EGT Rise|RELEASE ENGINE START SWITCH:(sim/flightmodel2/engines/EGT_deg_C[1]:>200)&&(xscenery/mu2b60/annuns/rh_starter_button:1)
sw_item: SRL FAIL Annunciator|EXTINGUISHES ABOVE 14% RPM:xscenery/mu2b60/annuns/r_srl_fail:0
sw_item: Exhaust Gas Temperature|MONITOR
sw_itemvoid: **NOTE**|If EGT approaches 770º, position Condition Lever to Emergency Stop
sw_item: Engine Start Indicator Light|EXTINGUISHES AT 60% RPM:xscenery/mu2b60/annuns/rh_starter_button:0
sw_item: Engine RPM|STABILIZE AT ABOUT 76.5 TO 78.5%:xscenery/mu2b60/engine/eng2_percent_rpm_needle:76.5|78.5

- Before taxi, we can close the communications window.
sw_item: Pilot Communication Door|CLOSED:xscenery/mu2b60/manips/ticket_door_toggle:0

- Windshield Heat. I would include it as mandatory, even if it's not very cold, a fogging of the glass is very typical when it undergoes rapid cooling during the initial climbing.
sw_item: Windshield Heat|LOW:(xscenery/mu2b60/anim/left_windshield_heat_switch:1)&&(xscenery/mu2b60/anim/right_windshield_heat_switch:1)

- I would include this information as a reference for climbing:
sw_itemvoid: Optimum Airspeed| TO 10000 FT - 155 KIA
sw_itemvoid: Optimum Airspeed| TO 15000 FT - 150 KIA
sw_itemvoid: Optimum Airspeed| TO 20000 FT - 145 KIA
sw_itemvoid: Optimum Airspeed| TO 25000 FT - 140 KIA
sw_itemvoid: Optimum Airspeed| TO 30000 FT - 135 KIA

- Important not to forget to reset the Roll Trim to zero if we don't want to fly sideways... :D
sw_item: Roll Trim|SET TO NEUTRAL:sim/flightmodel/controls/ail_trim:0

- A check to verify that there is not a great pressure difference in the cabin when starting the final approach. It is always possible that on steep descents the pressurization system does not have time to reach the Airport pressure. This 1.5 PSI value roughly corresponds to a 3000 ft altitude difference which is somewhat tolerable.
sw_item: Cabin Differential Pressure|CHECK NEAR TO ZERO:sim/cockpit/pressure/cabin_pressure_differential_psi:<1.5

- In the original POH it is recommended not to use Flaps 40 if it is not necessary, especially in conditions of moderate wind and/or risk of icing. Perhaps this caveat would be worth it:
sw_itemvoid: **NOTE**|Use 40° Flaps only if necessary and always below 120 KIAS
-Power. Again, a little more headroom in the GROUND position is helpful.
sw_item: Power|GROUND IDLE:(xscenery/mu2b60/anim/left_power_lever_position:0.30|0.45)&&(xscenery/mu2b60/anim/right_power_lever_position:0.30|0.45)

- I think this Beta Range check and Reverse warning would come in handy:
sw_item: BETA RANGE Annunciators|Illuminated:(xscenery/mu2b60/annuns/lh_beta_range:1)&&(xscenery/mu2b60/annuns/rh_beta_range:1)
sw_itemvoid: **NOTE**|REVERSE if required,
sw_itemvoid: **|then back to GROUND IDLE position

- Stop Engines must be correctly checked and hold until the RPM drops below 50%, according to the POH
sw_item: Run Crank Stop Switch Right|STOP AND HOLD UNTIL 50% RPM:xscenery/mu2b60/manips/R_run_crank_stop_switch:0
sw_item: Run Crank Stop Switch Left|STOP AND HOLD UNTIL 50% RPM:xscenery/mu2b60/manips/L_run_crank_stop_switch:0

- Ignition Switches. You have a small error here in the text that it should be OFF instead of AUTO, however the dataref is fine.


I have included all these suggestions in your checklist together with the additions that you have mentioned above, and I will send you the clist.txt privately for you to evaluate and, if you agree, include them in your next update, which I will appreciate, because you will also make them look better.
You will be able to easily see the modifications that I have made because they are without color, that is, with the default color of the xchecklist.
I await your comments. :)


Link to comment
Share on other sites

Good comments and good suggestions. Thank you @MANOLO   :)
I've changed the presentation of your suggestions so that they fit in well graphically in the checklist and sometimes the sequencing of the actions so that it's a more logical path of actions.
For the controls test, don't test down to values -1 and 1, some users have badly calibrated josyticks or have modified the response curves. They don't reach -1 or +1. A test limited to -0.7 and 0.7 seems more flexible for me.
Version v1.2 of the dynamic checklist.
MANOLO's suggestions are incorporated into the checklist
The changes are indicated on the download page (on the .org).
=> To download this new version, please go to the initial post.

Good flights  :)

Link to comment
Share on other sites

Hi, :)

Fantastic! It has been perfect once again!
I appreciate your collaborative attitude.
The modification in the controls test seems optimal to me too.

I hope that the pilots know how to appreciate this work and benefit from a well-done checklist. In my opinion, following a good checklist is the best way to learn to fly an airplane and to get the most out of it. Of course, this plane deserves it because it is full of great details, it is a marvel.


  • Upvote 1
Link to comment
Share on other sites

In this version 1.2 of the dynamic checklist there is a small dataref condition bug in the aileron trim setting for take-off. This has now been corrected and you can download the checklist again.

This dynamic checklist remains in v1.2   :)

  • Upvote 1
Link to comment
Share on other sites

6 hours ago, MANOLO said:

Of course, this plane deserves it because it is full of great details, it is a marvel.

Thanks for the kind words Manolo,  I'll keep working to improve it, I can still think of lots of cool things to do.  It will probably always be a work in progress.

Thanks all for the Xchecklist work..I haven't used it before, but will have to check it out, it looks quite handy.


Edited by tkyler
  • Upvote 1
Link to comment
Share on other sites

  • 3 weeks later...
  • 4 weeks later...
5 hours ago, Goofy said:

Version v1.5 of the dynamic checklist.
The changes are indicated on the download page (on the .org).
=> To download this new version, please go to the initial post.

Good flights  :)

Awesome, thanks.  Just wondering the clist.txt file is still dated 22/05/2023.

Link to comment
Share on other sites

On 7/13/2023 at 10:08 AM, Goofy said:

The date of the "clist.txt" v1.5 file is 12/07/2023.
Download the new file and check it.

I'm sorry but see attached image.  The clist.txt file is dated 22/05/2023 however, it is a great detailed checklist and works great.


Screenshot (640).jpg

Edited by fleurenf
Added text
Link to comment
Share on other sites

When you display the "INITIAL" page of the checklist (the first page), what version number is displayed in the title bar of the Xchecklist window?
If you have the correct version, you should read "-o- CHECKLIST - v1.5 XP12 - -o-".

I've just had another look at the checklist file available for download: this is v1.5 and the "clist.txt" file is dated 12/07/2023  ;)

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...