Hi,
here is a screenshot from the Asobo C208B MFD. From my point of view are the engine values: TRQ, ITT, NG and especially PROP RPM very difficult to read. What do you think? Is there a way to get them brighter?
Those readings look about the same as my MFD. From my seating position I do have to lean forward sometimes to read them. Old age, in my case.
Itās a bit difficult for us to personally follow every bit of feedback that comes in through all the various channels, although we do try to read it even if we donāt necessarily have the time to answer each question individually.
As far as the aforementioned issues goes, the lack of magenta VNAV target altitude above the altitude tape on the PFD and lack of data sometimes prior to TOD (and on ground) in the Active VNV Profile window on the MFD are both bugs that will be addressed in a future update.
This is not correct. A VNAV profile for descent is constructed regardless of whether the approach is loaded or activated.
2 Likes
Thank you, that is all we needed to know.
OK thanks, again good to know what should happen, but I have had situations where that did not happen for whatever reason.
Iāve an issue with entering the transponder code in STBY mode. The field is complete white and I canāt see what Iām entering. Only after all 4 digits itās readable. Not sure since when this happen
Which aircraft are you using in the screenshot? That NXi looks different than some of the āstandardā NXi aircraft. Are you running any mods/add-onās?
Regards
The screenshot is from the Asobo C208B without any addional mod. I tested it also with the C172, here itās the same issue
1 Like
@DAQUA3828
Well DUH! 
After I woke up and reread your OP when I wasnāt asleep, concur, there is an issue (and itās still in BETA 1.34.12.0) where the transponder code wonāt show up until the fourth digit is pressed when in standby mode.
Great Find!
Regards!!
1 Like
Good catch
Iāve got it also in the G36 and G58
I hope it will be fixed soon
1 Like
Thanks for the report, we have logged this and it will be fixed in a future update.
2 Likes
Hello. Surely this has been brought up before, but I have had no luck in searching.
The Garmin documentation for the G1000 NXi states that Advisories, or as it calls them āSafe Operating Advisoryā are displayed in Green text. However when an Annunciation is defined in panels.xml as āAdvisoryā it shows in White text.
Maybe
Yeah I guess it is possible the specific implementation in a given aircraft varies, but that just reinforces that we should have options, no? The aircraft I am trying to more accurately replicate has green advisories.
what Aircraft is it?
Turns out I was oversimplifying it, and in fact there are both green and white. In fact the white advisory are CORRECT. So I was wrong on that one. The Kodiak also has a āNormalā annunciation which is in green.
So tl;dr the WHITE āAdvisoryā Annunciation is in fact correct. There is however, at least in the Kodiak, an additional Annunciation type āNormalā which is displayed in green.
I canāt find anyway to color the text manually though, only assign it an Annunciation type, of which the only options (documented) are Warning, Caution, and Advisory.
1 Like
Hi,
the Kodiak shows the Inert Seperator inside the PDF. Is there a way to get for the C208B too?
There is no such annunciator.
I seem to be unable to get CursorColor to work. The following code still draws a White cursor. What am I doing wrong?
<Gauge>
<Type>Horizontal</Type>
<Style>
<Margins>
<Top>-10</Top>
<Bottom>-10</Bottom>
</Margins>
<CursorColor>blue</CursorColor>
<Width>10</Width>
<ReverseY>True</ReverseY>
</Style>
EDIT: Actually the more I play with this.. I donāt think ANYTHING in the section is being applied
EDIT2: So yeah I donāt know if this is a case of documentation being wrong/me reading the wrong docs/docs just not applying to the WT G1000NXi? But this does not work, and the reason it does not work is right in the MFD code. Iāve modified it now and it works.
Is it possible/allowed to modify the base code and redistribute it with a mod? Iām guessing the answer is no but wanted to ask.
The ābugā is right here on line 1160 of āworkingtitle-instruments-g1000/html_ui/MFD/MFD.jsā
// msfsSdk.FSComponent.buildComponent("path", { d: "", fill: "white", stroke: "black", "stroke-width": ".5px", ref: this.ptrPath }),
msfsSdk.FSComponent.buildComponent("path", { d: "", fill: this.props.style.cursorColor, stroke: "black", "stroke-width": ".5px", ref: this.ptrPath }),
The commented out line is the original, the second line my change to make CursorColor work. Basically it is hard coded to only be white.
1 Like
Hello @Agathorn1975
We have logged the issue and will look into it.
Is it possible/allowed to modify the base code and redistribute it with a mod? Iām guessing the answer is no but wanted to ask.
You can redistribute it while adhering to the license of the published source microsoft/msfs-avionics-mirror: MSFS Avionics Source Code Mirror (github.com)
In the meantime though I would suggest to publish it under a different path (and change in your panel.xml) with your package since it will otherwise overwrite the instrument for all other planes too.