Hi @DabullAir
Can’t speak to xbox, but I’m not having any issues with that on a vanilla version of the sim on PC.
Regards
1 Like
It’s recommended to use actual G1000 NXi manuals.
3 Likes
It is the oddest issue. I am using navigraph nav data, but that shouldn’t affect the search functionality.
You might want to search the NXi threads. I don’t use navigraph but I do remember several posts (including WT dev) that there is a known issue with searches and names with the now-default NXi and navigraph. I believe they were hoping to have it resolved in SU11.
Regards
1 Like
Does anyone know if Along Track Offsets or User Waypoints are implemented or if they’re going to be? I haven’t figured out how to use them if they’re there already. I’ve tried following the official G1000Nxi handbook to no avail.
ATK and User Waypoints are not presently implemented, although they are planned for some time in the future.
1 Like
We finally had a chance to look into this, and this is correctly reflective of the real unit. The MFD minimums is not meant to be sync’d, it’s meant to show the default minimums for the selected procedure, which can then be changed. This will then transfer to the PFD.
One of the reasons it took us a minute (besides being a bit slammed on our three current projects), is that we couldn’t really recall a time where this was not the implementation. Looking back at older code we’re still not sure it ever worked any other way than it does now (or if it did, it wasn’t intentional).
Thanks. Previously I would set minimums for my destination on the PFD based on my anticipated approach as part of the pre-flight checks.
When ATC eventually informed me which approach to expect I would select that approach in the MFD. The minimums would be showing what I had previously set in the PFD and if the approach was different to the one I anticipated, and had different minimums, I would increment or decrement the value in the MFD as required and the PFD would automatically follow suit.
Currently, regardless of what I have already set in the PFD, when I now select approach in the MFD the minimums is always blank, no value at all, until I enter something. Whatever I dial in at that point is reflected back to the PFD.
In the current version I have never seen a default value appear for any selected approach in the MFD, it is always blank until I enter something.
From what I remember since the Mod became an NXi version (and before it was on Marketplace as an add-on), the Minimums always was blank, even if I had set it during a previous session.
I am not talking about previous session settings being remembered.
Naturally the minimums settings in the PFD will be blank on starting the Garmin until something is entered, that is what I would expect to be normal.
My description is about what happens after that.
I can’t ever recall Minimums being set in the PFD carrying over to a newly selected Approach. In any case, from a workflow perspective, I wouldn’t want that anyway. Seems like a way to get a preset altitude that may or may not be appropriate to the Approach selected. Probably why Garmin makes it work that way IRL.
I am describing my experience of how it worked before, whether that was correct or not.
If the way it operates now reflects the real Garmin more accurately then fine, but it does not display the default minimums for the selected approach as described by WT:
I am now going to try a flight without entering anything into the PFD Tmr/Ref MINS setting pre-flight and see if that makes any difference, as it seems to be a redundant option now unless only flying VFR and not using the MFD approach options.
However it is supposed to work I always check the value against the appropriate approach chart.
Sorry, I was unclear there. That’s what it is meant to do, but we don’t receive minimums in the sim navdata specifically. If we did, that’s where it would go, as in the real unit.
You can select procedures from the PFD also, so it’s not necessarily redundant. Additionally, sometimes folks will add a little for their personal minimums, and it’s easier to do it with the little dial in front of you as you ascertain the approach situation than reaching over to the MFD. But there’s no wrong answer.
2 Likes
Thanks for clarification.
I’m having issues with the g1000 nxi system not finding waypoints when I’m putting them into the flight planner or “direct to” section. I enter the name of the waypoint and the system just says it doesn’t exist, despite the fact that it’s shown on the map in the plane itself, as shown in This image
I’ve updated the in-game map to the latest airac cycle since I have a navigraph subscription, but its affecting waypoints that exist in the base game too?
Any help?
You can check out this thread
But the gist of it is, yes there is a known issue, but it appears to be fixed in the current beta and should be good when SU11/40th Anniversary edition releases on 11 November.
Regards
2 Likes
Amazing, thanks for letting me know about this. An added note to this is that if you sign up to the beta it fixes the issue
Is the WT G1000 NXI a default instrument in the simulator now or do you stilll need to download it?
The G1000 NXI is the default in the sim for all default planes since SU10 and many of the 3rd party planes have been updated to automatically use the new default NXI, such as the Diamond DA62X mod.
IIRC, the download is available for those who fly 3rd party planes that used the NXI before SU10 that have not been updated for SU10.
1 Like
thank you for the answer. so is it still prudent to download the NXi addon in case some planes need it? would it conflict at all with the built-in one now, or cause a doubling of files to overwrite?
1 Like