The C key and V key were assigned in MSFS2020's keyboard settings to Decrease Cowl Flaps and Increase Cowl Flaps respectively. I assigned (bound) two joystick buttons to these keys (in fact I am using the same keyboard settings), as I did in Flight Crew A320 MSFS. In there hitting these joystick buttons resulted in the correct FS2Crew action. 

In FS2Crew FBW A32NX hitting the C or V key gives the correct result, i.e. FBW A32NX responds correctly, however, when I hit one of the assigned joystick buttons no response is being given by FBW A32NX. To make sure that the joystick buttons were configured correctly I shut down MSFS2020, restarted it and fired up Flight Crew A320 MSFS. All worked fine in this "old" app. 

What can be the culprit here in FBW A32NX that joystick button input is not being recognized apparently.

Apparently fs2crew monitors specifically the keyboard keys, and not the actions in the simulator that are assigned to them, it's a pity. I also used a joystick in the previous version. Hopefully this will be fixed somehow.

4 hours ago, Draiv said:

Apparently fs2crew monitors specifically the keyboard keys, and not the actions in the simulator that are assigned to them, it's a pity. I also used a joystick in the previous version. Hopefully this will be fixed somehow.

You're not obligated to use keyboard keys.  I personally don't.  I just use the mouse.

But you can change the hotkeys on the Config panel, or if you select "blank" you'll have no hotkey.

Fyi, there's a bug in Simconnect that prevents developers from using joystick button assignments.  It's a known issue in MSFS Simconnect.

We're hoping Asobo fixes it someday.

 

Edited August 15, 20214 yr by byork

Just reading this thread as I just found out about the A32NX version being released, does this mean that if we normally use joystick buttons for flaps, landing gear, reversers, etc. that these won't be recognised and therefore we'd have to change the way we fly to use the product? Not entirely sure how the product works / what it offers so apologies if a silly question.

Thanks!

11 minutes ago, r2b2nz said:

Just reading this thread as I just found out about the A32NX version being released, does this mean that if we normally use joystick buttons for flaps, landing gear, reversers, etc. that these won't be recognised and therefore we'd have to change the way we fly to use the product? Not entirely sure how the product works / what it offers so apologies if a silly question.

Thanks!

There's no such thing as a silly question 😉

I don't know if you've ever used an FS2Crew before, but it works like this:

Voice control:  You speak "Gear down".  FS2Crew sends the gear down command.  Your gear goes down.  Your joystick is not a factor.

Only way hardware could be a factor is if you're using a home cockpit setup and your gear lever sends a continuous "gear up" signal that overrides our "gear down" signal.  Make sense?

Button control:  You can use your mouse or press a hotkey to tell your FO to drop the gear.  Your joystick button assignments are non issues.

I think the other poster wanted 'hot key' assignments to be connected directly to joystick buttons via the hotkey assignment menu on the Config Panel.  Due to Simconnect issue, we can't do that yet.  Waiting on Asobo.  It used to work in P3D, but our friends in France broke it 😉

Only way to use joystick buttons is to use FSUIPC to connect your joystick button to the same hotkey (for example the "C" key) selected as your hotkey assignment in the drop list on the Config panel.

Remember though hotkeys are optional.

You can easily get away with just using your mouse... or even use just the hotkeys.  There is nothing wrong with them.



 

Edited August 15, 20214 yr by byork

Thanks for the reply.

I haven't used one of the FS2Crews wasn't but your explanation has explained things well so thanks again

9 hours ago, hvw said:

The C key and V key were assigned in MSFS2020's keyboard settings to Decrease Cowl Flaps and Increase Cowl Flaps respectively. I assigned (bound) two joystick buttons to these keys (in fact I am using the same keyboard settings), as I did in Flight Crew A320 MSFS. In there hitting these joystick buttons resulted in the correct FS2Crew action. 

In FS2Crew FBW A32NX hitting the C or V key gives the correct result, i.e. FBW A32NX responds correctly, however, when I hit one of the assigned joystick buttons no response is being given by FBW A32NX. To make sure that the joystick buttons were configured correctly I shut down MSFS2020, restarted it and fired up Flight Crew A320 MSFS. All worked fine in this "old" app. 

What can be the culprit here in FBW A32NX that joystick button input is not being recognized apparently.

Also note that in FS2Crew FBW were are not "linking" joystick / keyboard assignments to stock MSFS events anymore like we did for A320 Button Control.

So we're not using Cowl flaps, etc., for keyboard / joystick assignment.

We're doing straight assignments  now...  trying to connect to MSFS stock events just got too messy.

Edited August 15, 20214 yr by byork

7 hours ago, byork said:

You're not obligated to use keyboard keys.  I personally don't.  I just use the mouse.

But you can change the hotkeys on the Config panel, or if you select "blank" you'll have no hotkey.

Fyi, there's a bug in Simconnect that prevents developers from using joystick button assignments.  It's a known issue in MSFS Simconnect.

We're hoping Asobo fixes it someday.

 

I personally always used joystick buttons in previous versions. I wonder why you no longer are using events like "increase cowl flap" etc, but rather use only alphanumerical values. (Even combinations with Shift and Control or both are not possible). Fyi, so far with other applications I haven't found any hiccup with using joystick buttons. Why can other developers use joystick button assignments and you cannot? Isn't it too easy to blame MS/Asobo?  

