Just doesn't fit with my flying style. I enjoy FS recreationaly, so I don't fly by anyone else's schedule. They're all offline flights and sometimes I'm paused for extended periods while cooking a meal. Just wouldn't work for the poor soul in the right seat.

I think we should not preclude it this feature just because of the internet connection. Today broadband connections are getting better and cheaper and this trend will go ahead in the future. So I'm absolutely in favor for a cockpit sharing evolution of the NGX

I voted a yes and willing to pay a few euro extra for it. Normally I fly the iFly with fs2crew voice co-pilot over VATSIM and although I also have the PMDG NGX I'm waiting to step over till the fs2crew version for PMDG is there. However, iFly is not planning to extend with a Multicrew add-on or update so now I'm waiting for PMDG. I know there are a lot of Virtual Airlines in the world that want a full Multi experience.Maybe we can expect something with Flight or the new X-plane 10 but when there is nothing coming, I consider buying the Maddog Pro 2010I have several friends who are retired airline pilots who want to share the cockpit in PF and NPF with me but we all demand a full working system.I hope PMDG will make the step....Happy landings...

I think it would enhance the RW simulation of a complex aircraft. We are all entitled to fly the plane the way we want to, but I would enjoy flying in a 2 person crew. It's a feature I'm looking forward to. In a SP or not.In regard to people's behavior, I play MMORPGs and FPS games, I'm well aware of the childish behavior and I hope to find people who want to try to seriously simulate the multicrew experience. (Whether in a VA or this forum)

...Shared cockpit functionality with a plane as mega complex and intricate as the NGX I'm sure would be a massive undertaking for PMDG... but if anyone can pull it off, they can.

The Leonardo crew managed to pull it off and their plane is at least as complex as the NGX, in many aspects more complex. So surely PMDG should be able to pull it off as well.

The Leonardo crew managed to pull it off and their plane is at least as complex as the NGX, in many aspects more complex. So surely PMDG should be able to pull it off as well.

I really hope they can get cracking at this MultiCrew. If for some reason they decide to throw in the towel, I hope the SDK is open enough where a third party dev can make a client application that will allow fully shared cockpit, as it would really be a shame if something with this much immersion doesn't go to the next step to complete the entire simulation.JB

Couple questions to some of the c++ coders and net programers around here.Assuming the SDK will give full access to all cockpit states and switch positions...1. Would it be possible to create a client app, that runs on a local networked computer that can sync to the NGX locally via simconnect and flag cockpit states in their current positions?2. Could this app also sync all aircraft flight states, like velocity, altitude, attitude, throttle position, flight control position etc via simconnect, without having to use the default FSX Multiplayer shared cockpit?3. Could this app also refresh the syncronisation fast enough, but not too fast to use too many resources off the main sim computer and at the same time allow for the ability to adjust syncronization refresh rate to tweak for performance?4. Then, could this application be networked to the same application over the web, using network code, thus creating a syncronisation of multiple aircraft states and flight conditions, to then be syncronised to another local sim computer, thus giving the ability to have shared cockpit?Obviously, one of the local client apps would have to be flagged as the master and the other a slave in regards to flight control positions (Yoke, rudder and brakes) with the option to switch, so that both clients don't have conflicts to which client is "flying" the aircraft. Obviously, the rest of the cockpit switches would need to be dynamically syncronised, so that both the PF and the PM can operate and syncronize switches regardless of who is flying the aircraft (Master Clent).The system would have basically three network connections between two simmers. SimComputer 1 to Client 1 via simmconnect locally, then client 1 to client 2 over the web, then client 2 to SimComputer 2 via simconnect locally. Now wouldn't this system benefit by being able to adjust for each of the three connections seperately (For troubleshooting and or adjusting network performance)? The local client could even have cockpit switch states shown visually in the UI so that you can see if syncronization is working or not. Not to mention, by having a seperate client app running on a seperate local client, would not take precious resources away from the NGX.I am not a programer, but I can only imagine this is an example of such an application that would allow for multicrew.JB

