On the Developer Q&A, I heard Sebastian Wloch say that there are so many use cases for testing that it’s difficult to reproduce bugs sometimes. Why not give us a function we can map to a key that lets us “report” what’s happening in the plane into a file we can attach to a bug report? Like when my AP starts porpoising my Citation, I can press a button and it begins “recording” the circumstances that exist in my environment (weather, plane telemetry, GPS coordinates, etc) and outputs a file to my desktop. I’m assuming (hope) that CTD’s are already reported to you automatically, if not we need that too! Just a thought.
3 Likes
That’s a very good idea!
1 Like
Excellent idea! I’m in!
1 Like
Hey,
it’s a good idea. To get your Idea recognized by the development, I suggest posting this another time in:
https://forums.flightsimulator.com/c/self-service/wishlist/163
There other users can also upvote your idea and it gets more present!
Happy landings!
1 Like
I suspect programing in that key stroke would consume hours of time the team could better use to fix the issues we are finding by the second. However, I think that is an excellent idea. It also would help if, the bug reporting procedure we were asked to follow outlined specific items they need to reproduce the problem. I suggested a standardized format via a suggestion I made, don’t know as we will see one. And it’s difficult to figure out if it’s something I did inside the sim, or is the sim just bucking like a bronc because of the rattlesnake on the ground I don’t see. Someone mentioned having Visual Studio 2019 installed on the PC to stop or somewhat mitigate CTD’s. I did that, but had only one CTD before. I turned up my Glass Cockpit refresh rate with no apparent change to the simulator, and don’t see if this made a significant change to frame rate.
Thanks for the redirect. I have done that now. Cheers!
1 Like
I hate to point this out, but X-Plane already do this - as soon as there’s a crash, a log file can automatically be sent to LR. It can also be attached to any other bug reports by the users, or (as it’s text format) used by the more savvy users to sort problems themselves.
I must say I am surprised if Asobo are trying to fix bugs without such a tool. I must presume they don’t take the trouble to occasionally look at their competitors forums, which I think is a big mistake.