btw, what server are you flying in?

I tested today and found some strange behavior after the players were moved into the mission aircraft, e.g.:
- Host: Prop pitch and Radiator didn't work until I activated the autopilot for a second
- Client: Autopilot was enabled initialy, if deactivated the engine couldn't be started (oil and water temp. was at 0°C, not ambient temp)

Can anyone confirm this? Or even better has someone an idea to solve this?

@Tigertooo: Not much public online flying in the last weeks. The launcher crash is really annoying ... hopefully after the next patch I'll be at ATAG or III/JG27 more frequently.

thnx Banks

I compared my code with that of Navyr and I assume the reason for the mentioned problems is that I call the Player.Place() method in the OnActorCreated method, which could be to early.

I will delay it by some seconds to see if it helps.

I remember there was a bug in naryv's script. Either a player could not take control if joined in progress, or AI did not take control is player ALT-F2 from the aircraft or a player could not take control after re-enter the aircraft again after ALT-F2. The bug depended on whether autopilot or plane switching was enabled in difficulty settings. Sorry, do not remember more precisely. I think naryv said that autopilot must be disabled on the server to fix it.

Thank you, that sound reasonable. I had autopilot enabled, not sure about plane switch. I will test with autopilot disabled and report back.

IIRC

You needed Auto enable with that script.

Awesome work!
I´m going to test this scrip and also the mission loader script in our server for coop missions.
Keep it coming!

New version available: http://code.google.com/p/il2coop/downloads/list

IL2Coop-0.2.0.15 fixes the host and client problems, no strange behaviour any more:
- Controls (Prop pitch, radiator) now work correct for the host
- Clients can start the engine as regular (engine temp is also normal)

The script finally works as intended.

There is no need to have AI control enabled in realism settings.

The reason for the strange behaviour was timing related. Obviously there has to be some time between mission loading that contains the aircraft, aircraft creation and the assignment of a player to that aircraft. I added a delay after the mission loading and the assignment of 3sec. which solved all the problems.

thnx Banks,will try