A32NX rendering pilots in cockpit

Hi all,

May I ask is there a way to let the A32NX render the co pilot inside? I found one mod at flightsim.to but with the latest development build it seems that it still can’t render the co pilot, and it makes the APU bleed not working

Yeah, I posted a message that it requires an update to make it work with the current dev version. It looks like the issue is a lot more difficult to solve. I used to manually add the copilot as an object to the interior model file. Which usually works, but recently I can’t get it to work using the same method. So I had to download Mugz’s mod and that works for a time until the current dev version. Nothing else we can do but wait, I guess.

I would not use such mods, as they cause issues, as you already found out. FBW is not supporting it, so, just dont use them id say.

2 Likes

They only caused issues when the FBW changes made the copilot model incompatible. As soon as it’s fixed, it works again. That doesn’t mean the mod caused issues outright. They just need to keep up to make it compatible. The copilot model was actually integrated as a standard feature of FBW months ago. But something happened and they found out the copilot mod was the cause.

It’s not actually the model themselves that’s causing the issue, it’s the configurable copilot model that you can change instantly using the MCDU options that made it imcompatible. That’s why I used to write the copilot model code directly into the interior model to have the sim render them without the need to touch on the MCDU at all, which used to work until recently when I can’t even get them to render at all.

Then because it was an issue, FBW team posted a poll to the public whether they want the copilot model to be an important aspect of the aircraft. It was a landslide result favouring No. But hey, that’s democracy and I have to respect the will of the people. So I have to live with an empty cockpit from time to time, which kind of breaks immersion since I use FS2Crew to have a copilot monitoring and helping me out with checklist and all. And hearing the copilot voice in an empty cockpit. Makes me feel like I’m hallucinating.

Whenever it causes an issue, I won’t use the copilot mod, but as soon as it’s working, I would use it because that mod is a big deal for me. And I’m just hoping that MSFS would incorporate copilot model as a default feature instead having to rely on mods. But yes, having a visible copilot sitting next to me is important to me.

1 Like

Mugz have updated the mod. You should be able to use it again now.

1 Like

For me, I also like having a copilot at my side, since I let her do the comms during flight, as, I believe, IRL. I have used the Mugz mod for dev version. The problem is, at least with FBW installer, I get updates to FBW A320 almost daily, so I understand It’s quite difficult to keep up with that.

For instance, yesterday I installed an update for Mugz mod from the previous day and also last update for FBW A320. The result was black screens in cockpit, including radios, and no copilot.
I use the MSFS Addon Linker by bad2000, to turn mods on and off with ease, so I managed to determine the issue was with the copilot mod. After I turned it off, everything worked fine with the plane. I’m waiting to get a new update for the copilot mod before trying it again.

P.S the Addon Linker also available in flightsim.to.

I just wish we can get them integrated again, at least to the FlyPad.

1 Like

I can’t even get the aircraft to show up in the aircraft selections. I’ve tried a few different suggestions and it’s still now there. Guess it’s a flop.

You might need to uninstall any FBW A32NX from the Marketplace/Content manager. Then check your Community folder and delete any FBW A32NX in there. Then use the installer to reinstall the aircraft again.

I’ve already uninstalled and reinstalled it, but not through the content manager. I’ll give it a try.

The one through the content manager is just to make sure you’re actually uninstalling the Marketplace version if you have previously installed it. Otherwise, if you only deleted from the official folder without going through the content manager, it will think that you have missing files and redownloading the addon again. That’s why if you uninstall from the content manager, you can save the state into your cloud setting telling it that you want to remove it from your installation, so it doesn’t reinstall again in the future.