Robson
-
Posts
8 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by Robson
-
-
Is there any way to tell which program can be blocking that hot key?
-
Hi all :)
I am trying to get old Aribus CDU from Flight Deck Solutions to work with JeeHell software and as advised on MyCockpit forum I am doing it through WideFS and ButtonKeys.
I've got all working except for one: F12 code 123.
In the WideClient.log I get:
15 Error: failed to register ButtonKey T126=123,8
And that happens only for this one. It does not happen on main server PC though when I tried it there. Can anyone advise me what can be wrong with it? This is the very last piece I need to call my cockpit fully functional :)Cheers,
Robert
-
Ok, it works now ;]
Thank you very much. For information update to 4.745 helped ;]
Regards,
Robert.
-
I use 0BB2, 0BB6 and 0BBA offsets, and according to FSUIPC log values are written (no error) and then read back to app but returned value differs from send one.
FSUIPC 4.60a.
That's part of log:
255468 WRITE0 0BB2, 2 bytes: 88 13 ..
255967 READ0 0BB2, 2048 bytes: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 36 04 ..............6.
255967 36 04 00 00 00 00 00 00 00 00 00 00 00 00 00 00 6...............
255967 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
255967 00 00 00 00 00 00 FF 3F 00 00 FF 3F 00 00 FF 3F .......?...?...?
255967 00 00 FF 3F 00 00 5B 84 01 00 00 00 00 00 00 00 ...?..[.........
255967 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
255967 00 00 00 00 00 00 00 00 00 01 00 00 00 00 31 31 ..............11
255967 3A 30 31 3A 35 33 00 30 30 2E 30 00 30 30 30 00 :01:53.00.0.000.
255967 00 30 30 2E 30 00 30 30 30 00 00 00 00 00 72 FC .00.0.000.....r.
255967 00 00 01 00 00 00 00 00 00 00 00 29 54 01 00 00 ...........)T...
255967 00 00 00 00 5A 00 00 00 00 00 5A 00 3B 01 00 00 ....Z.....Z.;...
255967 00 00 00 00 00 00 00 00 00 40 00 00 00 00 28 00 .........@....(.
255967 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
255967 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
255967 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
255967 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ................
Unfortunately I understand nothing from this beside that it writes it and reads somewhere.
-
Hi all,
I develop software for my homecockpit based on FSUIPC. Currently I transfer input from joystick via my app and FSUIPC offset to FS. It works like a charm in FS9 but I'm unable to set these values in FSX.
I can read every value and write some of them so this is not a connection problem. Also my app is working fine cause even FS-Interrogate cannot set for example aileron value.
I tried various things like reinstalling FSUIPC (of course clean install performed) and many others but I still have no idea whats wrong...
Maybe someone encountered similar problem?
Regards,
Robert.
-
It cheered me up it is possible. Maybe you are able to point me to some examples, tutorials or whatever that could help me with getting started.
Also another question: is it possible to generate mouse macro without keyboard shortcut? When I create mouse macro there is somekind of offset. Maybe it's possible for you to add option to run it via FSUIPC?
Regards,
Robert.
-
First of all - is it even possible?
I'd like to capture non-standard control change. An example: APU switch or FMC in Embraer 190 by Wilco. I would like only to capture it, then transfer to second machine and input to FS. All in FS2004.
Maybe there is somekind of offset responsible for user inputs in FS2004?
Thanks in advance,
Robert.
Problem with ButtonKeys on WideFS
in FSUIPC Support Pete Dowson Modules
Posted
Pete, I used this Windows Hotkey Explorer (free version): http://hkcmdr.anymania.com/
and found out that F12 is System debugger.
Also after you mentioned RegisterHotKey i jumped to documentation and found out that F12 is binded to system debugger by kernel. Luckily one can reassign it to different key using registry and then all works perfect. Thank you for pointing me in the right direction!
Link to page explaining how to reassign system debugger:
http://muzso.hu/2011/12/13/setting-f12-as-a-global-hotkey-in-windows
In short:
Of course a reboot is necessary after having set this registry key.
Now this is pretty much upsetting. But not all is lost. I tried to google for a way to disable the kernel from registering F12, but found instead the description of theHKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AeDebug\UserDebuggerHotKey registry key. Modifying this you can set the keycode (scancode) that is registered as a global hotkey for the debugger. By default it's value is zero (0x0), but you can set it to eg. 0x2F (VK_HELP) which is not present on most PC keyboards, thus you can free up the F12 key.