In multi-player, when we move instruments to a separate window and drag that window over to a second LCD monitor, P3D does not "remember" the settings after resetting the flight. It reverts back to a single window and we have to start over again and drag things to the second monitor. The earliest version of P3D has this issue in single player mode and it was fixed. But we are still seeing this problem in multiplayer (where we expect to spend most of our time on joint missions).

I assume you already know about this. I would like to know if there is a fix on the horizon.

Hi Beau,

Resaving flights doesn't make any difference. In a multi-player session window states in flight files ( we know where they are) are ignored, pure and simple. It doesn't work and it's not difficult to reproduce (follow steps below).

1) Select aircraft - Beach Baron G1000 (or whatever).
2) Open Views-->Instrument Panel-->Radios.
3) Undock Radio stack window (or whatever) and move it someplace.
4) Make Default Flight - optional, but irrelevant.
5) Save Flight - "Yadda"
6) Flights-->Multiplayer-->Host Session-->OK
7) Additional Options-->Load Light-->"Yadda"-->Fly Now-->OK

Q: Where's the radio stack?
A: Gone

1) Flights-->Exit Multiplayer Session
2) Flights-->Load Flight-->"Yadda"

Q: Where's the radio stack?
A: Right where we left it.

It doesn't matter how the MP flight is loaded (e.g. command line or manually), what aircraft it is, or what ANY parameter in the panel.cfg is set to for said windows, window positions simply are NOT read (or ignored) from saved flight files in MP sessions. You should be able to reproduce this easily at your end.

It appears to us that there is NO WAY to use Prepar3D in a location-based simulation with external windows on external displays (e.g. "simpits") in multi-player sessions.

We are helping to integrate TackPac into P3D so that weapons can finally be avaialble within this simulation. Currently slew mode is hardwired OFF in any multi-player MISSION. Multi-player freeflight has a host option to allow/reject it, but multi-player MISSIONS do NOT allow slew mode. No slew mode, no TacPack. The TacPack itself can prevent any player from using slew to control their aircraft, and we have a TacPack host option for that, however if the simulation itself is preventing slew in a multi-player mission, the TacPack has no way to control its own objects and thus rendered completely useless in missions.

I am hoping that getting this resolved is a high priority. I am here to help where I can.

Mike

Now that 1.4 is out and I'm using it ... I'm seeing the same problem Mike was. Didn't fix it?

We tracked down and fixed some of the panel saving issues in multi-player, but we didn't look into it heavily for multi-channel. It's possible the fix we put in for saving panels only didn't carry over to MC. We'll see if we can reproduce it and log a bug ticket, but the fix would probably not be available until the next release (which I don't have a time frame for).

I do have some ideas you might try to work around most of your issues. You can set panels only to true in a camera definition and load up your instrument system with that view. There may be issues with using panels only for your default view if the view is on your master pc, however, as it may prevent the master doing certain simulation updates that only happen when drawing.

While it's a bit limiting compared to the flexibility of using a flt file, you might try making a variant of your user aircraft panels folder for your MC scenario with different default placements and with any unused panels removed from the config. Most multi-channel visual systems require this level of scenario-specific configuration and cost 10+ times more per channel, and many of those systems only support a single monitor per channel.

Thanks,
Beau