FSUIPC - Hotkey Problem

[Cruachan]

Hi,

Has anyone else noticed that the hot key combo for clearing the weather has stopped working in version 3.5 of FSUIPC? I use Ctrl+Shift+W

Mike

[aarskringspier]

Hi,

Has anyone else noticed that the hot key combo for clearing the weather has stopped working in version 3.5 of FSUIPC? I use Ctrl+Shift+W

Mike

Mine works perfectly well.

[Cruachan]

That's odd, but thanks anyway.

I've tried redefining the key combo but still no joy :(

Mike

[Cruachan]

Stranger and stranger :?:

After much experimenting I found the binding combo CTRL+SHIFT+R did the trick.

I have to assume that there was a conflict between the chosen FSUIPC assignment and FS9's keyboard assignment for CTRL+SHIFT+W = Cycle Chase View Forward. However, deleting FS9's assignment made no difference whatsoever. After making the change I exited FS9 and then restarted to ensure that the changes were written to FS9.cfg.

What is puzzling is the fact that I have always used CTRL+SHIFT+W for Clearing Weather and this change in behaviour has only recently become apparent.

Ah well, at least I have managed to resolve the problem, albeit without having found a satisfactory explanation.

In passing I noted that I have Powerstrip configured to use CTRL+SHIFT as the global modifier for several Hot key bindings. One in particular could have proven to be a bit of a pain while FS9 is running and that was the binding for restoring adapter defaults - CTRL+SHIFT+S. Not sure whether this has any effect in FS9 but I imagine this combo could be hit by accident with unexpected results!

FS9 sure keeps us on our toes :wink:

Mike

[peterhayes]

Hi Mike

You are correct in your assumption. If you have a key or axis assigned in FS04 then that assignment has to be matched exactly in FSUIPC for it work without conflicts. If it is NOT assigned in FS04 then you can use FSUIPC to assign the keystroke(s). I always make sure that any assignments in my fs9.cfg match both my devices.cfg and FSUIPC.ini wherever possible.

Regards

PeterH

[Pete Dowson]

Has anyone else noticed that the hot key combo for clearing the weather has stopped working in version 3.5 of FSUIPC? I use Ctrl+Shift+W

I use the same combination and it works fine for me. There's certainly been no changes in FSUIPC for that. It sounds like you have some other program grabbing that combo.

Regards

Pete

[Pete Dowson]

After much experimenting I found the binding combo CTRL+SHIFT+R did the trick.

I have to assume that there was a conflict between the chosen FSUIPC assignment and FS9's keyboard assignment for CTRL+SHIFT+W = Cycle Chase View Forward. However, deleting FS9's assignment made no difference whatsoever.

FS's own assignments are entirely irrelevant to FSUIPC because it intercepts the key messages before they get to FS's processing.

The only possible explanation is that you have some other program using Ctl + Shft + W as a hotkey -- the Windows hotleys facilities take priority and will steal them first.

In passing I noted that I have Powerstrip configured to use CTRL+SHIFT as the global modifier for several Hot key bindings.

I expect there's a Ctl+Shft+W in there somewhere, then.

Regards,

Pete

[Pete Dowson]

You are correct in your assumption. If you have a key or axis assigned in FS04 then that assignment has to be matched exactly in FSUIPC for it work without conflicts. If it is NOT assigned in FS04 then you can use FSUIPC to assign the keystroke(s). I always make sure that any assignments in my fs9.cfg match both my devices.cfg and FSUIPC.ini wherever possible.

Actually, for BUTTONs (only) you are correct, though you omitted to mention those. If button actions are defined in both FS and FSUIPC then both have effect -- FSUIPC has no way to stop FS seeing them.

For Axes you are not correct because FSUIPC does not handle axes at all -- all the "joystick" facilities in FSUIPC act on FS axis controls, which are the results of axis inputs via FS assignments -- therefore it is imperative that any axes you want are assigned in FS else they cannot result in the controls which FSUIPC processes.

For keypresses you are incorrect also, because FSUIPC actually intercepts all the keyboard messages before FS sees them, and if they are programmed in FSUIPC then FS never gets them.

I hope this is clear now.

Windows also provides a "Hot Key" facility (not used by FSUIPC), and this takes precedence over any programs awaiting keyboard input -- so other programs, like PowerStrip for example, can steal their allocated keypress combos before FSUIPC or FS sees them.

Regards,

Pete

[peterhayes]

Hi Pete

Many thanks for the explanation. With regard to the axes I meant to mean what you posted but obviously put it badly.

Regards

PeterH