KurtV

Oh yes, thats the magic, much better! Thank you!

Cool, I'll give that a try, seems like it would be more reliable than what I'm doing now. Thanks!

Interesting ideas... So far I have better luck with it on 'left turn', as it triggers as I'm releasing. Triggering on right turn (as pressure is applied) seemed less reliable. I'm going to run it like this for a bit and see how it goes... Basically I have this little LPD8 laying around and was hoping to integrate it, but if it doesn't do what I want I can always build up a little arduino button box or something. The other failure of the LPD8 is that the rotaries have stops, so you can't really use them for things like altitude where you might want to really crank on it for a while... Thanks again for the help on this. At least I have it working for now, so I can tinker a bit and see how best to continue.

The firmware editor doesn't allow you to disable velocity... So that has to be software.

It is always software controlled (in every other program I use...) Looks like there is a editor for the firmware, I'll mess with that and see if it can do it... Is that something you could consider for a future version? A check box? All of this kind of scripting is new to me (obviously). Is there a way I could script something that says if the velocity is between 1 and 127 then thats a press, and if it is 0, it is not a press? In my example code, I copied an earlier version where I didn't have the Enum on that first Lvar... Thanks for your example code, but I have tried that and it behaves exactly the same. I'm just thinking that I need a way to tell it that any press regardless of velocity is a press. but whats weird is that all other event types work normally.. Strike that... It works the same in all types... what is happening is if it sets 'Click' as the trigger it doesn't work... If I press again it goes 'Turn Right' then 'Turn left' as I release.... So in most cases that works ok (and your script works)... So it is looking at that velocity. That returns me to the top of the message -- Would it be possible to get a check box to define velocity vs absolute on midi buttons?

I have an RPN Script that I have assigned to a button on my Akai LPD8 midi controller. The first time I press the button the script works as expected, but subsequent presses do nothing. If I assign the script to another device (such as a mouse button) the script fires on each press as it should. It seems specific to the midi input. If I assign other events to midi buttons everything works fine, its a thing with scripts exclusively... The button works fine with other events, but with the script it only fires one time. And again, if the device button is not midi, it fires on every attempt as expected. I wonder if it is to do with the button being velocity sensitive? Sometimes mapping it says 'Click' other times it says 'turn right' or 'turn left' (even tho its a pad and not a rotary??) It's a pretty frustrating snag, and I'm hoping you can help. The script is a simple toggle. It works fine on the test script button. Script text is below. Thanks for anything! (L:SWS_LIGHTING_Switch_Light_Landing) 0 == if{ 2 (>L:SWS_LIGHTING_Switch_Light_Landing, enum) } els{ 0 (>L:SWS_LIGHTING_Switch_Light_Landing, enum) }

Yeah, I cleaned that all out with acetone, so I'm quite sure whatever it was is gone forever. Waited for that to dry and then dry wiped it and went in with the dry lube. it's more slippery than a greased doorknob now.

@tutmeister I wanted to call your attention to an issue that evolved with my Fulcrum One -- I have had the yoke several months now and remain very happy with it. The pitch movement had developed a slight hitch, or bump in it, it was very slight just coming off its center point. So minor it almost felt like some pet hair had found its way into the mechanism, but that is not what I discovered. When I opened up the case and moved the axis I noticed that the flange that the front bearing in the carriage is mounted to, (This is the flange with the large bolts that take a 5mm allen key), was moving on the left hand side up and down slightly. I recentered the shaft and snugged up that bolt and all is fine now. But what I wanted to suggest is that since this wasn't loose on arrival, it clearly worked loose over time, you may want to consider using some thread locker on that bolt in your future units. Also, I noticed that the rail for the pitch axis had become sticky, this would have been whatever lube you were using at the time (back around Apr/May 2022 I think). I cleaned that all up and re-lubed with the WD40 Dry lube as suggested in your other post. And all is good for now.

Rather than posting the moment I pulled it out of the box as folks tend to do, I wanted to spend time with it. I am an inactive private pilot, and been a simmer for 35 years. So not my first rodeo. The Fulcrum One yoke is easily the best quality flight control device I've used (well, maybe a tie with my Virpil pedals). I have primarily been flying on an old CH stick and pro throttle since about 2000, as nothing has really improved on that. I have owned a CH Yoke, and the old Saitek (Logi) yoke as well and those were both simply horrible, sticky weird disasters. I've never understood why those stayed in production for so long. The Fulcrum yoke is SMOOTH. Both in pitch and roll there is no detectable detent, and it gives reasonably convincing weight on both axis. the handle is a little large, but not unlike a larger GA plane such as a Bonanza, or some Pipers. If you're only experienced with small Cessnas, it will feel a little girthy. The metal handle feels great, and while it seems stupid that would make a big difference, it does. It feels like a real aircraft part. The hat switch is a little twitchy, and I find it uncomfortable to use. Similarly the two trim switches feel a little to big and clunky.. They all are good quality, but I think some refinement could be done here. All of the push buttons are great. No issues. I wish there was a button on the front of each yoke handle in the 'trigger' position. I feel liike that was an unfortunate oversight in the design. But it doesn't ruin my day. Maybe in a future version? With no throttle you will need a solution. I still have an old saitek usb throttle quad I'm using until I decide if I want something more sophisticated. My CH Pro throttle isn't appropriate as it is a left hand military style. I guess it could work if you like to flight right seat, but if you want to sim the left seat, it isn't the right solution. The only issue I have had with the controller is that on day one I didn't get the handle seated firmly on the shaft, so some of the buttons were being flakey. Support suggested checking and reseating and this did the trick, there have been zero other concerns. It worked straight out of the box and I never looked back. The desk clamp is secure and sturdy, but it is honestly probably way larger than needed. The size of it interferes with my keyboard drawer and I had to modify it. I have the tools to do metal work here, but not everyone does, so it would be nice if it had a smaller clamp option. I think the huge table this thing can bite on to is way bigger than most people would ever need. Again, perhaps a design consideration for the future, but not a killer problem. The unit over all is heavy -- which is actually a great thing. But be aware, if you're putting it on and removing it from your desk pretty regularly, it takes a minute. This is not a controller you just slap down and go. Take a minute, set it up good and right. Great product over all and I have no regrets. I probably now have hundreds of flight hours with it, its always just perfect. I do still use my CH stick for shorter sessions, or for stick aircraft, but the Fulcrum is my preferred device now. As Ferris Bueller said about the Ferrari.. "If you have the means, I highly recommend picking one up..."