JohnDikkson, as kengou1 and kaha300d already told, that is not a but. As in real plane, you should never fly with empty tanks.
Just a couple of gallons are enough to prevent the float from breaking.
1 Like
I had literally just finished hand writing my notes for this aircraft, including the engine and battery reset procedure and now you go change it! 
Thanks for all your effort. I look forward to your first payware aircraft 
1 Like
My manifest.json still says version 1.4, while other documentation says 1.5. Is that just an oversight?
Yes, as always I forgot to update manifest.json. The correct version is 1.5.
2 Likes
@kengou1 @kaha300d Thanks guys, I had indeed been flying with dry tanks so that must be the reason for the gauge failure.
@AlexBap8588 awesome to have failures like this, gives us a reason to look after the aircraft. Keep up the great work 
how do i navigate throught the different modes? By default is the fuel mode, I do not know how to access the other two!!!
Ok. I found it. Cheers.
Long press on ADD FUEL button. See manual p.31
@AlexBap8588 are there new āvarsā for mapping the new Miniflo-L features? (the long and short press buttons, and for the selector knob)
Man, the new flight model update is sure nice and smooth .
Do you publish your manuals anywhere besides within the zipped folder? I like looking at updated MSFS aircraft manuals as bedtime reading on my phone and didnāt know if there was an easier way than going through the whole OneDrive song and dance.
Thanks, your mastery when it comes to MSFS modding is better than anything I can think of thatās out there right now; this plane keeps getting better and it was a treat to begin with.
edit: forget it, just emailed the thing to myself and opened in a browser, all good - still getting used to this PC thing it feels like sometimes
Ha i did the same -e mailed it
Sorry, but at least for buttons there isnāt nothing for now. Iām not sure about the knob since I didnāt change the template, only its code.
Iām going to have a look and report back.
In real life we lined up with the runway and set the gyro with the compass , sometimes it was right on and other times we reset it . This one was the same but now the gyro above the auto pilot Iām sure I used to just hit the D key and it would set but now it doesnāt, not sure if I unset some thing , but any one else have this happening? I didnāt try the dc3 to see if itās the same cause it periodically did the same and hit the D key and all went to sync.
The D key resets the gyro drift. So, if the gyro didnāt drift much until you lined up with the runway for start you will not notice a change.
Or your Assistance settings got reset as happens sometimes?
Just downloaded the latest version. Has there been a change to the free-castering tailwheel?
I am lucky enough to have a great setup with rudder pedals and toe brakes (and a great throttle quadrant). I have noticed in the latest version that the free castering wheel seems to become uneffective at speed. As soon as you taxi above a certain speed, you can shove on a brake pedal to max, and the aircraft will still continue in a straight line. As soon as the speed bleeds off, it will suddenly turn.
This seems differnt to before, and is probably a little unrealistic.
Once more, thank you so much for this mod. It is amazing!
1 Like
Observations on the Behavior of the Beech 18 (MSFS 2020) Avionics as it Relates to RNAV (GPS) Approaches
Introduction
As I have been flying Beechcraft D18S (aka Twin Beech or Beech 18) in MSFS, I have noticed seemingly inconsistent and sometimes confusing behavior when using the GNS 530 during instrument approaches. To understand this better, I made several flights, systematically noting the behavior of the avionics and autopilot (AP) during different RNAV (GPS) approaches. The results are documented and summarized here ā mainly for my own benefit since I often forget details of an aircraft when learning to fly another one in MSFS. I also thought I would share this with the Beech 18 community as I have not found this documented anywhere else except for ILS approaches (see e.g. https://www.youtube.com/watch?v=Xlt6s7yYkks). I am not an instrument-rated pilot and am just starting to learn IFR in the sim, so some of my findings may be obvious to those more knowledgeable than me.
Please note the following:
-
All observations were made with the Denarq mod (v1.4) of the Carenado Beech D18S. I donāt know if the Denarq mod includes any changes to the avionics, but I have not seen anything suggesting that, so I suspect these observations would apply to the default Carenado plane as well.
-
There is a known bug with the AP not functioning properly in this plane plane (both original Carenado version and the Denarq mod) with the landing light on. I have found that turning the landing light on during approaches with the AP already on doesnāt seem to cause any problems.
-
There is a known bug with MSFS 2020 that when starting from a saved flight (loaded from a flt file), the avionics and AP donāt seem to behave properly. None of the observations presented here were made using a saved flight.
Observations
The table below shows what type of guidance (lateral or vertical) is shown on the HSI and VOR2, what type of control the AP can provide, and the approach mode shown on the GNS 530 for the various approach / minima types and availability of an ILS or Localizer. Also given are the specific instrument approaches used to develop the table. See the attached Figure 1 showing the avionics equipment referred to in the table.
The following points summarize the observations and consequent conclusions:
-
Lateral guidance is always shown on the HSI but vertical guidance or glidepath is not. The only exception to this is that when a Glideslope (GS) is available from an ILS tuned in on NAV1 (indicated by āILSā in the second column of the table), then the glidepath is shown on the HSI, no matter what the CDI mode on the GNS 530 is set to (either GPS or VLOC). This is the fifth line in the table below (ILS on for RNAV approach to KCXO Rwy 14) and is the example shown in Figure 1. This behavior is also demonstrated in a video (https://www.youtube.com/watch?v=7Nscg-PsyBQ) of the aproach to KCXO Rwy 14 both with and without the ILS tuned in.
-
Vertical guidance is given on VOR2 for all RNAV approaches flown. When flying the approaches, as one turns onto the runway heading, typically at the Intermediate Fix (IF), the mode on the GNS 530 changes from āTermā to the type of approach guidance (e.g. āLPVā or āLP+Vā) and the glidepath becomes active on VOR2. Lateral guidance is not shown on VOR2 except when an ILS or Localizer is tuned in on NAV2, no matter what the CDI mode is set to on the GNS 530.
-
Combining the above two points, a key learning is that lateral and vertical guidance are shown on different instruments except when an ILS is available and tuned in on NAV1 or Localizer tuned in on NAV2. This seems odd to me and is certainly not convenient as many (most?) RNAV (GPS) approaches do not have an ILS or Localizer available. I wonder if this is a bug or oversight on the part of developers. I would be surprised if this is the way the airplane behaves in real life but I havenāt seen videos or documentation of the real plane with similar configuration (e.g. Garmin GNS 530, HSI, COM2/NAV2 radio with VOR2, Century III AP, etc.) to be sure.
-
For control with the AP, lateral control is always available when the AP mode selector knob (located to the right of the transponder and just below the COM2/NAV2 radio) is in NAV mode, and probably in LOC/NORM mode as well, although I did not try that before reaching the Intermediate Fix for the approaches. Vertical control worked for all RNAV approaches by selecting the LOC/NORM mode on the AP selector knob (equivalent to APR function on newer autopilots) at or right before the Final Approach Fix (FAF), including the three LNAV approaches which do not have āApproved Vertical Guidanceā but do have āAdvisory Vertical Guidanceā from the GNS 530. It was also observed that the Glideslope (G/S) indicator light illuminates when vertical control is engaged, even when an ILS is not present or tuned in (see Figure 2).
-
Although not shown in the table, when starting out with enroute navigation with the GNS 530 with an active waypoint (flight plan activated or ādirect toā activated) with CDI in GPS mode, I noticed that sometimes the CDI needle in the HSI is not giving lateral guidance ā it is always centered even if off course as shown by the CDI in the GNS 530 default NAV page. Usually changing the CDI mode to VLOC and back to GPS fixes this.
Except that vertical guidance is shown on VOR2 instead of the HSI for the RNAV approaches with vertical guidance, the behavior observed is pretty much as expected for these approaches from what I have learned from IFR training videos for the sim. Of particular relevance here is Alpha Hotelās āMSFS RNAV (GPS) Approach Basics (AH IFR Flight Lesson 8.1): https://www.youtube.com/watch?v=gcGks86Pdaw&t=0s.
5 Likes
Thanks kaw i had the setting on my go -flight module and can set it
The Beech 18 is one of my favorite airplanes but I have avoided buying it because I prefer āStudy Levelā aircraft. Well thanks to this mod I have purchased it and I am not disappointed. Thank you
AlexBap8588.
I have a Stream Deck and an XTouch mini and have most of the switches and actuators on the Stream Deck (with Axis and Ohs). But I am having trouble with the oil shutters. (>L:DENARQ_OILSHUTTER_SET_1) does not work.
Can anyone share the correct event syntax for me to use with Stream Deck and AAO?
Also I need help with the fuel valves if anyone has event syntax for those. I tried the syntax from the Denarq user manual but no joy so far. Iāll keep working on it.
I will share some of the Stream Deck AAO scripts I have got working. Set these up on an AAO Toggle button. Use event type āSā which is script. Eventually I would like to get these on rotary encoders or sliders, but I will try the toggles for now.
Cowl Flaps
(L:CARVAR_cowlflap_L, Number) 0 == if{16384 (>K:COWLFLAP1_SET)} els{0 (>K:COWLFLAP1_SET)}
(L:CARVAR_cowlflap_R, Number) 0 == if{16384 (>K:COWLFLAP2_SET)} els{0 (>K:COWLFLAP2_SET)}
Manifold Heat
(A:GENERAL ENG ANTI ICE POSITION:1, percent) 0 == if{16384 (>K:ANTI_ICE_GRADUAL_SET_ENG1)} els{0 (>K:ANTI_ICE_GRADUAL_SET_ENG1)}
(A:GENERAL ENG ANTI ICE POSITION:2, percent) 0 == if{16384 (>K:ANTI_ICE_GRADUAL_SET_ENG2)} els{0 (>K:ANTI_ICE_GRADUAL_SET_ENG2)}
Itās L:Denarq_OILSHUTTER_SET_1
Tomorrow, when Iām at my PC I can give you the script I use for that in FSUIPC, you will be able to see which Variables Iām using.