Page 1 of 1
[v453000] [0.16.5] rail split block visualization graphical glitch
Posted: Mon Dec 18, 2017 2:42 pm
by MicFac
When building a rail constellation like shown in the picture and holding a rail signal, the train block visualisation shows the end of the (in this case yellow) block a second time right next to the rail (shown in the red box).
Re: [0.16.5] rail split block visualization graphical glitch
Posted: Mon Dec 18, 2017 2:53 pm
by Loewchen
I can reproduce this.
Re: [wheybags] [0.16.5] rail split block visualization graphical glitch
Posted: Mon Dec 18, 2017 8:47 pm
by MicFac
Still works in 0.16.6
Re: [v453000] [0.16.5] rail split block visualization graphical glitch
Posted: Wed Dec 20, 2017 6:05 pm
by Charlemagne
Here's another example in 16.6. I circled it in green. It happens every time this rail configuration occurs (I have it in a few places near where I am). There's another case where the endpoint is not duplicated but is still in the wrong location, but this happens with a slightly different rail configuration. Circled that one in green too. I'm attaching the save and the log as well.
- two straight rails
- Graphics bug.png (970.34 KiB) Viewed 7276 times
- one straight rail
- another example.png (658.48 KiB) Viewed 7276 times
Re: [v453000] [0.16.5] rail split block visualization graphical glitch
Posted: Thu Dec 21, 2017 10:34 pm
by MicFac
Still works in 0.16.7
Re: [v453000] [0.16.5] rail split block visualization graphical glitch
Posted: Tue Jan 02, 2018 11:10 pm
by MicFac
Still works in 0.16.12
Re: [v453000] [0.16.5] rail split block visualization graphical glitch
Posted: Wed Jan 03, 2018 12:55 am
by Rseding91
Thanks for the report. It's now fixed for the next version of 0.16.
Re: [v453000] [0.16.5] rail split block visualization graphical glitch
Posted: Thu Jan 04, 2018 7:12 pm
by MicFac
Rseding91 wrote:Thanks for the report. It's now fixed for the next version of 0.16.
The Bug still seems to work in 0.16.13.
Re: [v453000] [0.16.5] rail split block visualization graphical glitch
Posted: Thu Jan 04, 2018 8:01 pm
by Koub
But it is fixed for the next version of 0.16
Re: [v453000] [0.16.5] rail split block visualization graphical glitch
Posted: Thu Jan 04, 2018 10:55 pm
by MicFac
Koub wrote:But it is fixed for the next version of 0.16
So 0.16.14? Sorry but the bug still occurs in that version for me
Re: [v453000] [0.16.5] rail split block visualization graphical glitch
Posted: Thu Jan 04, 2018 11:05 pm
by Koub
Actually, it should have been corrected with 0.16.13 :
Fixed one of the curved rail segment visualizations wasn't aligned correctly. (55276)
However, the advantage of "Fixed for next release" is that it is always true
Re: [v453000] [0.16.5] rail split block visualization graphical glitch
Posted: Wed Jan 10, 2018 7:52 pm
by MicFac
Still works in 0.16.16.
Re: [v453000] [0.16.5] rail split block visualization graphical glitch
Posted: Wed Jan 10, 2018 8:10 pm
by Rseding91
MicFac wrote:Still works in 0.16.16.
?
No it doesn't. Delete your cropcache.dat and or atlascache.dat files.
Re: [v453000] [0.16.5] rail split block visualization graphical glitch
Posted: Fri Jan 12, 2018 3:02 am
by Sifu
Just to note for futur people having the same issue on futur versions:
The crop cache file name is actually
crop-cache.dat (which is found in C:\Users\
username\AppData\Roaming\Factorio).
I have yet to find the atlas cache file...
After deleting crop-cache.dat, the issue is still here for me on [0.16.16].
I have posted a new bug report earlier.
viewtopic.php?f=7&t=56499
Re: [v453000] [0.16.5] rail split block visualization graphical glitch
Posted: Fri Jan 12, 2018 6:50 am
by Rseding91
Sifu wrote:Just to note for futur people having the same issue on futur versions:
The crop cache file name is actually
crop-cache.dat (which is found in C:\Users\
username\AppData\Roaming\Factorio).
I have yet to find the atlas cache file...
After deleting crop-cache.dat, the issue is still here for me on [0.16.16].
I have posted a new bug report earlier.
viewtopic.php?f=7&t=56499
I see now. I fixed it in normal res but it's also broken in high-res. It's now fixed for high res as well in the next version of 0.16.