Closed redruin1 closed 2 years ago
Any entity that is within the bounding box of the CurvedRail
will throw the error despite being a valid location. This is similar to 2 since it is using an AABB collision box for a curved object.
Both CurvedRail
and diagonally placed StraightRails
now have correct collision boxes, so this should no longer be an issue. I think these were the only real offenders, so I'm going to tentatively close this issue, though if anyone finds more examples feel free to reopen.
There are a number of cases where
OverlappingObjectsWarning
s are issued to the user when they're not valid:StraightRail
orCurvedRail
entities overlap otherStraightRail
orCurvedRail
entitiesRailSignal
s orRailChainSignal
s are placed next to a diagonal straight rail (the collision box is not rotated 45 degrees because currently we operate exclusively with AABBs)Feel free to add more in the comments if you come across any.