February 28, 20251 yr I'm trying out the simple button handling in Axis and Ohs. However, something weird is happening. When configuring a button, the button click works, and shows up as "CLICK" (button 0). Long press also works the first time, and show up as "CLICK" (button 1). However, after this long press, if I do another short press it shows up as "TURN_RIGHT". If I save the button using this "TURN_RIGHT" assignment, it seems to work. But if I save the button when it shows "CLICK" assignment, it doesn't trigger. What is "CLICK" vs "TURN_RIGHT" and what determines which one is triggered?
February 28, 20251 yr Commercial Member 19 minutes ago, pilotjohn said: I'm trying out the simple button handling in Axis and Ohs. However, something weird is happening. When configuring a button, the button click works, and shows up as "CLICK" (button 0). Long press also works the first time, and show up as "CLICK" (button 1). However, after this long press, if I do another short press it shows up as "TURN_RIGHT". If I save the button using this "TURN_RIGHT" assignment, it seems to work. But if I save the button when it shows "CLICK" assignment, it doesn't trigger. What is "CLICK" vs "TURN_RIGHT" and what determines which one is triggered? Save it when it says "CLICK". Do not press the button again. The TURN_RIGHT is an internal error - the SD input is mapped to a fake MIDI event and that "TURN" is what it understands when you press the button again in this state. But that is only when assigning it, it doesn't matter in actual operation (that is a different mechanisms altogether, because the app already knows what to look for) I wouldn't assign "long press" this way. The SD should send button down and up separately, so I would use the "Long Click" option in the AAO button assignment instead. Question: why are you using the "Button" Action, what is your use case? I'm not aware that anybody has done this before... so I'm curious. Edited February 28, 20251 yr by Lorby_SI LORBY-SI
February 28, 20251 yr Author 32 minutes ago, Lorby_SI said: Save it when it says "CLICK". Do not press the button again. The TURN_RIGHT is an internal error - the SD input is mapped to a fake MIDI event and that "TURN" is what it understands when you press the button again in this state. But that is only when assigning it, it doesn't matter in actual operation (that is a different mechanisms altogether, because the app already knows what to look for) I wouldn't assign "long press" this way. The SD should send button down and up separately, so I would use the "Long Click" option in the AAO button assignment instead. Question: why are you using the "Button" Action, what is your use case? I'm not aware that anybody has done this before... so I'm curious. Hmm... I save when it says "CLICK", but then the button doesn't trigger (neither down nor up, the green light never lights up). If I save it when it says TURN_RIGHT, it triggers on release. I'm planning on moving from FSUIPC to AAO. I'm using a simple FSUIPC Stream Deck plugin, which is just buttons, and using the buttons is the fastest migration path. I didn't have long-press, but would like to, but I see how I can do that in AAO instead of the SD plugin, so sounds good! Edited February 28, 20251 yr by pilotjohn
February 28, 20251 yr Commercial Member 28 minutes ago, pilotjohn said: using the buttons is the fastest migration path I'm not sure about that. Depends on what those buttons did in FSUIPC. When you need to trigger scripts you would have to migrate those too - and then you can just as well implement them properly in the StreamDeck. Or alternatively don't migrate at all and look instead for ready-made StreamDeck profiles on flightsim.to. If you are lucky, there is at least one for your "main" aircraft - and you can then take that as inspiration for making your own. The SD actions are so much more powerful and fun than the simple "button" Edited February 28, 20251 yr by Lorby_SI LORBY-SI
February 28, 20251 yr Author Just now, Lorby_SI said: I'm not sure about that. Depends on what those buttons did in FSUIPC. When you need to trigger scripts you would have to migrate those too - and then you can just as well implement them properly in the StreamDeck. Or alternatively don't migrate at all and look instead for ready-made StreamDeck profiles on flightsim.to. If you are lucky, there is at least one for your "main" aircraft - and you can then take that as inspiration for the others. They're triggering virtual FSUIPC buttons, which seems to be very similar to your "WEB API" buttons. The reason I prefer this, is that the config for what to trigger remains in AAO, so if I want to move it to a physical button, I can, without touching Stream Deck profiles (for which I have scripts to swap out buttons per aircraft - to move layout around).
February 28, 20251 yr Author 33 minutes ago, pilotjohn said: Hmm... I save when it says "CLICK", but then the button doesn't trigger (neither down nor up, the green light never lights up). If I save it when it says TURN_RIGHT, it triggers on release. Any thoughts why this is not triggering when it's assigned to "CLICK"?
February 28, 20251 yr Commercial Member Just now, pilotjohn said: They're triggering virtual FSUIPC buttons, which seems to be very similar to your "WEB API" buttons. The reason I prefer this, is that the config for what to trigger remains in AAO, so if I want to move it to a physical button, I can, without touching Stream Deck profiles (for which I have scripts to swap out buttons per aircraft - to move layout around). But you are degrading the StreamDeck to a mere button box, which IMHO is a massive waste of resources. Just asking, no offense please - you do know what the SD Actions can actually do? LORBY-SI
February 28, 20251 yr Commercial Member Just now, pilotjohn said: Any thoughts why this is not triggering when it's assigned to "CLICK"? Not really, no. Lack of experience on my part - in all these years, nobody has every used this before. All the authors flock to the "proper" StreamDeck actions. I will put it on the list, I am currently implementing a change in the plugin anyway. LORBY-SI
February 28, 20251 yr Author 9 minutes ago, Lorby_SI said: But you are degrading the StreamDeck to a mere button box, which IMHO is a massive waste of resources. Just asking, no offense please - you do know what the SD Actions can actually do? I do. 🙂 I prefer visual feedback from the VC (instead of buttons blinking/changing). But I prefer some tactile/spatial triggering. My main use for SD buttons is to place them "roughly" in the location where I would reach for them in the VC (not always possible, but close enough). This way, flaps are not where I think flaps should be (e.g. flaps on XCub is left, not on the right), but rather, where you would reach for it in the aircraft (I have plans for having some above my monitor, but not there yet). Edited February 28, 20251 yr by pilotjohn
February 28, 20251 yr Author 5 minutes ago, Lorby_SI said: Not really, no. Lack of experience on my part - in all these years, nobody has every used this before. All the authors flock to the "proper" StreamDeck actions. I will put it on the list, I am currently implementing a change in the plugin anyway. Thanks, I can get it to trigger on TURN_RIGHT, which I think is good enough, but would be nice to trigger on KEY_DOWN/UP with short/long press. This seems to just "trigger" when I release.
February 28, 20251 yr Author 22 minutes ago, Lorby_SI said: If you are lucky, there is at least one for your "main" aircraft - and you can then take that as inspiration for making your own. The SD actions are so much more powerful and fun than the simple "button" What I would really like is custom sized touch LCD screens that I could display anything on, and trigger from there. FlightSafety has some classroom trainers that use this concept, but of course more overkill than I want. Edited February 28, 20251 yr by pilotjohn
February 28, 20251 yr Commercial Member 21 minutes ago, pilotjohn said: What I would really like is custom sized touch LCD screens that I could display anything on, and trigger from there. You can do that with AAO gauges or AAO web pages, depending on which tech you prefer. But something like that will be quite the effort to implement. Edited February 28, 20251 yr by Lorby_SI LORBY-SI
February 28, 20251 yr Commercial Member 28 minutes ago, pilotjohn said: Thanks, I can get it to trigger on TURN_RIGHT, which I think is good enough, but would be nice to trigger on KEY_DOWN/UP with short/long press. This seems to just "trigger" when I release. Please send me an email to the support address (last page of the manual) with your proof of purchase. I think that I have a solution for this, but it requires a new plugin and a new version of AAO as well. This is dangerous stuff, because it messes with the existing MIDI logic. LORBY-SI
February 28, 20251 yr Author 11 minutes ago, Lorby_SI said: Please send me an email to the support address (last page of the manual) with your proof of purchase. I think that I have a solution for this, but it requires a new plugin and a new version of AAO as well. This is dangerous stuff, because it messes with the existing MIDI logic. Sent, thanks!
Create an account or sign in to comment