Page 7 of 7

Re: Integrated ATIS for Pilotedge

Posted: Thu Feb 07, 2019 6:46 am
by Marcus Becker
Thomas_Horn wrote:... would save a lot of CO2 emissions :)
Not to mention pennies.

Re: Integrated ATIS for Pilotedge

Posted: Thu Feb 07, 2019 7:48 am
by yajna
It's out?? That's awesome!

Now if only FlightFactor would fix the 757 radio so you could listen to both COMs simultaneously...
Ah well, I guess I can ask permission to change freq.

Re: Integrated ATIS for Pilotedge

Posted: Thu Feb 07, 2019 8:19 am
by Kevin_atc
yajna wrote: I guess I can ask permission to change freq.

Try to time it with a frequency change. A good time to do it (in an airliner since you referenced the 757) is during the change from center to approach. Even if you’re flying a smaller GA airplane, you can go grab the ATIS quickly as you get a handoff to approach as you near the airport. If you do this, it’ll save frequency time having to ask the controller later on to get the ATIS.

Re: Integrated ATIS for Pilotedge

Posted: Thu Feb 07, 2019 9:35 am
by Keith Smith
yajna wrote:It's out?? That's awesome!

Now if only FlightFactor would fix the 757 radio so you could listen to both COMs simultaneously...
Ah well, I guess I can ask permission to change freq.
The stock audio panel in the Baron also behaves that way, only allowing you select one COM at a time. You can always map your own key or button press to enable or disable COM2 reception, though. Just search for COM2 in the command list, I'm sure it'll be fairly obvious.

Sorry about not having the release done. There was a time constraint to get the system launched (Wed), coupled with a very poorly timed business trip (Mon-Wed night) which precluded us from having everything in place to do the formal announcement at the same time as the deployment. Hence, it was quietly released (other than a hint on the facebook page on Tuesday which stated it'd be released the following day).

A formal announcement with all sorts of details is forthcoming. It'll be hard to miss.

Re: Integrated ATIS for Pilotedge

Posted: Thu Feb 07, 2019 10:58 am
by yajna
I tried mapping a custom key to a FlyWithLUA script that alters the dataref (sim/cockpit2/radios/actuators/audio_selection_com2) but something in the FF 757 code changes it back to 0. The same custom-key approach worked in other aircraft. I opened a ticket with FF support. Who knows, maybe they'll fix it eventually... in the meantime, I'll try to grab the ATIS before switching to approach controller.

Re: Integrated ATIS for Pilotedge

Posted: Thu Feb 07, 2019 11:05 am
by sono
Thank you to everyone involved in making this happen.