[0.14.22] 'Closed' rail signal doesn't read its state
Posted: Sat Apr 01, 2017 9:05 pm
by Avezo
I recreated the issue in smaller save file in attachment, rail signal is set to work both as 'close' and 'read', meant to close upon circuit condition and send its state to color lamp so it's more visible. It doesn't output anything to the lamp when 'close' conditions are met. It does output green signal otherwise. It should output red signal when closed, because that's how 'read' mode works for signals.
0.006 2017-04-02 19:03:25; Factorio 0.14.22 (build 25342, win64, steam)
0.006 Operating system: Windows 10 (version 1607)
0.006 Program arguments: "C:\Program Files (x86)\Steam\steamapps\common\Factorio\bin\x64\Factorio.exe"
0.006 Read data path: C:/Program Files (x86)/Steam/steamapps/common/Factorio/data
0.006 Write data path: C:/Users/Radek/AppData/Roaming/Factorio
0.007 Binaries path: C:/Program Files (x86)/Steam/steamapps/common/Factorio/bin
0.056 System info: [CPU: Intel(R) Core(TM) i3-5005U CPU @ 2.00GHz, 4 cores, RAM: 8107MB]
0.059 Display options: [FullScreen: 1] [VSync: 0] [UIScale: 100%] [MultiSampling: OFF] [Screen: 255]
0.061 Available display adapters: 1
0.061 [0]: \\.\DISPLAY1 - Intel(R) HD Graphics 5500 {0x05, [0,0], 1366x768, 32bit, 60Hz}
0.062 Create display on adapter 0. Size 1280x720 at position [33, 6].
0.139 Initialised Direct3D:[0] Intel(R) HD Graphics 5500; driver: igdumdim64.dll 20.19.15.4531
0.152 Video memory size (dedicated video/dedicated system/shared system/available): 128/0/4053/4092 MB
0.211 DSound: Starting _dsound_update thread
0.211 DSound: Enter _dsound_update; tid=1780
0.212 Device reset internal.
0.219 Desktop composition is active.
0.220 Graphics options: [Graphics quality: normal] [Video memory usage: high] [Light scale: 25%] [DXT: false]
0.382 Loading mod core 0.0.0 (data.lua)
0.404 Loading mod base 0.14.22 (data.lua)
0.612 Checksum for core: 1291735968
0.612 Checksum for mod base: 786624017
1.371 Info PlayerData.cpp:55: Local player-data.json available, timestamp 1491152530
1.372 Info PlayerData.cpp:60: Cloud player-data.json available, timestamp 1489695541
1.617 Initial atlas bitmap size is 8192
1.640 Created atlas bitmap 8192x8189
1.641 Created atlas bitmap 8192x2778
1.641 Created atlas bitmap 4096x968
1.641 Created atlas bitmap 4096x3652
16.410 Sprites loaded
16.410 Convert atlas 4096x968 to: trilinear-filtering
16.447 Convert atlas 4096x3652 to: mipmap
17.129 Loading sounds...
19.364 Custom inputs active: 0
19.419 Factorio initialised
33.365 Loading map C:\Users\Radek\AppData\Roaming\Factorio\saves\Problem2.zip
33.431 Info Scenario.cpp:152: Map version 0.14.22-0
35.877 Checksum for script C:/Users/Radek/AppData/Roaming/Factorio/temp/currently-playing/control.lua: 1057114497
70.515 DSound: Stopping voice
70.515 DSound: Joining thread
70.518 DSound: Exit _dsound_update; tid=1780
70.518 DSound: Waiting for voice to stop ... signaled
70.519 DSound: Joined thread
70.519 DSound: Destroying thread
70.519 DSound: Thread destroyed
70.519 DSound: Releasing buffer
70.519 DSound: Voice stopped
70.519 DSound: Deallocating voice
70.519 DSound: Deallocated voice
70.620 Steam API shutdown.
70.624 Goodbye
Re: Circuit 'block' rail signal broken and breaking pathfinding
Posted: Sat Apr 01, 2017 9:19 pm
by Loewchen
Boil it down, upload a save with the character next to a signal not working as you consider to be correct, describe what state you want the signal to be in and why.
Re: [0.14.22] 'Closed' rail signal doesn't read it's state
Posted: Sun Apr 02, 2017 5:18 pm
by Avezo
Edited and clarified from previous submission.
Re: [0.14.22] 'Closed' rail signal doesn't read its state
Posted: Sun Apr 02, 2017 5:37 pm
by Loewchen
Avezo wrote:It should output red signal when closed, because that's how 'read' mode works for signals.
That is not correct.
pic
Fac_signal_bug.png (300.04 KiB) Viewed 2376 times
Re: [0.14.22] 'Closed' rail signal doesn't read its state
Posted: Mon Apr 03, 2017 2:38 am
by Avezo
But why?
Re: [0.14.22] 'Closed' rail signal doesn't read its state
Posted: Sat Apr 08, 2017 2:27 pm
by biliskner25
Possibly to prevent feedback and infinite loops between connected signals, not a bug but a design choice.
Workaround for you could be to change close condition to Red signal instead, or use a decider combinator to output red on close condition