From @alexismmef: In MFS, on the PFD, if you press Menu, it doesn't have the Option, on the Mini FPL Page, to Activate a Leg, when you select a Different Waypoint than the one activated.

We should think about, how to refresh pages when values change without using periodic refresh.

For one, we could just put the setTemplate call in a function and call it manually when a value changes.

Another solution I saw in Asobo's code which i quite liked. They use the onUpdate loop and a dirty flag to rerender/resync things.

    onUpdate(_deltaTime) {
        super.onUpdate(_deltaTime);
        if (this.symbolsToSimvar) {
            SimVar.SetSimVarValue("L:CJ4_MAP_SYMBOLS", "number", this.symbols);
            this.syncSymbols();
            this.symbolsToSimvar = false;
        ...
    }

So we could also do something like

    onUpdate(_deltaTime) {
        super.onUpdate(_deltaTime);
        if (this.pageDirty) {
            renderPage();
        }
    }

While looking at some other stuff, I have noticed that we may be able use JS imports like this:

Include.addScript("/JS/Services/Aircraft.js");

That would allow us to pull dataStorage.js in CommonPFD_MFD.js and avoid changing every *.html files we want to use it and also remove the try/catch blocks in PersistVar.

Originally posted by @tavip in #73 (comment)

From @alexismmef: When you Select a NDB / VOR / Waypoint, Information such as Full Name should be Displayed Below the Identificator. MFS right now only shows this when it's an Airport

Sometimes the ATC tells me to verify my squawk even though it's correct in the FMS. After a while they terminate my IFR flight plan and tell me to squawk 7000. When I try my last IFR flight plan again one of two things happen depending on what I do:

• If I manually enter the squawk code they give me they loose me again and cancel my IFR flight
• If I acknowledge the squawk code but leave it on 7000 in the FMS everything seems fine

So apparently my squawk code is set automatically but in the FMS it's 7000

The change for the G1000, by design, broke the coupling with the avionics brightness knobs on the handful of planes that had them working (eg, the C172). It would be great to come up with a good way of allowing both to work.

Ideal solution: adjust the SCREEN_EMISSION_CODE so it listens to both the XMLVARs created for display brightness and the avionics pot and lets the latter override the former when it changes. That might be tricky.

When you select to display the bearing pointers (to VOR) in the CJ4, they do not appear, any chance to fix that please?
Also the very important DME information is lacking from the CJ4, I hope you can fix that as well.

thanks for the great work you are doing to help us with these fixes.

Swapping is done by pressing the COM1 or COM2 line select key and it'll swap in the freq from the recall. I don't think it works right now though, we will add it in.

Request to have the “ACTIVATE LEG” implemented in the FLP PLN MENU page, so if you have a vector to intercept and join an airways, you can use that function as you normally would in the real unit.

Like the GPS used to, the altimeter setting will show 30.1 or 29.9 instead of 30.10 and 29.90.

From this avsim post
https://www.avsim.com/forums/topic/585217-cj4-community-mod-by-working-title-released/?do=findComment&comment=4355672

"SBRJ airport, IH1C procedure, i can't select any transition that this procedure allows you to (BITAK, NAXOP, SIDUR, UMBAD waypoints)"

Would like to see if this is repeatable, is widespread, impacts only departures or also arrivals/approaches?

From @alexismmef: When you Type a New Waypoint / Airport , the FPL Page will Automatically Adjust the Map Range to show the entire Route Length from Last Waypoint to the one you just Typed.

When in FPLN and selecting a line to delete, when that line is an airway to a fix, only the first waypoint in that line is deleted. Need to confirm real world behavior and replicate.

At some point we'll want to enhance the build script to support dependencies, since we do want to make our stuff interdependent. That'll require figuring out what the syntax for that in the project spec XML is.

Originally posted by @kaosfere in #1 (comment)

CJ4-GS Indicator doesn't appear for LPV approaches

From @alexismmef: The MFD Map Has a Maximum Range of 2000NM. Right now in MFS, it only goes to 200NM

I don't know if it's within the limits to what you can do, but it would be very nice if one could have different pages opened on the two FMS:es.

Would like to request an improvement regarding colors when using VOR.
So in the real unit when VOR1 is selected (with CDI), the course should be in green as well as the active NAV1 frequency with the corresponding VOR identifier should be green color. (NAV 2 freq and identifier in white)
same thing happens when VOR2 is selected, the course should be in green as well as the active NAV2 frequency with its corresponding identifier should be the same green color. (NAV 1 freq and ident in white)
when CDI is set to GPS then it should be back to what we have now, so the course is in magenta and both NAV frequencies and identifiers are white in color.
Thanks.

The yaw damper doesn't work, and the landing gear warning goes off prematurely. This thread details both problems and also provides fixes:

https://forums.flightsimulator.com/t/citation-cj4-yaw-damper-gear-warning-fixes/272098

(copied from previous repo)

It would be good to add filter rules to the CI configurations so that, for example, the CJ4 builds don't need to run when the G1000 is updated, or vice versa. At least, up until the point where one actually starts depending on the other.

I believe there's a simvar for is flying. Need to add a condition of is flying for wind display.

When an approach is active, need to not delete waypoints - add criteria for IF statement asking is approach waypoint AND is approach active and change behavior accordingly.

From @alexismmef: There should be Dashes on the Region Before you Type a new Waypoint, right now in MFS there's Blank.

PROG Page doesn't appear to show VOR fixes, only RNAV waypoints and airports.

From @alexismmef: When Selecting Procedures, the Map will Show in Real Time the Route of Each, as you Go through Them, before selecting. In MFS, it doesn't show anything.

Hi!
I just found out how to change the G1000 PFD color with SYN VIS off, since the default one is fairly inacurate:

Have a look: https://github.com/guifarias31/msfs_pfd_color_modification

Looks like a possible problem with the input filter on COM frequencies

From BackboneOne on Avsim

"today on vatsim i was unable to tune 133.22 munich radar fms was saying invalid entry"

Trying to change COM frequencies in the TUN page results in invalid entry. Changing frequencies via the built-in ATC window or 3rd party apps (e.g. Pilot2ATC) works, and the COM frequencies reflect in the PFD, but the COM frequencies in the TUN page are static and do not update.

Direct to page only shows first two approach waypoints.

I realize that there is a always a balance between making it as real as possible and as pilot friendly as possible, but I would really like to see the font sizes increased on the PFD and MFD readouts.
The bottom left section on the PFD where the critical waypoint information is located, should be readable at a glance..
Also, the top PFD readout in ALT mode has the target altitude listed, but in a tiny font..

Fuel flows seem to be excessive. The jet is capable of approximately 410-420 KTAS for about 5 hours at around 160 gal/hr (total, not per engine). This means total fuel flow from each engine should be approximately 500-600 lbs/hr at cruise altitudes and power settings. Currently we are close to 1000 lbs/hr to achieve book numbers in cruise.

Contributing is a problem where the fuel flows actually seem to rise as the jet climbs in altitude. It seems that the fuel flow is tied to TAS instead of IAS. For reference, just rough numbers:

Assumptions: At 30k' a generic turbofan engine produces approximately 36% of it's rated thrust. The FJ44 series of turbofans have a specific fuel consumption of approximately 0.45 lb/lbf/hr (being generous). The FJ44-4A has a rated thrust of 3,600 lbf.

Math: At 30k' the FJ44-4A turbofan is producing approximately 3600 lbf x 0.36 = 1296 lbf of thrust.
1296 lbf x 0.45 lb/lbf/hr = 583.2 lb/hr of fuel at this power setting (which is maximum possible thrust at this altitude)

This falls roughly in line with the known fuel burn/KTAS/endurance numbers quoted by Cessna regarding the CJ4 above. If we do a quick calc on Cessna's numbers we should be seeing 80 gal/hr per engine x 6.7 lbs/gal = 536 lb/hr per engine, which makes sense because we are likely not operating at max thrust in cruise.

DMEs are nowhere to be found for both VORs.

The softkey lights, and the lights around range, crs-baro, nav, hdg can all be lowered with the same menu key or rheostat (in airplanes with brightness knobs) in the real G1000.

In the picture you can see the instrument light knob in the DA62 1 tick above off, and in the menu they are both turned to 0% but the knob brightness is still 100%.

To reduce the risk of potential conflicts with other mods we had a healthy discussion about changing the directory structure of the mod.

For a first easy step the latest suggestion we agreed on (for the CJ4) is as follows:

• Change Pages path
  src\workingtitle-vcockpits-instruments-cj4\html_ui\Pages\VCockpit\Instruments\Airliners\CJ4
  becomes
  src\workingtitle-vcockpits-instruments-cj4\html_ui\WorkingTitle\Pages\VCockpit\Instruments\Airliners\CJ4

• Apply new paths to CJ4_FMC.html

• Apply new path to the html in panel.cfg of the airplane.

We could also move some of the things in SimObjects that is visibly referenced and changeable by us. For example the CJ4_Cockpit.xml could go somewhere else as we can change the path via model.cfg. But lets keep that for later.

From @alexismmef:

When in FPL Page, Typing a new Waypoint / Airport, it should Start with the Alphabet Letter A, not a Number. The Numbers Start only after you go through all the Alphabet.

The Wind display on MFD is opposite to the one on PFD. By comparing TAS and GS, I find out the one on PFD is the correct one.

Since this mod will probably need to be first on the list loaded, would calling the release "a-working-title" or "1st-working-title" to help those without knowledge of mod order keep it alphabetically high on the list?

This may reduce help required with troubleshooting for users when using other mods that may not be as finely tuned as this one.

Thanks for your work, and I wanna request a few features on the improved G1000...

1. Save Settings. Every time a plane is loaded, the PFD settings (Wind Direction, Bearing Pointers, Reference Speed, etc.) are gone. I don't know if the real world Garmin would reset these settings. I wonder if you could save the settings and load it at start.
2. OBS (Other Bearing & Suspend). It let you select another CRS inbound to a GPS Waypoint. Can be useful when flying some procedures.
3. insert Vectors-To-Final and Activate-Vector-To-Final. I even don't know if they are in database... If not, this is probably impossible though...
4. VNAV
5. Save and Load Flight Plans
6. Map Declutter

I just know a bit about MFS SDK, and still learning. Some feature may be hard to realize, so its just a suggestion on what you could probably make later.

Hi,

Over the past two weeks I have been working on a CJ4 add-on. I thought it would be best to merge it with the work you guys have done on the CJ4, especially since they compliment each other. However, the structure of the repo makes it difficult to contribute as your sifting through files related to other aircraft constantly. Would it not be better to have each of the aircraft in different repos, all under the same organisation?

This is a very weird one.

I was on a flight on the cruise phase, FL290 and following the FMS1 flightplan. I left the computer for 5 minutes and when I came back, I see my plane turning in circles and descending slighly. I noticed that the AP was disconnected.

Not big deal, I switch it on again and continue with the flight.

About 40 seconds later, same thing. This time I was on the chair and I noticed that the avionics where switching off and on again. For a brief second the PDF would go black and on again. And the AP was disconnected. It was like if the avionics BUS were resetting itself.

I'm just throwing this here for future ref or if anyone experience the same thing. I have the Carenado Mooney and I experienced the bug where the avionics would die mid flight. So probably this is a bug of the sim itself.

Thanks for the mod and the outstanding work!

I didn't know if it was going to be fixed in the patch (I reported it more than once to MSFS Zendesk - with acknowledgement) or if its in the scope of what y'all are doing with the G1000 but...

Exactly as the title says!

To reproduce: Climb out in any G1000 aircraft. Pre-select an altitude higher than you are. Hit FLC (it will capture FLC with your current airspeed, this is accurate). Press Nose Up. In the real aircraft, nose up means your airspeed goes down, because the nose of the airplane goes up. In the sim, Nose Up increases the airspeed lowering the nose. This is reverse of reality. Using VS, nose up will increase positive vertical speed raising the nose, FLC does the same (except in the sim where its backwards!).

Also regarding FLC, it cannot be set below the lowest operating airspeed of the GFC700 configuration for that aircraft. For example, in the G36 if you aren't moving and hit FLC it will set 80kts and cannot be set lower. If I remember its 70kts for the DA40NG, either way its in the POH under the minimum airspeed for autopilot operation listed with the specific airspeed. with FLC, you can't set the speed below minimum, even if you are currently stationary.

Last, would a curator of all these suggestions and organizing them into one space be a good idea?
I liked how we had just one thread where people would add to the list. Perhaps we can have an organized master list of everyone's suggestions which y'all can triage into what's easy/important, what's specific to only 1 or 2 G1000 flavours (meaning the G1000s from different airframe manufacturers... like everything beechcraft being in Celcius). I can see a challenge in trying to sort through the mud of all this, people adding suggestions that only exist in the nxi version (which isn't modeled at all in the sim, or from what I understand you guys are doing), or specific to one model, etc.

Basically, when shooting an ILS app, there is no information about distance to runway (DME) in the PDF. Not entirely sure if in default CJ4 its also missing, will try later.

Also, first time posting here trying to figure out tags, labels etc..

1. The title needs to be left aligned
2. It will change when FPLN is modified to show "MOD FPLN". I think the "MOD" part becomes white

after insert GPS flight plan, FD won't engage. I can only engage FD before entering flight plan.
If I engage FD then disengage it, I'm able to engage it later.

XTK L and R are reversed.

VS Code needs some configuration in order to automatically read old-school global imports from the JS side. Enabling this will make tracing our own code as well as tracing back through stock code easier to do.

See https://code.visualstudio.com/docs/nodejs/working-with-javascript

The text at the top of the PFD is a bit close to the display frame. It's obscured by the frame if you look from what I consider to be a normal head position.

With just departure and arrival airports, no PROG is shown. Need to update to/next to handle undefined.

From @alexismmef: There should be a Map Displaying the Region of the Selected Waypoint, as you Type it. The Range Knob changes the Distance of the Region Shown on this Mini Map

The EXEC element and property is now in main.

We need to properly show/hide it.

CJ4_FMC has a property fpHasChanged which can be set and will show/hide the EXEC element accordingly.

In a page it should be reachable via fmc.fpHasChanged = true|false