[JorD1]

Just want to add my experience this evening when trying it in a full MP game.
We had only problems.
Encountered the following things:
Train Out of controll, I ran back behind the signal pressed ctrl+m, and accidental pressed it twice.
Train wen to WaitDisp mode, don't knwo waht that is?
According to the first post I should make the signal ahead green?
The signal didn't turn green whatever I tried.

Also it was almost impossible to set every signal in front of a switch without having players running in a red light.

[Csantucci]

Are you testing the actual release (1912)? From what you write, it does not seem so.

Anyhow also R1912 has some problems here.
I tested R1912 on my computer with two OR instances, first using tsimserver and then locally.
With tsimserver there seem to be comprehension problems between local computer and tsimserver: both instances start as "dispatcher" (so the second instance does not recognize that there is already one dispatcher on the chosen port), and I don't see my user names on the tsimserver page.

Running locally on my PC(one server, one client), the client is not able to connect as can be seen in attached logfile
 OpenRailsLog_socket.zip (2.39K)
Number of downloads: 294

As a verification I tested both operating modes with R1888, and everything run correctly.
So, as far as I can test, release 1912 is not yet usable for MP sessions.

[roeter]

The socket connection is performed in ClientComm.cs. This code has not been changed at all as part of the signalling update, which has now been reverted.
So this error has nothing to do with the changes in either revision 1889 or 1910, but more likely with the changes related to the new opening sequence - ClientComm.cs was changed for this in revision 1902.

Regards,
Rob Roeterdink

[JorD1]

We were using X1900 I think, the one available on openrails.org

[APK-LVDZ]

Signals is no longer developed?! :ermm:

[gpz]

Is there a particular reason you feel like this?

[APK-LVDZ]

After December has no changes in signal working (6 weeks). We hope, will be prepared to make, even though similarly MSTS.

[James Ross]

 APK-LVDZ, on 21 February 2014 - 06:33 AM, said:

After December has no changes in signal working (6 weeks). We hope, will be prepared to make, even though similarly MSTS.

I don't think your evidence backs up your claim at all. Additionally, since December I can count:

• 8 bug fixes to signalling.
  
• 1 big new feature.

If you have any specific bugs or issues, please report them on our Launchpad bug tracker.

[APK-LVDZ]

Hello! I have a one question. How I can get the state of the junctions and signals, and then manually change their, if OpenRails is minimized to TaskBar? I want to make my program with dispatcher windows for my route. My problems are this: I do not know to write a code for OpenRails, I will write this program in Pascal language. I need to people, who helps me to write and read all states in special logging file.

Idea is this:
1. OpenRails will be write in special log file all signal states (block_clear or block_occupied, block_jn_obstructed not needed)
For example:
signal_ID:155_state_block_clear;
signal_ID:953_state_block_occupied;
2. In this file will write all junction_states (main route, side route)
3. Then my program read this log file, and work with data
4. Then, if a choose to switch junction, or opening signal, my program create new file with commands for OpenRails. For example:
junction_ID:456_to_main_route;
signal_ID:155_NORMAL_to_CLEAR_2;DISTANCE_to_APPROACH_3;
5. OpenRails read this file, and without dispatcher window change this signal aspects and route directions.
6. If file are readed and all is applyed, file will be deleted. For good working of hard disk, this files can be created by one for 5 seconds with all commands.

Very big supplication, help me! All problem are with my program and Your OpenRails communication. The Pascal language is very old language, but others I do not know. But this will resolve all problem with other countries signals, and helps to make the own dispatcher window. If my window will sets all aspects, then signall will be worked as it is necessary. This all are for multiplayer mode! Thank You!

[gpz]

One thing I don't understand: OpenRails has its own dispatcher window already, why do you want to write another one?

In case the problem is that is doesn't work well enough for you: What is exactly the problem with it? I think it would be better to support your working method in OpenRails officially.