OnCourse Software

Good you moved the thread

I am afraid this still isn't working. I have the Hotkeys set to H and L and I tried over and over during my last flight to get a descent instruction., I press 'L', holding it down, immediately press '5' and hope that the pilot will request to descend by 5000' (and that ATC will confirm). But that never happens. The pilot requests to descend (with 'L') to "flight level xxx", where xxx is always the altitude of the aircraft at the moment I hit the keys.

I also assigned this macro to one of my keypad keys -

" 'L' key; '0.05" delay; '5' key; '0.05" delay; Release '5' key; '0.05" delay; Release 'L' key

That way I am sure all the keys are being used. And if I put the focus onto an open txt file, 'L5' is quickly printed. But in the sim, the result is the same as above, the pilot requests the altitude at which the aircraft happens to be currently flying.

I only hope that the log reveals why I can't get this to work It can't be of my own doing (surely??)...

M.

Hi Martin, i can assure you 100% the keying sequence works. Some users find it difficult to get used to initially but usually master it.

The only thing I can't guarantee is if it works with Xplane, because of course that doesn't use fsuipc and that's what handles the hotkeys.

I haven't had chance to check your log yet but will do so later today... I don't however expect it to show me much if the keys aren't being detected. I'll get back to you when I've checked

OK Dave, I'll look back later.

The reason I had changed some of the hotkeys became clear when I was setting up a flight to Philadelphia today - 'KPHL'. I sometimes have to enter the ICAO code via my keyboard, and as I enter the last two letters, 'H', 'L', PF3 reads it as an input of course. I must have decided the easiest way was to change the PF3 key - but the exact whys and wherefores are now lost in the mists of time!

The beta you encouraged me to install seems great, by the way! Haven't run into any problems at all which could be related to it.

Quote:

The beta you encouraged me to install seems great, by the way! Haven't run into any problems at all which could be related to it.

Thank you And there was nothing in your log to indicate any problems... the hotkeys were not detected and therefore not logged

OK, thanks for checking: I suppose that the XP version of FSUIPC isn't working for that function.I've gone back to the 'turbulence' descent/climb option.

Oh, there is one change I have noticed with the beta - the VCP sets the radio frequencies, but is no longer setting the squawk code at clearance (I get the reminder to set it as I start my taxi!). Maybe this has been reset by the update and I have to re-enable it somewhere in Options?

Oh, that's interesting about the squawk... I'll check that out. Thank you

Hi Dave... Just to report that the transponder is still not quite back to how it used to be. I get an instruction to check my transponder literally only seconds after I have just been given clearance and a squawk code. (And, as I reported, the VCP no longer sets the squawk code, I have to set it manually in all aircraft; but you already know that! Did you locate the problem?).

The transponder nag fix is in interim version 3.19.10 and you're using 3.19.6

Haven't checked the other issue yet but I will

Quote:

The transponder nag fix is in interim version 3.19.10 and you're using 3.19.6

Ooops, I'll grab the update now