| OnCourse Software http://www.ocs-support.co.uk/forums/ |
|
| Airport initial contact error http://www.ocs-support.co.uk/forums/viewtopic.php?t=4159 |
Page 1 of 1 |
| Author: | JStegman [ Sat Jan 21, 2023 10:50 am ] |
| Post subject: | Airport initial contact error |
| On VFR flight plan - KLBE - KAGC Approach turns me over to tower Switch to tower freq. Press the 1 Hotkey My radio get switched to departure freq. of airport (119.35 - not from Com 1 standby) - even when flying to another airport - KAGC - KLBE for example Logs attached Thanks |
| Author: | Dave March [ Sat Jan 21, 2023 4:27 pm ] |
| Post subject: | Re: Airport initial contact error |
| Sorry but I'm not sure why you think anything was wrong with this flight as it all seems fine to me. As for your radios changing have you check you don't have any pilot assist radio options set in MSFS? |
| Author: | JStegman [ Sun Jan 22, 2023 10:01 pm ] |
| Post subject: | Re: Airport initial contact error |
| This problem reoccured on another flight On approach - turned over to tower (KTTN) - tuned to tower freq. Used 1 hotkey and my Com 1 radio was switched to a different frequency - this time 123.8. I checked everyplace I could think of in MSFS to see if there is any programming of the 1 key for the coms but couldn't find anything - in order to be safe, i removed all keyboard commands to the COMS. I've attached the logs. Sorry if I am making some kind of error but i can't decipher what i may be doing wrong, John |
| Author: | pointy56 [ Mon Jan 23, 2023 4:30 pm ] |
| Post subject: | Re: Airport initial contact error |
| Hi John, I've taken a look at the log you provided and can see that you correctly tuned to the Tower on 120.7 (per handoff) but then the radio was retuned to 123.8 before you used Hotkey #1 so PF3 ignored the keypress. It accepted Hotkey #2 a little while later, as by then you had retuned to 120.7 I believe that this is an interaction from one of the MSFS Assist options, as Dave previously suggested - the MSFS ATC frequency for KTTN Approach is 123.8, but this was altered by PF3 to avoid a clash with KTTN Departure. Airport KTTN :N40:16:36.0861 W074:48:48.4990 184.74ft ILS: ITTN 111.30 Hdg: 58.5 , Flags: GS BC Slope: 3.00, "ILS RW06" in file: Official\Steam\fs-base-nav\scenery\0302\NAX28170.bgl COM: Type=8 (APPROACH), Freq=123.800, Name="PHILADELPHIA" COM: Type=13 (ASOS), Freq=126.775, Name="KTTN" COM: Type=1 (ATIS), Freq=126.775, Name="KTTN" COM: Type=7 (CLEARANCE), Freq=121.900, Name="TRENTON" COM: Type=9 (DEPARTURE), Freq=123.800, Name="PHILADELPHIA" COM: Type=5 (GROUND), Freq=121.900, Name="TRENTON" COM: Type=6 (TOWER), Freq=120.700, Name="TRENTON" COM: Type=3 (UNICOM), Freq=122.950, Name="TRENTON MERCER" FSM A/P KTTN, lat=40.276695, long=-74.813469, alt=184.74 Cheers, Martin |
| Author: | JStegman [ Mon Jan 23, 2023 5:10 pm ] |
| Post subject: | Re: Airport initial contact error |
| OK - I figured out what was happening. Even though I had ATC inactive in MSFS, it was still intercepting keystrokes and was interpreting the 1 hotkey as a request to change frequency (or whatever else it wanted the 1 key to do) which of course took me off the tower freq. thus I was unable to check in with the tower. I have "solved" the issue by deleting all the ACT panel keyboard assignments in MSFS. Thanks for taking the time to help me. John |
| Page 1 of 1 | All times are UTC+01:00 |
| Powered by phpBB® Forum Software © phpBB Limited | |