a320NX update

No, you don’t have to delete the work folder. If you’re already using the custom FBW version, you don’t need to delete the a32nx folder inside the community folder. Just run the installer and click update and it’ll replace for you.

But I think it’s still always a good practice to delete the A32NX folder from the community from time to time. Especially when there’s a major update being deployed. It’s just better to clean up junk files and install a fresh one to make it as compact as possible without having old files conflicting with the new.

But you don’t need to delete the a32nx in the package folder with the work folder inside. If you want to, you can just backup the throttleconfig.ini file or the contents inside. Once you reinstall a fresh copy, just replace it with the backed up one. That works too. But it’s not necessary.

The EFB tablet is currently only working with SimBrief. I had a go at it, and it works fine. But I personally don’t like it because it requires too much effort from me setting up the flight plan properly to make it work in the sim. I usually plan my flights according to my mood and looking at the world map, looking for which airport I want to depart and which airport I want to go to. While also checking the total flight duration, making sure it’s still within the duration that I want.

With SimBrief, I can’t have that visualisation. I need to already decide which airport I want to depart from and arrive to, and I also have to know the ICAO code to put it into SimBrief. It’s good for a proper flight planning because you get flight briefing and all the documentation that’s generated. But it doesn’t suit my flying style of just picking a place that I fancy from the world map and just click click using the GUI and I can fly within 2 minutes of setting things up. Those other stuff in Simbrief is just too much and too serious for me.

So while I wouldn’t be able to fully utilise the EFB because I just don’t like using SimBrief and the Link MCDU button isn’t working yet. I think it’s a nice step and I’m looking forward for its usability for non-SimBrief pilots.

You can plan a route via skyvector.com or using a tool like LittleNavMap, and then copy/paste the waypoints into the simbrief planner and generate the route. Its only a couple extra steps in “deciding on the fly” where you want to go.

1 Like

Lol, that’s even more extra steps over the extra steps I already don’t like doing with Simbrief. Thanks, but neither of this is for me.

I honestly can’t think of any other way that’s quicker and simpler and always works than the built-in world map for planning flights.

1 Like

Using the “Installer” for the first time trying to install the Custom version and it’s sitting there at 0% (for 20 minutes so far).

Downloading from GitHub manually has been almost instant previously.

That sounds like the old version of the installer that you’ve been using that’s no longer connected to the current server.

Your installer should look like this and version 1.0.3. It’s actually downloading as instantaneous as manual downloading from github for me. But faster overall since it decompress automatically.

It does, I literally installed it for the first time ever from the link a few posts up.
Still sat at 0%. Restarted it twice. Maybe 3rd time is a charm.

Maybe antivirus blocked it since it does inject a file directly from the internet?

Running the installer as Admin has gotten me to 2% immediately…

Ehh, even downloading manually from github will give you the same thing anyway. So whichever way works, that’s the way to go.

My only hassle is that I have to keep editing the same Interior cockpit file whenever I get a new update so I can have my pilot and copilot model rendered inside.

Yep I’ll go back to manually downloading. It’s sat at 2%…

Very strange… manually downloading the developer build just took about 5 seconds. Manually trying the custom FBW dev build and its stuck on 2.2MB out of 301…

Thanks! I supposed cause with the last custom FBW update (before the flytab operarive) i did what you say. Only deleted A32nx in comunity folder but not the other ( wich contains the work folder)one and it works perfect.
I also have a word note with my throttle ini backup. But I was not sure if the work folder contains other files that needs to update too.

Great advice as usual and have to say I agree with you in respect of the MSFS planner

I use simbrief without default ATC.
I use ATC chatter and FS2 crew.
Yesterday ORBX released a new freeware fearure: VOLANTA, is a good flight tracker , much better and accurate than the default vfr map.
You can import a flight plan on diferente formats or even inport from simbrief. Very useful to Keep your flights as well.

2 Likes

CTD
234567890 this is a sentence

The CUSTOM FBW version adds a folder directory inside package/local state/a32nx/ work/
Inside work folder you can found the throttle. Ini file . You must to open the sim and charge the a320 for to create this directory.
Then exit your flight and open the ini file and edit for your throttle works properly.

