Hello Everyone,
We know this issue has been disruptive, and we want to thank you all for your patience while we’ve been investigating and working on it. Our team has made progress in narrowing down the possible causes, but we’re not quite at the finish line yet. This one has been particularly tricky, since, despite numerous attempts, we haven’t been able to reproduce it in-house.
Many of you have proposed rolling back to a previous build to resolve this issue. We’ve also considered that, but ultimately determined it is not feasible in this case. Our goal is to offer everyone the benefits of a long-term stable fix, and that requires focusing on identifying the root cause in the current build. We wouldn’t want to accidentally reintroduce this behavior later on.
To help us get to a resolution faster, we’re planning to add debugging code in the next Early Access build. If any of you are interested in joining Early Access to lend a hand in pinpointing the issue, please let us know. Your feedback could make a huge difference.
We’ll continue to keep this thread updated as we move forward, and we truly appreciate the time and effort many of you have already put into reporting your experiences. Your input has been key in getting us this far, and we’re committed to getting this resolved.