dga711

Fyi, from the SU14 (Beta) release notes

It is on the copilot MFD as per the real plane. In the freeware mod - back in the days - the MFDs weren't split, so it showed it different

It also works in Lock. Just hold the inner knob with the Left Mouse Button and press the Right Mouse Button at the same time.

WIth FPL open on the MFD you now have to push the inner FMS knob to activate the highlighting on the FPL page. This is true to the real thing. We just didn't have this behavior before, because we also didn't have the page menu on the MFD.

It's crucial for proper functioning of the vertical modes in our autopilot. And we rather have a display issue (on hardware) for now, than a worse autopilot. Edit: Also what Matt said 😄

The issue here is, that the sim provides different altitude slots for different vertical modes. Since we implemented our custom autopilot solution for those vertical modes we have to override specific slots, therefore making this a visible issue. So in the meantime, if possible with your setup, you have to read the specific alt slot. Otherwise, we expect changes in the API with SimUpdate 6 that will resolve this in general.

Make sure that you highlight the blank "_____" line below the header and then turn the inner FMS knob. Not the ORIGIN header itself.

Afaik its only the joystick to pan charts that doesn't work in Legacy.

This format means 1hour and 58minutes. Looking at the Flight Plan I can see on your screenshot it all looks a bit weird. It goes Dubin - Strum - Dubin - Strum etc. and your Airways are also shot up. It either bugged out for you or there have been mistakes made when setting up the flight plan.

Just hold the inner knob with LMB and press RMB

Yes. 2 and 1.

Hard to make a list of that ^^ The WT1000 is now just the stock instrument + engine pages (since the stock 1000 caught up in terms of the features we've added to that mod back then). The NXI is a new instrument built from scratch reusing zero code from current stock. As I already stated the main draw right now is the capability to do advanced flight planning, also including Airways. And the flight path calculation that is able to parse and calculate all ARINC leg types. Plus the custom autopilot implementation that is able to fly those legs (incl. Holds, PTs). And VNAV! 😉 There was big focus on making it as performant as possible, as well as much attention to detail so it looks just like the real thing. Since we always focus on navigation features first, it is missing a bit of informational pages at the moment, but that will come over time.

As far as I can tell you have to switch the CDI source (softkey at the bottom) to the tuned localizer (green needles). As per your screenshot it is handling it as LPV not ILS. We didn't implement the auto switch yet.

One of the big things that make the NXI great is the advanced flight planning and path calculation capabilities (DME arcs, procedure turns etc.), that are currently not possible in any other instrument across the sim. These capabilities are prototyped in the NXI, so to say, for them to be transferred to other instruments and/or in the end into the core sim at a later point in time. As with the CJ4 (that contains our first attempt of our own flight plan management) we will implement the sync back to the sim, but the VFR map will never fully match since the sim doesn't parse the procedures the way we do and therefore doesn't draw them like this. Again, until these things get integrated into the sim. In your case you did see a path on the VFR map because you had set it up in the world map, so the sim knows about your plan but shows it the way it calculates it.

Do you deselect the keyboard focus (click anywhere on the instrument screen) after entering something? The little icon next to the input field should not be blue anymore.

Don't mistake the freeze issue, which happens under certain circumstances when calculating TOD during flight, with CTDs that people are reporting. Its a different thing and will be fixed with the next update coming very soon. We have no clear indication of the NXI causing CTDs or why that would be. But we are of course investigating. Also to set the record straight again NXI: Is a new instrument built from the ground up with the goal of replicating the G1000 NXI, which is available on the marketplace as "early access" until it is polished enough to be in the core sim WTG1000: Is the "old" mod of the stock legacy G1000 we had for months and is no longer maintained. There is a 0.4.0 release for SU5 compatibility though, which is just the stock G1000 + engine pages. You should never have both installed at the same time.

The frequency knob only firing downwards is an issue with the modelbehaviors of the plane which is to be fixed by Asobo. But they know about it. Probably next update the NXI will have settings persistence for brightness and the map settings. The other things will come over time.

Next update will fully support importing custom waypoints and POIs from world map

The main benefit of this early version would be its advanced IFR capabilities imo. On the flight path calculation side it is even a crazy improvement to what we did in the CJ4. It should draw and fly all kinds of different leg types (including RF Legs, PT etc) to a very realistic level. The flight plan management, flight path calculation and ap was all built up again from scratch, which took quite some time. As with the CJ4 we are putting Navigation before Features.

There is no indication based on facts, that this is the case 😉 Most of these are already logged and fixed internally. Next update will come very soon and remedy those issues. All three points you listed will come very soon. Brightness settings are also implemented. To your point of "releasing a product that is unfinished". That is why it is called early access and came to the marketplace before becoming stock in the sim. So people can opt in/out. The main point of releasing it at this state is to put the advanced IFR, flight planning and flight path calculation features out there for people to test and enjoy. Doing it this way was very good as we now received a lot of feedback and reports which helped us already in fixing a lot of issues. From the beginning it was our goal to involve the community in the development of this avionics stack. The G3000 (which was a mod and not done from scratch) also took mostly one person 10+ months to get it where it is now. So we rather bring something to the interested people early that might not have it all yet instead of people having nothing 😉

I think its even only 1Mb afaik. Well. Its just code 😉

The new G1000 NXI is a completely built from scratch instrument. It is distributed as "early access" through the marketplace until it is at a good enough place to be integrated into the core sim. The WT G1000 mod was a modification of the stock G1000 and you can't run both at the same time, since the NXI replaces that stack. So remove it from the community folder when using the NXI.

Sounds more like an issues between NXI and GTN then. But right now, we wouldn't really know what causes it. Should ask the GTN dev what his current investigation concludes. EDIT: Didn't really see other reports of issues like that. So it may as well be on your end

Maybe lost in translation but did you try having A32NX and NXI but no GTN? Having just the NXI from the marketplace and latest FBW dev, should work fine imo. Make sure you don't have the WTG1000 mod in community also.

@jarmstro The WT G1000 mod is updated for SU5. But at this point it is basically the stock one with engine pages. We didn't hear about any definitive mod conflicts yet. Which from a technical perspective seems unlikely, since the NXI is its own instrument and not based on any files in the stock code. But if you have more details, feel free to provide. EDIT: Looking at FBW Discord the devs mention, they see no conflict with their latest dev build A32NX and NXI @Espana Pete There is no guide yet. Since the NXI is heavy work in progress, it would have to change too often right now. Also the CJ4 one was mostly created by members of our community, so who knows if they pull one up again 😉 We are working on dimming the inop functions in the Avionics like we did on the CJ4, so it is more clear if a function is not enabled yet.