Many things have been changed behind the curtain to bring OR back to work: Most significant:* OR supports the old AND the new MP protocol at the same time. As long as we still have old clients or clients running "visible to all" I leave the old protocol active. OR sees both types of clients and can chat to both at the same time. Please remember, you clients can only chat with clients using the same protocol.* OR support the new reception range feature that has been added to the MP protocol. If you zoom out, you will see clients from further away, max 2000NM radius, as defined by the MP protocol. You receive also their chat messages, so OR has its Chat Filter for range RNG back and enabled by default. To avoid, that your flightstripbay does not flow over, you can define your working range on the lower right of your radar screen. This setting filters the contacts in flightstrip and the visible chat message in RNG filter mode (right side, above Chat panel).

IMPORTANT: Your clients can receive your chat messages only, if YOU ARE IN THEIR reception radius. The FGFS clients will use the default 100NM radius. So they will not read your chat messages >100NM radius. Use FGCOM or mumble...

wagnerw wrote in Thu Mar 29, 2018 4:20 pm:....Please remember, you clients can only chat with clients using the same protocol.

Just to clarify[1]

If you are running FG2017.2 or later you should be able receive messages from any other MP user regardless of their protocol or FG version. 2017.1 clients will not receive your chat messages. This can lead to frustration and the feeling of being ignored.

If you are running FG2017.1 or earlier you will not be able to receive chat messages from clients in 2017.2 mode; although you will still see their aircraft.

2017.2 (or later) can chat freely regardless of the protocol in use; FlightGear will convert between the two.

----------[1] I say clarify, which is my intention, although often my explanations only serve to further confuse.