Robert stated just today or yesterday that MCC is on the map. Ghost mouse is an excellent idea.Majestic, is that the Dash guy? I've heard about his products. might be interesting.

Robert stated just today or yesterday that MCC is on the map.

Indeed. http://forum.avsim.net/topic/356169-multi-crew-capability/page__view__findpost__p__2187199

Majestic, is that the Dash guy?

Yep!

PMDG is a company all about realism. Flying a jet by yourself just isn't realistic. I think they really should implement multicrew, and if they did the NGX would be complete. And yeah. Being PNF might be boring if all you do is eatch but if you're really doing all the real roles, I think it would be fine. I would love to have another pilot in the cockpit. It just makes it more real.

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

There are two concepts that come out of your questions/suggestions that I've thought about for a while. If there was a separate program that read and transferred simconnect gauge data and control inputs... instead of having this built into the gauges themselves:1. Synchronized, simultaneous control inputs from both the pilot and copilot (instead of having to transfer control back and forth).2. With such a program, you might be able to make any FSX aircraft multi-crew capable provided both parties had the software and one of the two ran the synchronization software.The other idea I had might also allow multi-crew without flooding, sync and de-sync problems and lessen the load on the processor and network. I could be wrong here, but it seems that (for instance with the Maddog) that both parties run a full software suite, which results in essentially have two aircraft that are operating by themselves, and you have the illusion that it's the same aircraft. If one party was running the full software, and the other was running what would amount to a shell of the suite, it would seem to me that things would run much more smoothly.

The UDP flooding (that still exists) has NOTHING to do with any attempts to SHARE the Gauges.To be blunt, it's just Sloppy programming, and should be easily corrected.Other developers have done so--- it amazes me that the "GREAT" PMDG cannot correct this issue.That being said, personally, I have given up worrying about it, having adopted the solution that If you want a job done right -- do it yourself.

No doubt Multi-Crew through shared cockpit is the ultimate crew experience as far as MSFS is concerned.It doesn’t come without its own problems though.FPS drops.Unless it’s run on a private LAN, it can be subject to Internet traffic jams with the inevitable synchronisation issues.Need to find a close friend eager to sit on his chair for many hours waiting for you to say “flaps 1” or “gear down”. Try performing a cross the pond flight without acceleration to see if your mate is going to be there, by the time you get to your destination.The next best thing is Multi-Crew with a virtual officer using speech recognition.The drawback is that this FO can only do things he was programmed for, and you can’t have a chat with him on topics other than aircraft operation.On the other hand, he will always be happy to play the PNF (Pilot Not Flying)You can rely on him day and night, on short or long haul trips.For those who want to have a go at the available free Demo, just look at my signature, or google “Multi Crew Experience”.3 days guaranteed fun.

There are two concepts that come out of your questions/suggestions that I've thought about for a while. If there was a separate program that read and transferred simconnect gauge data and control inputs... instead of having this built into the gauges themselves:1. Synchronized, simultaneous control inputs from both the pilot and copilot (instead of having to transfer control back and forth).2. With such a program, you might be able to make any FSX aircraft multi-crew capable provided both parties had the software and one of the two ran the synchronization software.The other idea I had might also allow multi-crew without flooding, sync and de-sync problems and lessen the load on the processor and network. I could be wrong here, but it seems that (for instance with the Maddog) that both parties run a full software suite, which results in essentially have two aircraft that are operating by themselves, and you have the illusion that it's the same aircraft. If one party was running the full software, and the other was running what would amount to a shell of the suite, it would seem to me that things would run much more smoothly.

Thats funny as thats the same thing I was thinking about. I was curioous if it is possible to create an application that can read Sim Connect channels and then identify them. Then you could name these particular channels for a particular addon, save it as a configuration for that addon and then use the app sync up two sims flying the same addon. I'm not sure if sim connect transmits globaly by default, but yes it might give the ability to have one app create a shared cockpit for every addon that uses sim connect this way. Who knows, I'm not a programmer, but I think if this was possible it would be a great selling addon.

Thats funny as thats the same thing I was thinking about. I was curioous if it is possible to create an application that can read Sim Connect channels and then identify them. Then you could name these particular channels for a particular addon, save it as a configuration for that addon and then use the app sync up two sims flying the same addon. I'm not sure if sim connect transmits globaly by default, but yes it might give the ability to have one app create a shared cockpit for every addon that uses sim connect this way. Who knows, I'm not a programmer, but I think if this was possible it would be a great selling addon.

Why not just program correctly for FSX shared cockpit in the first place, and let FSX take care of the cockpit syncronization.It's all there already, and it works -- it just needs to be implimented correctly.

+1 on this one, the Maddog has been out for quite a few years and has the best working weather radar and shared cockpit code in Fsx by far.Shared cockpit is a fantastic adventure which takes our hobby to the very next level, unless you have tried it, you really have no idea how good it is.Like Bryan said, if anyone can pull it off, PMDG can.