Page 1 of 1
[0.15.21] Tree clips rail
Posted: Tue Jun 20, 2017 1:04 am
by Jap2.0
I have a tree clipping my rail in this map. This map was started several months ago (probably 0.14?). I have rebuilt this rail and seen trains drive over it, and the tree is still not detected. I am running the latest experimental in steam (0.15.21) on 64-bit Windows 7.
System information: Intel Core i7 CPU 950 (4 cores, 8 threads) and 12 gigs ram.
If you need any more information, please feel free to ask.
Re: [0.15.21] Tree clips rail
Posted: Tue Jun 20, 2017 9:50 am
by Rseding91
That's currently working correctly. Factorio doesn't support non-rectangle bounding boxes which leaves that gap between the rails. Because the tree doesn't collide withe the rails the rails don't care that it exists and the train doesn't collide with trees so it ignores it.
We currently have no plans to change that because any changes around rail collision reduce normal game performance or break rail builds. If you want you can just mine the tree
For now this goes in won't-fix.
Re: [0.15.21] Tree clips rail
Posted: Tue Jun 20, 2017 11:09 am
by Jap2.0
Cool, thanks for the speedy reply.
I think I might keep it so I can have the novelty of having a tree in my rail
.
Re: [0.15.21] Tree clips rail
Posted: Thu Jun 20, 2019 1:04 am
by Jap2.0
Well,
72244 inspired me to check, and it looks like this can be moved to resolved
- Railtree.png (1.94 MiB) Viewed 2030 times
Also, this is coincidentally exactly two years after the initial report.
Re: [0.15.21] Tree clips rail
Posted: Thu Jun 20, 2019 1:13 pm
by Rseding91
Jap2.0 wrote: ↑Thu Jun 20, 2019 1:04 am
Well,
72244 inspired me to check, and it looks like this can be moved to resolved
Also, this is coincidentally exactly two years after the initial report.
72244 and
72146 are why I never "fixed" this.
Re: [0.15.21] Tree clips rail
Posted: Thu Jun 20, 2019 5:51 pm
by Jap2.0
Rseding91 wrote: ↑Thu Jun 20, 2019 1:13 pm
Jap2.0 wrote: ↑Thu Jun 20, 2019 1:04 am
Well,
72244 inspired me to check, and it looks like this can be moved to resolved
Also, this is coincidentally exactly two years after the initial report.
72244 and
72146 are why I never "fixed" this.
I will admit that I was a bit skeptical of the harm a few pixels' change could do at the time... now I am much more convinced.