Trouble when playing multiplayer

Thank you for your reply! I learned something new today!

I checked with the host, and we have the same version. Both on the loader and the sim.

So, if SimSig works similarly to real signalling systems, then to make communications more efficient it might send indications to clients based just on position in a list rather than a name.
So rather than a message saying "track circuit TJM is occupied" (3 bytes for the name), it might be one saying "the 374th Track in the sim is occupied" (where the number is sent directly rather than as text making it smaller,2 bytes in this case).

But this would need you or the host to be on non-matching sim versions which I thought sim sig might check for?

stighetl in post 143032 said:

I checked with the host, and we have the same version. Both on the loader and the sim.

Well if the sim versions are the same, then that proves my guess wrong, and we will probably both have to wait for someone who does know how SimSig works to come and explain what might be wrong.

Whilst slow internet causing dropped messages has caused issues which look similar in the past for others I would be a little surprised if that's what you have here,

Tempest Malice in post 143031 said:

Tempest Malice in post 143031 said:

But this would need you or the host to be on non-matching sim versions which I thought sim sig might check for?

We don't bother to make such checks; the Loader makes it so easy to be up to date that it wasn't seen as worth it.

That is incorrect.
When a client attempts to connect to a host with either the loader or simulation not being the same version number, the client will receive a disconnection message and information on what versions the host and clients both report. This is a feature that gets used a fair amount in the testing of sims esp when there is a frequent release of builds for testing and we have more than 1 version of the simulation saved in our files.
An example of the messages the client receives;
[quote]00:00:00 Attempting connection to server - please wait...
00:00:00 The host at 127.0.0.1:50505 has rejected your connection attempt.
00:00:00 Server is not running the same simulation or the same version
00:00:00 Server reports 5.3.3/5.17.2.1/newstreet
00:00:00 Client reports 5.4.0/5.17.2.0/newstreet
00:00:00 Click "Check for updates" in the SimSigLoader

clive in post 143035 said:

Tempest Malice in post 143031 said:

But this would need you or the host to be on non-matching sim versions which I thought sim sig might check for?

We don't bother to make such checks; the Loader makes it so easy to be up to date that it wasn't seen as worth it.

That is incorrect.
When a client attempts to connect to a host with either the loader or simulation not being the same version number, the client will receive a disconnection message and information on what versions the host and clients both report. This is a feature that gets used a fair amount in the testing of sims esp when there is a frequent release of builds for testing and we have more than 1 version of the simulation saved in our files.