Multiplayer Signaling

Bug #1212495 reported by Nicholas Ozorak
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Open Rails
Expired
Low
Unassigned

Bug Description

I was in a multiplayer session on the NC Piedmont route available on Trainsim.com. Despite what the dispatcher would set, the signals didn't always match between dispatcher and engineer.

Revision history for this message
Nicholas Ozorak (etozorak) wrote :

V1691.

summary: - Multiplayer Signalling
+ Multiplayer Signaling
James Ross (twpol)
tags: added: multiplayer signals
Changed in or:
status: New → Triaged
importance: Undecided → Low
Railcat (railcat)
description: updated
Jijun Tang (jtang-h)
Changed in or:
assignee: nobody → Jijun Tang (jtang-h)
Revision history for this message
Jijun Tang (jtang-h) wrote :

More information is needed, please.

Changed in or:
status: Triaged → Incomplete
Revision history for this message
Nicholas Ozorak (etozorak) wrote :

What other info do you need? The trains were mixed, and the route is available for download at Trainsim.com.

Revision history for this message
Jijun Tang (jtang-h) wrote :

Where is the signal that you are trying to set (i.e. which signal from which station), and what are the differences you noted?

I haven't tried the route yet, but I assume I think it will be difficult to try and find out those with problems.

Revision history for this message
Nicholas Ozorak (etozorak) wrote :

Too many signals to list. I also saw this issue in a multiplayer session using the M&M sub (Trainsim). Red signals which should be green was what I noticed most.

Revision history for this message
r.roeterdink (r-roeterdink) wrote :

It could also depend on whether you open a dispatcher window at the server or at the client.
At present, each client runs the signalling process independent from the server, with only signal aspects broadcasted by the server. As a result, the actual signal states may differ from the shown aspect, this can lead to all sorts of problems.

Revision history for this message
Nicholas Ozorak (etozorak) wrote :

In our sessions, the server is the dispatcher.

Revision history for this message
Jijun Tang (jtang-h) wrote :

Each client does not perform a full signal update, but receives signal states (and light states) from the server, thus it should synchronize in theory.

Changed in or:
status: Incomplete → In Progress
Revision history for this message
r.roeterdink (r-roeterdink) wrote :

Just started rewrite of MP signalling.
That should clear this problem as well.
It will however take several months to complete this work.

James Ross (twpol)
Changed in or:
assignee: Jijun Tang (jtang-h) → nobody
status: In Progress → Triaged
Revision history for this message
Cédric GNIEWEK (sharpeserana) wrote :

Does the problem still happen with version 1.4?

Changed in or:
status: Triaged → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Open Rails because there has been no activity for 60 days.]

Changed in or:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.