4.35 multiplayer (Host in 3d Q)
-
Hello,
Has the message that didn’t allow other players to commit 3D until the host is the 3D? has it done on purpose or is it an unintended regression ?
I am not finding it in 4.34 and 4.35 manual to see the difference.
Best regards
EDIT:
This is in 4.34 U3 change log:
r21017
- Give 10 seconds room instead of 3 seconds when entering waiting screen to give time to react and change spawning method
- Allow clients to enter into waiting room even if host is not in 3D
- Clients will wait in the waiting room until host is in 3D even if their takeoff time has passed
- This allows to accelerate to X64 if everybody commits at the same time (as in the good old days) though host will always be the first in 3D independently of his own takeoff time
So if I understand correctly, the message was extinct in U3?
-
Hello,
Has the message that didn’t allow other players to commit 3D until the host is the 3D? has it done on purpose or is it an unintended regression ?
I am not finding it in 4.34 and 4.35 manual to see the difference.
Best regards
EDIT:
This is in 4.34 U3 change log:
r21017
- Give 10 seconds room instead of 3 seconds when entering waiting screen to give time to react and change spawning method
- Allow clients to enter into waiting room even if host is not in 3D
- Clients will wait in the waiting room until host is in 3D even if their takeoff time has passed
- This allows to accelerate to X64 if everybody commits at the same time (as in the good old days) though host will always be the first in 3D independently of his own takeoff time
So if I understand correctly, the message was extinct in U3?
Hello pilot.
In version 4.34 it was possible through falcon bms.cfg to change the option so that the client pilots could enter without having to put the server in the 3d world, then when the update 4 came, that was eliminated and the server had to enter the 3d world .
In this version 4.35 in the BMS-Technical-Manual.pdf page 165 it is explained that by enabling the following command with 0 or 1 g_bEnforceServerIn3dWorldBeforeClients it is possible to control whether or not the server has to enter the 3d world so that clients can enter. Before it is valid to mention that this line does not exist in the falcon bms.cfg so you have to add it, also put the prefix set before so that the simulator takes it as a correct line and at the end place the 0 or 1 depending on whether want on or off. We have been testing and it does not work, even if it is deactivated, the server always has to enter the 3d world so that the clients can enter.
Greetings from the Caribbean.
-
Fortunately, this line doesn’t work.
-
Thanks Viper,
But still I don’t understand it completely.
What is the standard behavior without the line?
-
Yesterday our host was in the first flight, and some people was able to press take off and wait in the ramp-taxi-takeoff selection while host was also there. Without the message that we used to have in the last updates of 4.34
-
Thanks Viper,
But still I don’t understand it completely.
What is the standard behavior without the line?
As LorikEolmin commented in a post above, the line now in this version “fortunately” is not operational, that is, it is worth it that it is at 0 or 1, the server has to enter the 3d world anyway.
The normal behavior now in this version 4.35 is, that the server enters the 3d world, yes or yes.
Greetings from the Caribbean.
-
Yesterday our host was in the first flight, and some people was able to press take off and wait in the ramp-taxi-takeoff selection while host was also there. Without the message that we used to have in the last updates of 4.34
As you said yourself, there was no message in the last updates. It was a nuisance preventing from clicking “take-off” and accelerating time automatically for everyone.