The game startup sequence for clients starts first the Viewer and then sends to the server the initial data of the client player train. A feature of Multiplayer is that, if the client exited the game after having run more than a km, his position is stored at the dispatcher's computer side. When the client re-enters the game, the dispatcher computer sends him the old train position, so that the client hasn't to restart his train run from the start position. If however this occurs after the Viewer has run, the Viewer must load all viewer data related to this other position of the train, and this can last many seconds where the client player hasn't a complete picture on his monitor.
So the startup sequence must be inverted: first the client sends his initial data to the server. He waits for some seconds a reply from the server, that can include a new position for his train, in which case he modifies his local position of the train. After this the Viewer is started, and so the train appears on the screen in its correct position.
Fixed in x.4270.