Bug reports are focused on a single repeatable, reproducible (by others) defect in order to qualify being considered by the Dev Team. This report has too many aspects to achieve the above. Please resubmit or edit, focusing on a single aspect, and submit reports for each distinct defect you want to raise. A focused title that tells the reader exactly and succinctly what the defect is about is also helpful. Thanks.
Respectfully, I’d request that the dev team prioritise comprehensive fault logging and report back to base for all crashes. That way they can aggregate, identify and prioritise fixes.
What you see here is an exasperated and frustrated community floundering in the dark with recalcitrant software that is routinely broken: if it continues people will abandon the software, as i have for months at a tome in the past because it’s just too painful to spend 4 hours troubleshooting for 1 hours broken flying.
USB handling, memory management errors, poor mod handling, conflicts with gpu drivers… any and all of these are problems and yet we see people peddling snake oil fixes and blaming completely blameless and otherwise stable hardware. THIS SOFTWARE IS BROKEN.
That’s not the purpose of the bug report process being discussed here. This is to report specific, repeatable bugs that have not already been reported, using the template enclosed.
Please see this post to understand proper use of this subforum.
In the meantime, this report as filed by the Topic Author remains inadequate to address anything. If the Topic Author wishes to refile, we’ll be happy to reopen it.
Thank you using the Bug section, using templates provided will greatly help the team reproducing the issue and ease the process of fixing it.
For anyone who wants to contribute on this issue, Click on the button below to use this template: