Just a heads up, can’t do a repro right now.
Tested on 5.6.1 f1 and 2017, think it slipped in after a previous edge collider fix for raycast edges or something, will check newest 2017 tonight but it’s definitely in 5.6.1
A bug report would be much appreciated.
I have managed to duplicate this. A bug report would be appreciated but isn’t essential now. I’m looking at this issue today and will get a fix out ASAP.
EDIT: I’ve just fixed the issue, will get it into the release pipeline ASAP.
A fix for this has just landed in 5.5.4p1 due for release on 14th June.
It’s also waiting in the queue for 5.6, 2017.1 & 2017.2 currently.
Thanks Melv, just got back to the main machine now… I guess a bit late! but thank you
I’m going to assume this affected collider.Cast and various other casts too (using collider.Cast here along with raycast).
No, this won’t affect cast functions. This fixes a regression in raycast against edge only. Anything else is a different issue. If you have problems there then a bug report would be great.