just tried this update. jumped in the DA62 with a simple sim generated plan. The first thing I noticed was a locked Saitek autopilot at 99000 alt. All my other Saitek gear are inoperative also. Looks like I can manage radios and altitude using a mouse in the vc. I switched out the NXi for a gns530 and all works fine. Just something to keep in mind as your build your product.
The altitude bug is also present when using external camera I’m sure is related.
Is this update available on the xbox marketplace?
Please see the release notes (always available in the first post in this thread) for known issues regarding both of those items.
-Matt | Working Title
Is there a github version of the nxi? I would like to see how some things are done in this complex html gauge, so I don’t want it “installed”, just view the code like all the other versions.
This product is not presently open source, as it is being developed by Working Title as part of our first party development work on the MSFS team. However, the package is not encrypted, so you can install it and view the compiled JS, which is well commented.
-Matt | Working Title
If you are making a flight plan in the NXI itself, can you adjust the altitude of the plan or no? I thought someone said no awhile back, but I don’t know if that was a specific thing. I tried reading this whole thread, but it has been several days of read time.
No you cannot. WT guy says it will come in future updated versions. This is still in development and we are the testers. You can delete it through content manager and have the vanilla G1000 if you desire and come back to the NXi when it is more complete at a later date.
does it mean we can’t reuse parts of the code ? or just we can’t fork it ?
Just like all the other standard unencrypted sim JS, nobody is prevented from modding it or otherwise using it.
-Matt | Working Title
Thank you very much, yes I have the WT Nxi and am looking at that, how ever the SDK in not well documented for html/js/css and was wondering if there are missing files that we can view, example the msfssdk imports.
example:
import { FSComponent, DisplayComponent } from ‘msfssdk’;
import { XMLCircularGaugeValuePos, } from ‘msfssdk/components/XMLGauges’;
I’m only trying to understand how you save simvars because the original G1000 engine system page uses MaxSinceStart
and that gets reset every time you open the page.
edit fyi: g1k_common.css cannot be opened. - all other files can, that I have tried. (works now)
That’s our own internally built layer we’re using for the moment. However, you can see all the code in the MFD.js and PFD.js, which are bundles and is what the actual instrument loads.
-Matt | Working Title
Ok looking at some code I have to disagree with your choice for weights of fuel Your using jet fuel, but what about avgas?, You have the weight for Jet Fuel: 6.7 lbs per US gal and avgas is 6.1 lbs per US gal. Or is this a built in Flight sim value?
// the following fuel units use the generic conversion factor of 1 gal = 6.7 lbs
UnitType.LITER_FUEL = new SimpleUnit(UnitFamily.WEIGHT, ‘liter’, ‘liters’, ‘l’, 0.80283679);
UnitType.GALLON_FUEL = new SimpleUnit(UnitFamily.WEIGHT, ‘gallon’, ‘gallons’, ‘gal’, 3.0390664);
And I assume your library has the def for SimpleUnit.
Hudson has done an overview of the Mod. He says that he is going to cover more, but says the screen seems dim to him.
- He is really good at explaining things.
I noticed this, too! Is this intentional and can it be changed?
Garmin G1000 working title version – data and instruction pop up – altitude displays 99,000 feet
I am using the sim on an Xbox X and sim 6 installed. I am using the G1000 NXI in a Cessna 172. When you adjust the altitude knob the data and instruction pop up always displays an altitude of 99,000 feet. When you twist the altitude knob the altitude setting changes correctly in the PFD (see photo 1) but not in the pop up when you select the altitude knob (see photo 1) or when you are in the external camera view in the HUD (see photo 2)
See known issues.
Doesn’t affect AP operation or anything, so it’s not a game-breaking issue, especially not if you fly from the cockpit vs external view.
i can’t get map panning to work either in the working title version
This isn’t implemented yet.
I’m sure once it is, the guys at WT will be shouting about it.