Jump to content

Battle of SMK - Direct Button Mapping Project


Lipfert

Recommended Posts

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!

 

 

 

Link to comment
Share on other sites

  • 1 month later...

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!

Link to comment
Share on other sites

  • 5 months later...

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.

Link to comment
Share on other sites

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 !

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
×
×
  • Create New...