OnCourse Software

The missing Local AcarsX was displaying off-screen and was not corrected by the new 'Reset' feature which resets some of the currently saved PF3 window positions. By a combination of jiggery and pokery, switching back into Windowed Mode etc, I eventually got the white blank taskbar image of the Local AcarsX window to become a black image which meant I could then right click it, select 'Move' and use arrow keys (or something like that) to drag it back onto a screen.

I still cannot display the HotKeys window in either Windowed or Full Screen mode. I get the "bing" of Hotkey recognition but no window opens. I can see its position in Display.ini and have edited that a couple of times, swapping its position with those which work fine for the [Acars_Window] and [Caption_Window] but no joy. In Adv Options for P3D and MSFS I have "Use PF3 Hotkeys Window" checked and Delay = 0.

I also tried editing these lines in PF3.ini:
[frmhotkeys]
LeftPos=-1860
TopPos=23535

to match the Display.ini positions:
[Hotkeys_Window]
LeftPos=1000
TopPos=500

but no joy.

Debug_monitorlog file attached.

Please can someone suggest how I can get HotKeys window to display.

I see by your reply to another post this is now working?

Sort of i.e. providing I switch to Tower before C/S T.

Is there a logic to that? I had assumed C/S T would work anywhere, including at departure parking.

It certainly should open whatever facility you're tuned to. I saw your explanation in the other thread but you didn't include your log file, which would be useful to see if you can recreate the issue as you described.

Dave,

Log file attached for last flight yesterday, EGCCEGNM. I just tried again, different airport/plane/flight plan, LGAVLGSK. Same thing. Whilst initially tuned to Clearance, C/S T did not respond. When I swapped to Ground, C/S T opened up the Hotkeys window with Ground options. When I swapped back to Clearance, the Hotkey window remained open and showed the Clearance options.

Hope this helps.

If I read it correctly this log shows that all waypoints in the flight plan were marked as Oceanic - was that intentional?
I don't know for sure, but that may well be interfering with standard ATC working.

Cheers,
Martin

Thanks for your reply Martin. I'm not familiar with Oceanic procedures so no, it wasn't intentional. I've looked through the two flightplans mentioned in my last message and can't see any reference to Oceanic. I've attached them below. I also compared my flight plans created with Navigraph against some I created with Little Navmap and can't see a signifciant difference. Please can you tell me in what way they are marked as Oceanic.

For what its worth, when I Select a Flight Plan in PF3, I am not clicking on "Define Oceanic Airspace" and I can't see anything else in my PF3 Options that relates to Oceanic.