Lipfert Posted July 5, 2018 Report Posted July 5, 2018 Alte Kameraden, As many of you know that fly with me, I've been having a problem with my control mappings freezing in game. Even after a fresh install, with Win10 it's still happening. Pretty sure it's related to modifiers Alt - Ctrl - Shift - Win. So I'm going to try and run Target with no keys mapped, with Combined Controls and no actual keybinds. Direct input, of course I'll need to decide which bloody controls are backwards per plane. Hoping to get a full day on this during the weekend. S! Klaiber 1 Quote
Lipfert Posted July 12, 2018 Author Report Posted July 12, 2018 I gave up on this, really wish we could load a profile. Quote
Klaiber Posted July 13, 2018 Report Posted July 13, 2018 Which game are you have problems with? Or is it all of them? Quote
Lipfert Posted July 14, 2018 Author Report Posted July 14, 2018 Which game are you have problems with? Or is it all of them? Just il-2 Sturmovik, I gave up on this for now. Quote
Klaiber Posted July 14, 2018 Report Posted July 14, 2018 I'm sorry to hear that you had so much problems. Quote
Lipfert Posted July 15, 2018 Author Report Posted July 15, 2018 Are you not flying BOS at all? Vonrd, Still flying, what I tried to do was either use direct mapping or single digit only. The big issue is the different aircraft and certain controls being backward for certain functions. S! Quote
Lipfert Posted August 31, 2018 Author Report Posted August 31, 2018 Kameraden, I'll be starting over on this, figure I'll run Spad.neXt as a direct button mapping for the controls. Will keep TARGET off completely and see if it keeps happening. For now, I'll bail on the VR side of it, as it's makes the process of mapping really slow. So frustrating...... S! Quote
Klaiber Posted August 31, 2018 Report Posted August 31, 2018 Have you found others with the same type of problem? Lipfert 1 Quote
Lipfert Posted August 31, 2018 Author Report Posted August 31, 2018 Have you found others with the same type of problem? It's always been an issue, think a few have had the same. Quote
Britchot Posted February 25, 2019 Report Posted February 25, 2019 Lipfert, not sure if you're ready to revisit this, currently. Recently, I made a new TARGET profile for BoX. I had issues with modifier key-bindings and found the solution to be to add a delay. From the manual: D() Delay command If you insert a simple D() in your CHAIN, you will place the default delay duration between your 2 events. You can define your own Delay duration by filling the () with the duration of your choice in milliseconds. MapKey(&Joystick, H3U, CHAIN(PULSE+'a', D(), PULSE+ 'b')); When testing this code with the Event Tester, you will find that “a†is pressed and then released, and then “b†is pressed and released. As the Delay sets the time for the first key to be released, you can create CHAINs with lots of keystrokes and combo keystrokes. Remember, if you want to separate the keystrokes pulses, use a Delay. Lipfert 1 Quote
Lipfert Posted February 25, 2019 Author Report Posted February 25, 2019 Lipfert, not sure if you're ready to revisit this, currently. Recently, I made a new TARGET profile for BoX. I had issues with modifier key-bindings and found the solution to be to add a delay. From the manual: I did a fresh direct HID profile without running TARGET. Still have the original, might test it when I get a minute. At the moment all my flight gear is unplugged, driving stuff setup instead. I need a better setup ! Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.