Goofy
Members-
Posts
111 -
Joined
-
Last visited
-
Days Won
8
Content Type
Profiles
Forums
Latest X-Plane & Community News
Events
Downloads
Store
Everything posted by Goofy
-
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
-
checklsit Dynamic checklist for the BN-2B Islander - X-Plane 12 version
Goofy replied to Goofy's topic in BN-2B Piston Islander
New version of the dynamic checklist: v2.1 The changes are on the download page. Please use the download link in the first post to download the new version. -
Test of lights of the panel notification lights issue
Goofy replied to stavka's topic in BN-2B Piston Islander
Same here for the BN-2B. -
With the G500 coupled to the GNS 430/530 you follow your flight on the G500 (SID / NAV / STAR) and you finish for the approach with the GNS 430/530, whatever the type of approach, it works (ILS / RNAV / VOR APP/ ...)
-
@flightyler This is normal. Read the documentation supplied with the Garmin G500: SIDs and STARs are displayed, but approaches are not processed (the management of approaches by Laminar is different from the management of SIDs, NAVs and STARs, which have waypoint paths).
-
I don't know why, but I often fly this MU-2 Marquise. I think I know why
-
In real life, these two levers are used to lock the controls in their current positions. In this simulation, these two levers are animated, but have no effect.
-
The percentage calculations are incorrect For example: "Expected climb distance = 21", "Actual climb distance = 19". The difference is not 90.48%, but 15.79%: (21-19)/21*100 = 15.789...%. Similarly for "Expected time = 7" and "Actual time = 7", the difference is 0%, not 100% : (7-7)/7*100 = 0% And so on. Or you give a different meaning to the "Diff" value...
-
livery Small graphic omissions on the C-FRWK livery
Goofy posted a topic in Mitsubishi Marquise MU-2 v2
Hello A few small graphic omissions on the C-FRWK livery: - the Pitot Covers are black and should be red - the Nosewheel Chocks are black and should be yellow and black Unlike the other liveries, these areas are not coloured in the "Exterior_4_ALB.png" file for livery C-FRWK. ----------------- I've corrected this file on my computer, it's look fine now : -
-
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
-
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
-
Hello With the MU-2 G500 version, we cannot enter the DH on the G500 3D, while we can do it on the G500 2D. We cannot press the right knob on the G500 3D to enter the edit mode.
-
For the -1- see here:
-
TOGA Simulation MU-2 Marquise v2.1.0 Update Released!
Goofy replied to Cameron's topic in Mitsubishi Marquise MU-2 v2
Do you have an assignment or keyboard shortcut to the "Toggle both levers to/from emer stop" function of the levers conditions? I had such an assignment that prevented starting the engines, even if I didn't use this function. I removed this assignment and I was able to start the engines. -
Okay, I've figured out how it works. The RUN/CRANK/STOP switches must be first in the down position for this click zone to be active.
-
Ok, thank you. I will look for that