Jump to content

Recommended Posts

Posted

I have a modifier in AH-64D assigned from the joystick as (joy-btn4) "pinky finger" and works well.  Now I am in P-51D and needing to assign the same (joy-btn4) "pinky finger" in that sim too.  I get a warning... "this key is in use".  Can I assign to both sims and not have a problem?

Posted

I would guess that btn4 is already bound to a function in P51, that’s the only reason I can think it would not let you make it a modifier


Sent from my iPhone using Tapatalk

  • Like 1
Posted
3 hours ago, gdotts said:

I have a modifier in AH-64D assigned from the joystick as (joy-btn4) "pinky finger" and works well.  Now I am in P-51D and needing to assign the same (joy-btn4) "pinky finger" in that sim too.  I get a warning... "this key is in use".  Can I assign to both sims and not have a problem?

Are you aware that you can give a modifier a new name when creating it i.e. adding it to the list of a module's modifiers?

This could be usefull in your case.

  • Like 1
Posted (edited)

Or

42 minutes ago, Trigati said:

I would guess that btn4 is already bound to a function in P51, that’s the only reason I can think it would not let you make it a modifier


Sent from my iPhone using Tapatalk

Or this! 100% agreed.

Sorry @Trigati

Didn't read your valid post carefully enough.

Edit: renaming the modifier does not help as long as the button is already used in the plane.

Edited by Tom Kazansky
  • Like 1
Posted

Hmmm... When you bind a button/key sequence that's already in use, it will tell you the conflict.
It doesn't do this with modifiers? I haven't used one in a long time so can't remember.

Cheers!

Sent from my MAR-LX1A using Tapatalk

Posted
17 minutes ago, MAXsenna said:

Hmmm... When you bind a button/key sequence that's already in use, it will tell you the conflict.
It doesn't do this with modifiers? I haven't used one in a long time so can't remember.

Cheers!

Sent from my MAR-LX1A using Tapatalk
 

If I understand the OP correctly, the warning occurs when the user tried to add the modifier to the list of the P-51 modifiers.

Imho this is not because he used the same modifier for his AH-64. I do that all the time without issues. It seems that the modifier button is already used with another keybind of the P-51 by default.

Which is not unusual for a button 4. I often see the first 4 or 5 buttons used by default when I come to a new module.

Posted
If I understand the OP correctly, the warning occurs when the user tried to add the modifier to the list of the P-51 modifiers.
Imho this is not because he used the same modifier for his AH-64. I do that all the time without issues. It seems that the modifier button is already used with another keybind of the P-51 by default.
Which is not unusual for a button 4. I often see the first 4 or 5 buttons used by default when I come to a new module.
Might have worded myself incorrectly, because I understand it the same way as you. I just thought that when you try to add a modifier, and that key/button already is in use as a single key/button, it tells you like OP describe, but also what it's used for.
I added some key/button in the UI Layer yesterday, not as a modifier though, and it listed every single module it was used in. Long list. Not sure if it listed what features it were used for, but I think it did.

Cheers!

Sent from my MAR-LX1A using Tapatalk

Posted
51 minutes ago, MAXsenna said:

Might have worded myself incorrectly, because I understand it the same way as you. I just thought that when you try to add a modifier, and that key/button already is in use as a single key/button, it tells you like OP describe, but also what it's used for.
I added some key/button in the UI Layer yesterday, not as a modifier though, and it listed every single module it was used in. Long list. Not sure if it listed what features it were used for, but I think it did.

Cheers!

Sent from my MAR-LX1A using Tapatalk
 

Yeah, roger that.

  • Like 1
Posted
On 8/26/2023 at 12:05 PM, gdotts said:

Can I assign to both sims and not have a problem?

Yes. Just clear any existing binding so the button is freed up to be a modifier. Modifiers like bindings (except the shared UI layer ones) are specific to that module only. 

  • Like 1

AMD Ryzen 5 5600X | Gigabyte RTX 3070 Gaming OC 8GB | 64GB G.SKILL TRIDENT Z4 neo DDR4 3600Mhz | Asus B550 TUF Plus Gaming | 2TB Aorus Gen4
TM Warthog HOTAS | TrackIR 5 | Windows 10 Home x64 | 
My HOTAS Profiles

  • 1 month later...
Posted (edited)

Yup, modifiers are plane-specific, you can have the same button as a modifier in one plane and not in another. You can even have two different physical buttons as the same modifier (when you specify its name) in two different modules.

When you define the modifier there is a warning that the button is used, but you can go on - which is actually good. You'll just see all the wrong bindings with red exclamation marks.

I've just created a video about modifiers, btw... there are some interesting applications, especially with axes and when you play with the logical names of the modifiers:

Edited by virgo47

✈️ L-39, F-4E, F-5E, F-14, F/A-18C, MiG-15, F-86F, AJS-37, C-101, FC2024 🛩️ Yak-52, P-47, Spitfire, CE2 🚁 UH-1H, Mi-8, Ka-50 III, SA342 🗺️ NTTR, PG, SY, Chnl, Norm2, Kola, DE 📦 Supercarrier, NS430, WWII, CA 🕹️ VKB STECS+Gladiator/Kosmosima+TPR ▶️ DCS Unscripted YouTube 🐛 "Favourite" bugs: 1) Object local camera fast/slow inverted, 2) Yak-52 toggles not toggling, 3) all Caucasus ATC bugs

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...