Couple questions to some of the c++ coders and net programers around here.Assuming the SDK will give full access to all cockpit states and switch positions...1. Would it be possible to create a client app, that runs on a local networked computer that can sync to the NGX locally via simconnect and flag cockpit states in their current positions?2. Could this app also sync all aircraft flight states, like velocity, altitude, attitude, throttle position, flight control position etc via simconnect, without having to use the default FSX Multiplayer shared cockpit?3. Could this app also refresh the syncronisation fast enough, but not too fast to use too many resources off the main sim computer and at the same time allow for the ability to adjust refresh rate to adjust for performance?4. Then, could this application be networked to the same application over the web, using network code, thus creating a syncronisation of multiple aircraft states and flight conditions, to then be syncronised to another local sim computer, thus giving the ability to have shared cockpit?Obviously, one of the local client apps would have to be flagged as the master and the other a slave in regards to flight control positions (Yoke, rudder and brakes) with the option to switch, so that both clients don't have conflicts to which client is "flying" the aircraft. Obviously, the rest of the cockpit switches would need to be dynamically syncronised, so that both the PF and the PM can operate and syncronize switches regardless of who is flying the aircraft (Master Clent).The system would have basically three network connections between two simmers. SimComputer 1 to Client 1 via simmconnect locally, then client 1 to client 2 over the web, then client 2 to SimComputer 2 via simconnect locally. Now wouldn't this system benefit by being able to adjust for each of the three connections seperately (For troubleshooting and or adjusting network performance)? The local client could even have cockpit switch states shown visually in the UI so that you can see if syncronization is working or not. Not to mention, by having a seperate client app running on a seperate local client, would not take precious resources away from the NGX.I am not a programer, but I can only imagine this is an example of such an application that would allow for multicrew.JB

YESbutPMDG have already indicated that they intend to produce a Shared Cockpit solution for their 737NGX, so why try to re-invent the wheel. ?

YESbutPMDG have already indicated that they intend to produce a Shared Cockpit solution for their 737NGX, so why try to re-invent the wheel. ?

I'm just thinking out loud...:)JB

What is multi-crew? Is that where you have someone in RL join you virtually in the cockpit? What I'd like to see is a co-pilot in the sim that will work the flaps & gear when required

What is multi-crew? Is that where you have someone in RL join you virtually in the cockpit?What I'd like to see is a co-pilot in the sim that will work the flaps & gear when required

You will have that as soon as FS2Crew comes out.With multi-crew you will have what FS2Crew offers and a lot more.

PMDG have already indicated that they intend to produce a Shared Cockpit solution for their 737NGX, so why try to re-invent the wheel. ?

Any confirmations? I didn't see any of them.

Any confirmations? I didn't see any of them.

1. http://forum.avsim.n...ost__p__20252332. http://forum.avsim.n...ost__p__21409693. http://forum.avsim.net/topic/351627-ngx-customer-feedback-pmdg-mod-please-read/page__view__findpost__p__2144404

Some time ago, PMDG confirmed that multicrew (shared cockpit) would be available for the NGX. To my knowledge, they've been silent on MC since the release, except I BELIEVE they said they planned to release it in SP2. While nobody knows for sure, the UDP flooding issue that has been tampered down may have been due to the gauge sharing programming for MC to work. It caused several problems.Only PMDG knows if MC will be implemented or not.I've been flying MultiCrew for about 2 years now, and it does provide an extremely high level of immersion - especially under ATC control on VATSIM. I recommended to PMDG, Leonardo (possible update to their Maddog), and Majestic (for their upcoming aircraft) that they implement a "Ghost Mouse" icon be provided showing where the other pilot/co-pilots mouse is so that you'll be able to see what they're about to click or clicking instead of just hearing the "click". Obviously if you were in a real cockpit, you'd see what the pilot/copilot was doing. PMDG didn't reply to my suggestion, but I hope they implement this.

...I recommended to PMDG, Leonardo (possible update to their Maddog), and Majestic (for their upcoming aircraft) that they implement a "Ghost Mouse" icon be provided showing where the other pilot/co-pilots mouse is so that you'll be able to see what they're about to click or clicking instead of just hearing the "click". Obviously if you were in a real cockpit, you'd see what the pilot/copilot was doing. PMDG didn't reply to my suggestion, but I hope they implement this.

Great idea there. Never though about it.