Forum Replies Created
-
Posts
-
@Ropp29: Was that successful? I’m wondering as I’m also using external trim wheel, but so far did not try to set it up in CLS2Sim.
@Brunner: Couldn’t CLS2Sim read out the simulator’s trim setting (or even just the force on the elevator?) to make the right pitch position and force?
Yes, I’m using a CLS-E NG with the Honeycomb Bravo Throttle and MFG Crosswind rudder pedals.
The absolute awesome thing about the Bravo is that it has Trim and Flaps, which is extremely useful and much more enjoyable compared to assigning buttons on the Yoke. I think the Bravo concept with modular levers is fantastic, and I was honestly not aware that there are soo many assignable switches and buttons, too. Lastly, the mounting with either clamps or a big 3M pad is really flexible.
No power required, no drivers for FS2020 required, .. those are details that round off the package. Of course, extremely affordable, too. Glad I ordered in the first week and got mine already. They are sold out since a while and for quite some more time I believe.
There is also an extension to have your mouse on a pad underneath, which might be a handy addition.
Known issue: With the default assignment in FS2020, there is a really bad config. The levers have an additional (freely assignable) “button” if you move them below the fully idle state. Some of the levers come by default assigned with things like “Throttle Decrease” or “Mixture Decrease” on those “buttons”. Also, if you decide not to attach some additional levers (which is a great option), then those buttons will be in triggered state. So if you didn’t yet: In the default config you’ll always have some button triggering throttle and mixture decrease, unless you attach those levers and move them away from fully idle. Solution: Just remove those button assignments.
Perhaps you’re in USB or VJoy mode and not using the API?
Mine is freezing, too, no matter in which order I’m starting the two apps or when I connect. Hope MS is fixing this soon. Seems like the sense of sending the Alpha out to people like Brunner is to make sure things are working from the beginning, so this looks like a serious change between last Alpha and Release version. I understand things can become hectic on the last mile, but in general you’d want to avoid such big change to how an API shipped to Devs work.
@Brunner, please update this thread once you have confirmation of a fix. Thanks!
