Page 1 of 1
[16.0] Cliff/belt bounding box / sprite overlap (MR)
Posted: Wed Dec 13, 2017 1:53 pm
by LotA
I know it's not technically a bug, but look at this :
- fac16.gif (621.12 KiB) Viewed 3380 times
Isn't something wrong? ^^
On this picture, I've detailed a bit more :
- fac16.jpg (368.14 KiB) Viewed 3380 times
Yellow circles doesn't shock me outrageously but yet, look rough and might need tweaks for a full polished game, maybe simply put the belt sprites on top of the cliff sprites could do it
Red square should definitely not be buildable
Re: [16.0] Cliff bounding box / sprite overlap
Posted: Wed Dec 13, 2017 3:58 pm
by Rseding91
Thanks for the report. This isn't likely to change as it would make interacting with cliffs incredibly annoying.
Re: [16.0] Cliff bounding box / sprite overlap
Posted: Thu Dec 14, 2017 12:47 am
by devilwarriors
why not just always put the cliff z-index under building?
Re: [16.0] Cliff bounding box / sprite overlap
Posted: Thu Dec 14, 2017 12:39 pm
by Engimage
devilwarriors wrote:why not just always put the cliff z-index under building?
This seams like an obvious solution that would at least make things not look dumb
I'm not sure about how it is now but in 0.15 same problem was with doodads that could mass spawn and literally cover rails so you could not see them.
Re: [16.0] Cliff bounding box / sprite overlap
Posted: Thu Jan 25, 2018 5:03 am
by Lostidiot
I was about to post a bug about the same issue.
Was very strange when encountering being able to build over this east facing cliff and all others behaving as expected.
I understand leaving some of the spots in the earlier post with bits of rock, but this feels left out.
I assume it's related to the south east red boxes from LotA's post.
Rseding91 wrote:Thanks for the report. This isn't likely to change as it would make interacting with cliffs incredibly annoying.
I thought they are supposed to be annoying? Hence the cliff explosives, to cherish revenge when you later research them.
Edit: Building a bit further...
This collision box was unexpected. But I'd prefer the earlier one blocked as higher priority over this one being build-able.