You don’t say 
So the WT G1000NXi does not “work as in IRL” 
The sim is not real life. The manual for the real G1000NXi is nearly 800 pages and it is a very complex system. I admire the work done by WT to develop a system that is close to real-life in many important aspects, but I don’t expect it to be 100%, and it does not need to be. There are bound to be compromises and there is nothing wrong with having options that compensate for the fact that it is running in a simulator.
Woah! “You don’t say” right back at you! Your “Where can I download this Garmin installer…” question
suggests someone who doesn’t realize that’s a process to change the default VFR code in the real unit, hence my simple and non-judgmental answer. If the question was supposed to be humor, it went over at least my head. I was by no means criticizing the sim or this beta. Everyone here realizes there’s limitations to replicating real life in the sim, and it’s not limited to using a mouse for interaction or updating nav databases online instead of feeding an SD card into a slot on the right side of the real unit. Where you get that I’m expecting this to be 100% escapes me, nor do I care.
I am happy to say I fully agree with your well-deserved admiration for WT and I also fully agree with your last sentence. Let’s move on.
Yes my sense of humour does operate at flight levels, but then I am British
(Retired Royal Air Force aircrew)
And there was a clue at the end of the question that I was joking:
Have a nice day 
Getting back to my original request, can we please have a settings option to select either 1200 or 7000 for the VFR button? Because a “Garmin installer” is not coming to my neighbourhood anytime soon 
Now I get it and all in fun. No worries! 
Typically legalese speak to cover their bases in case of an incident. It does not speak on the reliability of the system.
Yes, I can go either way. Frankly, I was expecting someone to say that you can indeed configure the VFR button to whatever you want; am somewhat surprised that it isn’t an option within the real NXi. So yeah, I concur on compromises for the simulator.
I am hoping for Time and Temperature fix.
You are correct about my error on the ‘green’ circle it is as you stated… my bad
and your answer is spot-on 
its reading set altitude and is not capable of ‘rendering’ distances of a ‘curved’ earth… that’s why as you move closer the horizon will adjust
After SU7 I am getting CTD very often, I believe due to Nxi mod. Anyone else having the same problem?
As far as I’m aware, from this thread and from discussions on Discord, the NXI JavaScript can’t really cause CTD’s in the sim, unless in a rare occasion that a JS call into the sim then subsequently calls an in-sim buggy routine that would cause the sim itself to CTD.
The only other thing I’ve seen folks talking about is if you rapidly move across pages on the MFD (airports, waypoints, flight-plan etc). I’ve heard that this can cause a crash, and I think this has been reported to Asobo.
it’s 5am and I have to go to work, but figured I would reply to this since I was flying a 300nm IFR from KSWF->KRIC in the SR22 and just about at the FAF and had a CTD for what I suspected was this very reason… So I reloaded to test if it was in fact from rapidly moving through pages, and yep…I was able to replicate it 4x, came on here to see if anyone else reported the same thing. Got My Answer.
I can also confirm that I occasionally get a CTD when I enter the flight plan in NXi before takeoff. Once that is done, there are no unexpected crashes.
I pasted the Working Title folders of their three main Garmin systems in the Community folder but they didn’t show any changes to Icon A5, JMB VL-3 and the rest of the aircraft with Garmin satellite navigation screens.
What have I not done right?
Difficult to say without seeing what you see. It’s possible you have extracted them wrong, and the addon is inside another folder.
If you look in your Community folder, there should be a folder for each addon. Inside each of those there should be a layout.json, and manifest.json file. If you don’t see those files, but another folder, then the addon has been extracted one level too far down on the tree. Sot it should look something like:
Community
├───addon
└───manifest.json
└───layout.json
If you are looking for the G1000 NXi, it is available on the Marketplace only (free). The latest legacy WT G1000 mod is no longer supported and will not appear different from stock other than an enhanced EIS. Additionally, the aircraft you list (Icon A5, JMB VL-3) use the Garmin G3X and not the Garmin G1000 NXi.
Yes, “fast” rotating FMS knob on MFD for me is 100% CTD
My workaround is to ignore MFD and just use PFD
That’s not the point I am asking, sir.
My question is: I have pasted all the latest files from Working Title (including G3X) in the Community folder. But I see no change in the aircraft navigation systems.
Have a pasted my files in the right folder?
THAT’S THE QUESTION.
Remove any latest WT Garmin G1000 mod from the Community folder, then install the G1000 NXI from the Marketplace which will install the G1000 NXI files in an Official folder.
To summarize, these are the steps required to see the Garmin G1000 NXI in any aircraft using the default stock G1000 navigation system:
If any other Garmin system other than the G1000 is not working correctly, then that should be a topic for a different thread.
From g1000-v0.4.1:
If you have the Working Title Simulations G1000 NXi installed, you do not need this mod installed. This mod and the new NXi cannot be installed at the same time. Similarly, if you would prefer to use this light G1000 mod for the engine pages, you will need to uninstall the NXi. Thanks!