#[✓2.3.17] multiplayer stops auto signal detection for sensors

5 messages · Page 1 of 1 (latest)

shadow comet
#

Game version: 2.3.16
OS: Win

Steps to reproduce:

  1. Create a new game
  2. place a departure sensor on a station
  3. place auto signals on the station
  4. open multiplayer settings and for either steam or tcp/ip press open
  5. departure sensor will say "At least one signal must be auto signal."

Wrong behavior:
Whenever I open my game up for multiplayer, all departure sensors, routing sensors and relay sensors on auto-blocks will say "At least one signal must be an auto-signal" If I close the multiplayer server, the message is gone and I can configure them again. (The signals still work automatically with the configuration they have stored, it is just the interface that doesn't work)

Expected behavior:
No matter if a multiplayer session is opened, the sensors should always recognize that they have auto-signals.

Map:
Basel

image.png 📎 Basel_Test_Basel_08-00-01_679aa.mp.lz4 📎 Player.log
supple creek
#

It happens on every map btw

winter crowBOT
winter crowBOT
vivid heron
#

@shadow comet as usual, it is caused by other fix: FIX: Signal was linked to Sensor in LinkPhase1, eventually before linking of the nodes en route to the signal -> TowardsPointOnDeterministicPath failed

But now already fixed in the #🧪︱unstable-version :

FIX: Unable to configure sensors in multiplayer due to false-negative check result
BUILD: 2.3.17