Hi can you please explain how you actually go about making the changes so that you get to keep your copilot visible. Cheers

Yeah I want this copilot in my cockpit too!!

To make this work, you need a bit of a technical understanding on how this works. But I’ll try to make it as clear as possible.

You need the following tools to make it easier to make the edits and maintain it whenever they make updates to the mod:

  1. Notepad++ (notepad-plus-plus.org)
  2. JSTool plugin for Notepad++. You can download and install this from within Notepad++ plugin page.

So after you have both tools above and ready, here are the steps:

  1. Download and install this mod made by Mugz. This is their ideas so all credits goes to them. Add Co-pilot to your cockpit (Standard Edition) • Flight Simulator 2020
  2. Install the A32NX developer one from that mod, and make sure the folder is renamed with ZZZ to bring it to the bottom of the list. This is important because we want the sim to load the A32NX mod first and have this copilot mod load the last because we’ll be replacing the cockpit files using the one from this mod.
  3. When you finish updating the Experimental version of the A32NX mod. Navigate to the folder and find this specific file:
    \A32NX\SimObjects\AirPlanes\Asobo_A320_NEO\model\A320_NEO_INTERIOR_LOD00.gltf
  4. Copy this file, and bring it to the Visible Copilot mod folder from step 1 and 2. Make sure you navigate down to each folder until you find the exact same file. Paste it here to replace it.
  5. Open the A320_NEO_INTERIOR_LOD00.gltf file using Notepad++. And in the Plugins menu, open the JSTool and select JSON Sort. This will format the code into a more human readable format.
  6. CTRL+F and find the term Nodes And click find “Twice”. This should bring you to a Node array with a lot of sequence of numbers.
  7. Above that nodes array you will see some blocks of codes that are grouped in brackets. You just need to set your cursor to the last bracket and add the following code:
, {
    "name": "PILOT_0",
    "rotation": [0.0, 0.0, 0.0, 1.0],
    "scale": [1.0, 1.0, 1.0],
    "translation": [0.567698, 1.262695, 10.8251953]
}, {
    "name": "PILOT_1",
    "rotation": [0.0, 0.0, 0.0, 1.0],
    "scale": [1.0, 1.0, 1.0],
    "translation": [-0.567698, 1.262695, 10.8251953]
}

This is if you want both pilots to appear in the cockpit. If you only want pilot. You just need to add the PILOT_0. If you only want copilot, you only need to add PILOT_1. If you want both pilots and copilot, you copy this whole code.

  1. Remember the nodes array that you found on step 6? Set your cursor to the line with the array of numbers and press END on your keyboard. This should bring you to the last number in that line.
  2. All you need is to add additional number at the end based on how many models you added. If you only add either Pilot or copilot. You need to add one more number. If you add both Pilots and Copilots, then you need to add 2 additional number. Assuming the last number is 1401. Then you need to add comma then 1402 then comma then 1403. So it will look like 1401, 1402, 1403] This is for both pilots and copilots. And as I said, if you only add one either pilot or copilot. you just need 1402.
  3. Save the file, and you should be good.

If there’s a new update to the A32NX mod. You have to repeat step number 3 onwards. But the more you get used to it, the faster it is you’ll do it because you have muscle memory.

The good thing about using the separate mod is to reduce the number of edits you have to do when you update the A32NX mod. Without the mod, every time you update you have to make the code edits. But with a separate mod file. You only need to do Step 3 onwards when the update breaks your cockpit. Otherwise, any new update to the A32NX mod that doesn’t make changes to this specific file, should not affect the cockpit or make it invisible. But I still do recommend to redo steps 3 onwards at least once a week just to make sure it’s stays in sync with the latest file.

I’ll post some screenshots or video tutorial when I can.

1 Like

cheers for this very detailed set of instructions …lol Im not sure my muscles would ever remember this all. but im def going to give it a try …and I am sure that there will be lots of folk out there who will also want to give it a go and would appreciate a wee video tutorial , but for know cheers once again
henry

Yes, I use Little Nav Map and then copy/paste into SimBrief if the flight plan has a lot of waypoints. If it’s a short one, I just enter it in on the FMS keypad manually.

The functionality that LNM offers is AMAZING. I can’t imagine going back to the MSFS world map to create my flight plans.