I am a paying customer who was only providing the information which the developer needs. In any ticket system i attach a log and the steps to reproduce the issue. I didnt do complete research on this topic because I'm reporting a bug, not taking part in a history lesson. Truth be told, when i first saw that this update was being released with two pages of fixes and new options i knew there would be bugs. It just comes with the territory. so for the first week i did read up on all the bugs. I did NOT DL the 1.6 update because of my prior expierences. I knew that within a week or so, there would be a hot fix. And i was right. So i downloaded this aircraft today, did a single flight and found what i figured would be a new bug since the hotfix. What i did search for was the needed information for reporting bugs. The developer has a post referencing this. Where he says "you start a separate thread for that particular issue". I did this. I wasn't looking for a fix. I was reporting a problem. If you have a written protocol on the steps of reporting a bug which includes one doing a ton research first, please direct me to that documentation, I'd love to see it.
If you don't want me or another customer to be offended by your comments, then maybe post your thoughts on this issue in a new post and not part of mine. It comes across as demeaning even if you are not intending it to be.
Valued customer?
Dave