Jump to content

smytilineos

Members
  • Posts

    6
  • Joined

  • Last visited

  1. I have the same problem. I stop the profile after noting which USB device does not have the yellow caution sign as it should (I find it helpful to list devices in the Device Manager "by Container"). I then physically disconnect and reconnect these devices and then run the profile again. It always works for me and it's much faster than a reboot. Haven't found a better solution although I have tried.
  2. Hi again Home Fries! I noticed a problem with the Bf-109 warthog profile. The gear up LMFD button (should be LOSB17 with S3) was not working (it was selecting the aircraft I have assigned for the profile switching mode). I checked the code and you appear to have REMed out the lines for LOSB16 and LOSB17. I unREMed and it worked. Bug or me doing something stupid? Many thanks, Stefanos P.S. The UH-1H kneeboard button is still not working. Pressing LOSB20 produces DX26 (with modifier 30+31). I remapped and I'm ok but I still suspect this might be a bug...
  3. Sorry. Of course. The Huey. Warthog.
  4. Wrong mapping for Huey kneeboard activate Hi Home Fries, Am I right saying that the left MFD long-hold press for kneeboard activate is wrongly mapped?
  5. OK, I think I found the problem. With 2.5 and Easy Comms disabled, I had to remap the DX20 and the other keys to "UHF Mic press" and not the default "Comms Menu". Seems to be ok now.
  6. Hi Home Fries. First of all many thanks for your work. I fly with VR and the Warthog and find your commstate HOTAS shortcut as well as your consistent approach across modules very useful when you cannot see the keyboard! Since 2.5 I have a problem with comms on the F5. I have studied your discussion with Lorthirk but I have a feeling my problem is different. Whenever gear state is up (GSU), the comms switch (PTT down on the WH throttle) does nothing. When I go into the key assignments screens, I notice that two events are triggered, one is the DX20 button (on the virtual thrustmaster) and then immediately afterwards the keyboard command is also triggered (the ""). I presume this negates the comms menu and effectively nothing happens. I have tried removing the assignment on either side to see what happens but nothing changes. The only way to make the comms menu to appear is to switch to GSD and press the S3 button. Am I doing something wrong?
×
×
  • Create New...