October 5, 20223 yr Ever since SU10 I've been having problems with the g1000 NXi. Mainly with VNAV and any RNAV approach that is supposed to have VNAV support. The issues continued today. Flying into Manila (RPLL) in the Philippines I had loaded the ILS Rwy 06 as the approach, but not a single altitude constraint loaded. I was also unable to set up VNAV with a TOD point - so, the problems continued. After completing the flight (the coupled ILS was no issue). I took a look in the Content Manager to see if there was something going on. It was my understanding that the WT NXi was now a part of the sim and that no installation or adjustment was necessary. Indeed there was no sign of the NXi as needing an update. On a whim, I did a "Garmin" search of the Installed items... there were TWO NXi's installed. I selected both to be removed. One was removed and one remained: Version 1.0.4. If this is selected there is no option to remove. I'm guessing that there is a fault in the SU10 install that leaves the previous NXi add-on installed (if used) while adding the new. I'm hoping that there was a conflict that kept the new version from working properly and that it will function normally in the next flight. Edited October 5, 20223 yr by RandallR Randall Rocke
October 5, 20223 yr I believe the content manager SHOULD show both. One is the default NXI as of SU10, and the other is there to permit third-party add-ons to use the NXI where they need the other version in the content manager. At least temporarily, leave both in the content manager.
October 5, 20223 yr 25 minutes ago, RandallR said: I'm guessing that there is a fault in the SU10 install that leaves the previous NXi add-on installed (if used) while adding the new. I'm hoping that there was a conflict that kept the new version from working properly and that it will function normally in the next flight. No, I believe you should not have done that. You should have both those NXi entries in the Content Manager. Just looking at the file sizes is a giveaway, one is tiny compared to the other. They are not duplicates. What aircraft were you flying as 3rd party aircraft using the NXi now might be rekt. GregH Intel Core i7 14700K / Palit RTX4070Ti Super OC / Corsair 32GB DDR5 6000 MHz / MSI Z790 M/board / Corsair NVMe 9500 read, 8500 write / Corsair PSU1200W / CH Products Yoke, Pedals & Quad; Airbus Side Stick, Airbus Quadrant / TrackIR, 32” 4K 144hz 1ms Monitor
October 5, 20223 yr Author The NXi has failed to work properly (with both installed) in the Turbo Bonanza and the C208B mod. Randall Rocke
October 5, 20223 yr I think both those (modded) aircraft use the NXi you just deleted. It might mean they default to a previous, bad G1000 version but either way, I don’t think you will find that this fixes your problem. GregH Intel Core i7 14700K / Palit RTX4070Ti Super OC / Corsair 32GB DDR5 6000 MHz / MSI Z790 M/board / Corsair NVMe 9500 read, 8500 write / Corsair PSU1200W / CH Products Yoke, Pedals & Quad; Airbus Side Stick, Airbus Quadrant / TrackIR, 32” 4K 144hz 1ms Monitor
October 6, 20223 yr " Chris (Z-6) — 09/21/2022 Another quick note for @everyone on the NXi: With the inclusion of the G1000 NXi into the sim as the default G1000, the latest G1000 NXi will appear in all default G1000-equipped aircraft in MSFS SU10. However, if you also have G1000-equipped third-party aircraft, you will need to ensure you have the latest package from the Marketplace installed, which will enable the NXi in third-party G1000-equipped planes as well. If you have previously “bought” and installed the NXi Marketplace package, please go to the Content Manager and ensure it is updated to v0.14. If you haven’t ever installed the NXi from the Marketplace before, you can do so to enable the G1000 NXi in your third-party G1000-equipped aircraft. As of this update, third-party developers have the option of either specifying the NXi or the legacy G1000 in their aircraft – once a third-party dev has specified the new NXi instrument directly in their aircraft, the Marketplace installation will no longer be required for that aircraft." https://discord.com/channels/750764704175226992/763804431413673984/1022197498946789388 AMD 7800X3D, Windows 11, Gigabyte X670 AORUS Elite AX Motherboard, 64GB DDR5 G.SKILL Trident Z5 NEO RGB (AMD Expo), RTX 4090, Samsung 980 PRO M.2 NVMe SSD 2 TB PCIe 4.0, Samsung 980 PRO M.2 NVMe SSD 1 TB PCIe 4.0, 4K resolution 50" TV @60Hz, VR: Pimax Crystal Light + HP Reverb G2 @ 90 Hz, Honeycomb Bravo Throttle Quadrant, be quiet 1000W PSU, Noctua NH-U12S chromax.black air cooler. 60-130 fps. no CPU overclocking. very nice.
October 6, 20223 yr Author Until today, the combined NXi packages failed to work properly in all modes (at least with the modded versions of the G36 and C208B). I set up a flight this morning with the G36 having removed one of the packages yesterday to see what would happen. During the start-up MS/ASOBO did a small update. When I started the aircraft the enroute altitudes loaded correctly for the first time since SU10 but not the approach altitudes. I reactivated the extra NXi package and rebooted the sim. After restarting the flight plan and starting the Turbo G36, I noted that all altitudes were now included in the FP (Enroute and Approach). The flight proceeded normally and (for the first time) all VNAV modes worked properly (including the Approach). Whatever was going wrong (I hope) has now been rectified. Edited October 6, 20223 yr by RandallR Randall Rocke
Archived
This topic is now archived and is closed to further replies.