![]() ![]() The releases from yesterday brought to light a couple issues that were lurking in the opensource code, and so today I sat down and went through the old changelogs to test everything once again. ![]() I did what I could to recreate the code for the open-source release, but I didn't have time to thoroughly test the results. In order to turn off crash reporting all you need to do is to set the SendCrashDump value in the TacOConfig.xml to 0.Īs I noted earlier, about a year ago I had a huge data loss in the TacO codebase that resulted in the wipe of the progress between builds #43 and #47. ![]() No identifying or GW2 account related information is sent (since the overlay doesn't have access to that anyway), however I'm anticipating that there will still be some, who'd like to opt out of sending crash info my way. The information that is sent is the TacO process dump file and the TacO log file of the crashed session. As crash reports from the overlay have been few and far between lately I don't expect there to be too many reports for now, this is more a convenience feature for me to track down any Schrödinbugs that may rear their ugly head. This system sends crash reports (basically the same information that has been logged before) into the cloud for easier sorting and analysis. In order to better be able to track unreported and rare crashes, I've integrated the BugSplat crash tracking system into the latest TacO build (#53). ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |