August 19, 20196 yr Commercial Member I've not had time to fly with P2A for a while, but i've been keeping it updated. I'm on 2.6.0.0_x64_R3. Today, first use for a long while, the Say It short cut keypress I've assigned (F2) no longer works. It makes no difference if I clcik on P2A first, to give it focus, or not. I can only use if by clicking on the button in the P2A window. Pete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
August 19, 20196 yr Commercial Member Pete, Did you try clearing it and resetting on the Btns tab? Something might have caused the setting to be lost in the AppConfig file. Or, are you using the SayIt+ Window? If so, I think I know what might have broken the HotKey. Dave
August 19, 20196 yr Author Commercial Member 1 hour ago, Dave-Pilot2ATC said: Did you try clearing it and resetting on the Btns tab? Something might have caused the setting to be lost in the AppConfig file. Isn't the on-screen showing what was read from the config/AppConfig. Here's what's it the AppConfig.xml: Quote <AppSetting> <Name>SayItKeyCodeText</Name> <Value>F2</Value> <LastChanged>2018-04-07T10:09:39.7135558+01:00</LastChanged> </AppSetting> <AppSetting> <Name>SayItKeyCode</Name> <Value>113</Value> <LastChanged>2018-04-07T10:09:39.7135558+01:00</LastChanged> </AppSetting> <AppSetting> <Name>SayItKeyMod</Name> <Value>0</Value> <LastChanged>2018-04-07T10:09:39.7135558+01:00</LastChanged> </AppSetting> <AppSetting> <Name>SayItHotKeyEnabled</Name> <Value>true</Value> <LastChanged>2019-03-21T09:55:17.1808619+00:00</LastChanged> </AppSetting> 1 hour ago, Dave-Pilot2ATC said: Or, are you using the SayIt+ Window? If so, I think I know what might have broken the HotKey. Er ... I don't think so. I don't go near P2A once the flight Plan is loaded and filed. I'm then in the cockpit, away from that PC. P2A is left in its normal default-looking state, but with the flight plan showing. The "SayIt" button which works is the one above the PTT button, but I can't reach either from inside the cockpit. I use buttons on the Yoke which are assigned to give keystrokes on that PC (press ... release), sent via WideFS. PTT works fine. SayIt used to. F1 is assigned to PTT, F2 is assigned to SayIt. F1 works via WideFS and via the PCs keyboard, but F2 doesn't, with either. And it is not a focus problem. Maybe something is stealing F2 -- I can try assigning a different key and checking via the PC's keyboard. I'll do that in the morning. If you think of anything else, please let me know. Thanks. Pete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
August 20, 20196 yr Author Commercial Member Yes, something is 'stealing' F2! This is so even on a fresh boot with only P2A running. There must be something I've installed which is loading in the background and doing this. i'll check. Anyway, I re-assigned SayIt to the F10 key, and so far so good ... Pete Win10: 22H2 19045.2728 CPU: 9900KS at 5.5GHz Memory: 32Gb at 3800 MHz. GPU: RTX 24Gb Titan 2 x 2160p projectors at 25Hz onto 200 FOV curved screen
August 20, 20196 yr Commercial Member Thanks for the update Pete. Glad you got it working again. Dave
Archived
This topic is now archived and is closed to further replies.