VR device lost the second time VR is enabled – fixed!.Preview icons were actually our number one source of crashes! Preview icon generation is now finally Metal/Vulkan-ready.NVidia Macs work with Metal and MSAA Hackintosh users rejoice.I’ll be looking at the crash reports like a hawk to see if anything else is still exploding. These fixes cover approximately 100% of the known ATC crashes. ATC crashes (including null segments and friends) – four issues fixed. We fixed a lot of crashes in beta 5 and beta 6: If you are the author of such a file and you are mystified at what you did wrong, then by all means, contact us, and we will help you with the file formats. If the sim says a file is damaged, it means the problem with the file is clear enough for the sim to go “nope, that file isn’t cool” without a human here looking at it – hence there’s no need to report to us and no auto-report. This is not a bug, and you do not need to report it to us, unless you are the author of that pack. This does not mean we stopped supporting the scenery it means it was always going to crash, and now you can see where the actual problem lies. We’ve been ramping up validation of these problems, and in some cases, it may result in your being told that a scenery pack is damaged. The sim was exploding during load, and nothing in the Log file could be traced back to the source problem. One thing I found was hard-to-diagnose crashes due to corrupt scenery files. Last week we went through the crash reports with a fine tooth comb. If you are on Windows or Linux and the auto crash report form does not come up, please try removing all add-ons before filing your bug report–plugin crashes will not bring up the auto crash report form. In these cases, X-Plane will suggest that you report the bug to us, which you can do via the bug report form. The auto crash report feature does not work on Mac, so those users will still need to file a bug report manually, and they should make sure to include Apple crash report. If you send the auto report, you do not need to send us an email via the bug report form as well! As the graphs show, report volume is high and we don’t this duplicate information. This is probably the most useful thing you can do if X-Plane 11.50 crashes. If you are on Windows (and most of you are) X-Plane will sometimes offer to auto-report crashes. With beta 6, we have tried to refine the error and crash reporting when something goes wrong, and fix X-Plane’s on-screen recommendations. Reporting Crashes, Finding Crashes, Fixing Crashes X-Plane 11.50 is the first version of X-Plane where we can get a complete diagnostic picture of the sim on a user’s machine, and I think that’s going to really be great for debugging.īut first…crashes. But we’re not there yet.Īs you can see from the graphs above, we’re still on step one: fix all the crashes! We have lots of ideas for improving VRAM and performance, and great tools to examine your particular case if you are seeing problems. org thread where people were questioning how much VRAM Vulkan would require. I’ve seen a lot of commentary on performance issues in the blog comments, and one user mentioned an. Fix crashes and “that’s not right” bugs.As I said in a previous post, our order of operations is: If you read the 11.50 beta 5 release notes (and you should if you are filing bugs or commenting on the state of the beta), what you’ll see is a lot of crash fixes. So with those graphs in mind, let’s talk about where we are at with the beta. Of these reported bugs, over 500 are in the category of “it crashed” or some other similarly catastrophic, bad thing happened. That’s bug reports and they’re up something like 1000% – we have received close to 1800 reports since then. Here’s one more graph: Bug reports per day – the big spike is X-Plane 11.50 beta 1. The silver lining is that the crashes we have been collecting are very very informative so it’s been a really great data stream. A lot of people are really excited to try the 11.50 beta even though it’s early and unstable and.The gap in the timeline at the end is when our crash reporter temporarily was shut off for exceeding quota! From this I can take derive two take-away points: That’s a graph of auto-reported crashes over time – the big spike up is April 2nd when 11.50 came out. But before we get into beta 6, a few graphs: Crash reports per 12 hours – the big spike is X-Plane 11.50 beta 1 We had spent a week very carefully trying to improve stability and then… beta 5 exploded on the launch pad. I had a very nice post written up last week on the state of beta.
0 Comments
Leave a Reply. |