[RESOLVED] MP with V4

[Pop]

We have been using P3D 3.xx, and 3.2 in the past with no MP connections problems. We are not able to connect either to our server or to each other with V4. gets all the way to "join" and P3D crashes????

[MiG21bis]

We have been using P3D 3.xx, and 3.2 in the past with no MP connections problems. We are not able to connect either to our server or to each other with V4. gets all the way to "join" and P3D crashes????

I've been testing with Pop, and can modify his previous post. We are now able to connect one of our stations with another as host, in a stable v4 session. We'll see if we can work from there, connecting those same two stations but switching host/guest roles. Will update posts here further as we see results.

[Pop]

still a prob Faulting application name: Prepar3D.exe, version: 4.0.23.21468, time stamp: 0x59279be2
Faulting module name: api.dll, version: 4.0.23.21468, time stamp: 0x59279c8f
Exception code: 0xc0000005
Fault offset: 0x00000000000153e1
Faulting process id: 0xb44
Faulting application start time: 0x01d2dc15f69c47b5
Faulting application path: C:\LM4\Prepar3D.exe
Faulting module path: C:\LM4\api.dll
Report Id: 817fab20-653d-41a0-b39f-3732a6ded9c2
Faulting package full name:
Faulting package-relative application ID:

[MiG21bis]

still a prob Faulting application name: Prepar3D.exe, version: 4.0.23.21468, time stamp: 0x59279be2
Faulting module name: api.dll, version: 4.0.23.21468, time stamp: 0x59279c8f
Exception code: 0xc0000005
Fault offset: 0x00000000000153e1
Faulting process id: 0xb44
Faulting application start time: 0x01d2dc15f69c47b5
Faulting application path: C:\LM4\Prepar3D.exe
Faulting module path: C:\LM4\api.dll
Report Id: 817fab20-653d-41a0-b39f-3732a6ded9c2
Faulting package full name:
Faulting package-relative application ID:

And this error is happening when Pop tries to connect to me as host, which results in CTD on his end.

[Pop]

We got it working last night by varying sliders, can't tell which one did the trick???:(

[Fryman]

I was able to join in with POP and another player. My V4 system had all stock sliders. The only problem we has was we all entered in the air near host and we could not change this setting. Once we had control of the airplane everything worked very well.

[Pop]

can't find the option to "join on ground" or " join at airfield' as a client. Also "in game comm" is "red icon out".:(

[MiG21bis]

My experience same as Fryman and Pop; as guest, cannot join in any other mode - only "join in air near host" is possible, despite host allowing all three joining methods.

Next, despite host having in-game comms enabled, guest always shows in-game comms disabled for the session.

[Clifton Crane]

Hello,

Thanks for the reports.

Pop,

The Starting Location setting can be found in the Additional Options tab when joining a multiplayer session.

MiG21bis,

Are you saying that you have found the settings, however they are disabled on the client's machine?

Thanks.

[MiG21bis]

...MiG21bis,
Are you saying that you have found the settings, however they are disabled on the client's machine?
Thanks.

Exactly right, Clifton. No matter how "permissive" the settings are on the host, guests are always restricted to only "join in air near host", and no in-sim comms (Red X versus Green check mark).

[simskunkworks]

...MiG21bis,
Are you saying that you have found the settings, however they are disabled on the client's machine?
Thanks.

Exactly right, Clifton. No matter how "permissive" the settings are on the host, guests are always restricted to only "join in air near host", and no in-sim comms (Red X versus Green check mark).

I do confirm, no matter how setting are into server options, clients can join the session only "join in air".
We are using a a batch file like this to set standard session:
start /min Prepar3D.exe -"net:H:\P3D\etc\vaafse.cfg" "-flt:H:\P3D\etc\VAAFSE_DEFAULT.FLT"
the vaafse.cfg says:

[Multiplayer]
AutoStart=2
AutoSignOn=1
AccountLogin=0
LanUsername=VAAFSE_SERVER
ClientEnableVoice=0
GameName=VAAFSE_HOST
GamePassword="xxxxxxx"
GameDescription=Welcome to VAAFSE P3D server
DefaultAircraft=Tower
MaxPlayers=63
condAccoutPassword=0
PasswordReqd=0
PublicOnWeb=0
PublicOnLan=1
AllowChangeRealism=0
AllowChangeLocation=1
AllowJoinInFly=1
AllowHostPauseSession=1
AllowPauseLocalSim=1
AllowSharedAircraft=1
AllowUseSlewMode=1
JoinWherever=1
JoinInAir=1
JoinAtAirport=1
EnableVoice=0
EnavleVoiceOnCom=0
TimeToStart=0
EnableShare=1
EnableVoiceIntercom=0
DisableSharingAfterStart=0
EnableAntiCheat=0
AllowAllHostAircraft=1
AllowAllAircraft=1
AllowRacingAids=0
AllowFailures=0
WeatherString="User-defined weather"

No one of bold settings is applied to client.
We will make also some tests on a MP session with 15 players or more, hoping that syncro problems that effected previous version 3.3 and 3.4 are gone, we were forced to use version 3.2.3 that was the last one working nicely in MP with more than 7-8 players.
/SSW

[Pop]

Any progress on these 2 bugs?

[Clifton Crane]

Hello,

The crash upon joining should be fixed in the next release. The crash was related to the "Broadcast GPS data to network" setting being turned on.

We have been able to reproduce the starting location issue as well and are currently working on a fix. This issue is specific to directly connecting by IP address.

Thanks.

[Pop]

How about the "in game comm" problem?

[Brad Shiver]

We were able to fix the issue for both the starting location and comms when connecting by IP address. They should be working correctly in the next release.

-Brad