Changing hotkeys doesn't give me joystick functionality either 🙂 

As said in my initial note, sending joystick button command to the previous version of FS2Crew work fine

I had hoped that this new version of FS2Crew would, for me, at least have the same functionalities as the previous version. In fact this new version thus has less functionality for me. Also the lack of a PDF manual is a royal PITA , tooltips going "all over the place" doesn't provide much immersion.

I think I will go back to the previous version for the time being

 

Edited August 15, 20214 yr by hvw
Spelling error

Hi Hans,

You can turn off the Tool Tips.  There's an option on the Config Panel.

And you don't need a PDF anymore, just use the "Assist" panel.

We're waiting on Asobo to fix the joystick button hotkey in Simconnect.

As an interim solution, maybe we'll bring the "Cowl" flap method back in V1.1 for people who don't want to use FSUIPC to link joystick buttons to key assignments.

Cheers,

18 minutes ago, byork said:

You can turn off the Tool Tips.  There's an option on the Config Panel.

I know, but wasn't the idea with these tooltips to replace a manual?

Wrt the joystick button hotkey. Wouldn't it be feasible to replace the alphanumeric value to a FS2020 event like Increase cowl flap as was the case with the previous versions of FS2Crew? In that way I can assign a joystick button to such events and the problem is solved or bind this alphanumeric value to an event? In that way both keyboard users as well as joystick users can be happy. (Just an idea).

Edited August 15, 20214 yr by hvw
adding text

1 hour ago, hvw said:

I know, but wasn't the idea with these tooltips to replace a manual?

Wrt the joystick button hotkey. Wouldn't it be feasible to replace the alphanumeric value to a FS2020 event like Increase cowl flap as was the case with the previous versions of FS2Crew? In that way I can assign a joystick button to such events and the problem is solved or bind this alphanumeric value to an event? In that way both keyboard users as well as joystick users can be happy. (Just an idea).

People don't read manual anymore, at least not 95 percent of them.  The culture has changed...

The tool tips are very easy to use, easier than a PDF.

And as mentioned, you can turn the tool tips off if you don't want them.

We'll see about using something like "Cowl Flaps" in V1.1...  it may or not be possible because it requires a "repeat" function for push to hold buttons like the Push to Talk button.  P3D and FSX had this... not sure if MSFS does off hand.

Can you not just assign a joystick button to an A to Z key using FSUIPC or some other joystick button to key program.  It's the best solution until Asobo fixes Simconnet.

1 minute ago, byork said:

People don't read manual anymore, at least not 95 percent of them.  The culture has changed...

The tool tips are very easy to use, easier than a PDF.

And as mentioned, you can turn the tool tips off if you don't want them.

We'll see about using something like "Cowl Flaps" in V1.1...  it may or not be possible because it requires a "repeat" function for push to hold buttons like the Push to Talk button.  P3D and FSX had this... not sure if MSFS does off hand.

Can you not just assign a joystick button to an A to Z key using FSUIPC or some other joystick button to key program.  It's the best solution until Asobo fixes Simconnet.

Bryan, I don't know where you derived this 95% from, but be assured, that lots of people still do read manuals 🙂 Anyway, I will switch off the tooltips and go by "trial and error"  🙂 

I used the "Increase Cowl Flap" etc while using the previous version of MSFS FS2Crew without any problem, that's why I was and am disappointed that you didn't include this in the new FS2Crew. I am not using fsuipc at all anymore as I prefer to assign everything thru FS2020's events. The reason I used to use fsuipc in FS2020 was the fact that I couldn't get my joystick's throttles to work as I preferred thru FS2020 itself. But when FBW introduced their throttle calibration feature, I didn't have any use for fsuipc anymore.

I don't know why you would need a repeat button for just a single joystick input, it is just the same as hitting an alphanumeric key once that can be used now, like we did in the previous FS2Crew versions (for FS2020/FBW A320 and under P3D's 737 FS2Crew and others). We only need the functionality that in these mentioned applications were done by the C and V key (and sometimes the B key could be used to bring up the main window). I think we have/had different functionalities in mind, but I hope I clarified what I have in mind with this note.

The "Cowl Flaps" system works for single button presses.  FS2Crew A320 Button control only used single button presses so it could work fine for it.

The problem is in FBW we're using a Push To Talk key, which requires a "repeating" function for the event because you're holding the button down, not just clicking it.

 As mentioned, FSX/P3D had this, but I'm not sure if MSFS does.
 

Edited August 15, 20214 yr by byork

1 minute ago, byork said:

The "Cowl Flaps" system works for single button presses.  FS2Crew A320 Button control only used single button presses so it could work fine for it.

The problem is in FBW we're using a Push To Talk key, which requires a "repeating" function for the event.  As mentioned, FSX/P3D had this, but I'm not sure in MSFS does.
 

OK, all clear. I could use fsuipc for these two functions only for the time being, hoping that you can come up with an option as I described in an upcoming (test) version.

It would be nice if you left the Push To Talk button for manual assignment, for those who use voice commands, and for those who use only button control, add Cowl Flaps.