- All Feedback
-
Bugs/Crashes
0
Fixed
Discovery issue with specific WayStat
The WayStat at Lat 283.07, Lon -6.4651 triggers the discovery event only if looked at from certain directions and being very close (a few meters) to it. From any other direction you can walk right up to it and it won't get discovered until you walk around it to find the right spot and distance.
I noticed this at a few times but since it's not possible to test once discovered, I wasn't quite sure about it until now.
Customer support service by UserEcho
I found another one with a similar issue at Lat 283.072, Lon -6.4969. It also has some "blind spots" from where it doesn't trigger even from up close and needs to be circled around.
I think ones that are on top of very steep, cone-like terrain features are more prone to this.
I'm having a hard time recreating the issue, but I believe the raycast might be getting intercepted in some cases by the doors to access the components. I've added the doors to the allowed collider list to trigger the discovery, so I'm hoping that was the main issue. You'll have to let me know if you have more difficulties with these or other waystats after public release of 0.61.