smsking Posted August 11, 2019 Share Posted August 11, 2019 When doing a long excavation / endless fissure excavation the waypoint for the excavators persist even after they are finished or destroyed, resulting in the map being filled with fake waypoints. If i remember correctly this bug has been in the game for well over a year now, and it makes doing excavation runs annoying, and confuses players. Please fix it Link to comment Share on other sites More sharing options...
CxLL Posted August 11, 2019 Share Posted August 11, 2019 This sounds like lag. How about some more detail such as whether you were playing alone or in a squad as well as, in case squad, whether you were the host or client of squad. Some visual evidence won't hurt either. Follow the reporting protocol written in the first post of the most recent megathread titled with the build name to see which information your report needs to contain in order to be considered a report. Link to comment Share on other sites More sharing options...
smsking Posted August 11, 2019 Author Share Posted August 11, 2019 (edited) 41 minutes ago, CxLL said: This sounds like lag. How about some more detail such as whether you were playing alone or in a squad as well as, in case squad, whether you were the host or client of squad. Some visual evidence won't hurt either. Follow the reporting protocol written in the first post of the most recent megathread titled with the build name to see which information your report needs to contain in order to be considered a report. it's not lag, i was in the squad but if you just do a quick google search you can find ppl having the same issue in solo too. I'm not gonna do another one hour run just to provide visual evidence for a bug that's this old, but i can link you another post as an example. I can't give more detail then this, because the bug is that simple: waypoint's don't dissapear. The bug used to happen to me often back when i did long runs with my friend a really long time ago regardless if i was the host or not. I just made the post because this recent run made me realize that they still haven't adressed this bug and it's really old and frustrating Edited August 11, 2019 by smsking Link to comment Share on other sites More sharing options...
Recommended Posts