I still think you should try moving manual crash reporting into the beta software itself. It may relieve you of the tediousness of telling people not to post bugs here. You could even have the bug reporter as a cockpit control with a flashing red arrow pointing towards it :0). Ok, i jest…….but…….

Thanks Ben!

But I’ve seen even more strange things with HDR settings box. While trying to restore my system settings, I enabled HDR and when I tried to set FXAA, i noticed a whole bunch more options. Like FXAA ONLY and then FSAA AND FXAA on at the same time,for all the setting levels. I thought WOW….. Here is a chance to REALLY test mthe capabilities of my GPU, but I set it at FXAA 2 and closed the window. The sim crashed to desktop before I could return to flight. I went back to that menu to get a screenshot after the crash and the options had magically reverted back to what they show for beta 5. I know this is not the place to report bugs, and I’ll report that and numerous others I’ve seen in beta 6 if you’d like me to, but I thought i’d pass this on as info after I read your post about this build being porked.

FWIW, until beta 6, with a few very minor exceptions the 10.20 beta series has been pretty solid for me on my Mac Pro.

Anyway, looking forward to beta 7.

This is not the right place to report bugs. Please use the bug report form, under “useful links” to the right! Thanks!

I use PilotEdge ATC on a iMac 10.8.2 with the VSProPlugin.xpl v0.7.7 – in x-plane 10.10 it works still perfect. Since 10.20 beta 6 (and now 7) I had problems with the communication. I try to use it in 32 bit mod, the plugin starts and I can configure it. I hear the ATC but he is not able to understand me – he hear something but it is not readable. When I test my mic in OS it works perfect. For me it is a issue with 10.20 beta – since I had installed it I had the problems.