A question: I have the Cowansim MD500e. It works great in msfs 2020. But in 2024, I just can’t get the collective to work regardless of how I map it. In 2024 it’s mapped to the collective via spade.next to the collective axis as per the documentation. In MSFS 2024 no axis binding works at all. The clective stays put and does not move. This is trying different axis assignment in the Sim mapping or via spad.next.
When I move it with the mouse the spad.next eve t monitor shows the collective B variable changing. But I cannot make any input event affect the collective. This also applies to discreet incr and decr events for the collective.
So is it just me, or does anyone else see this problem? I have not seen any announcements from Cowansim about 2024 compatibility
1 Like
Same issue here. Have you found a solution?
Yes. Sort of. What I managed to do is to use spad.next in a two-step fashion:
- Use the axis to set the LVAR for collective, calibrated to 0-100
- Send a B event for ENGINE_COLLECTIVE_LEVER using the
[LVAR:Collective] / 100 in an expression.
This seems to work, although in the sim, the collective is not stable (vibrates madly between the position and down) - but the helicopter behaves OK. Seems a very backwards way of doing it - but it does the job.
It would be nice if you could send a B event from spad.next using an axis value directly - or even a calibrated axis value. But as far as I can tell, that’s not possible, so I used an LVAR as an intermediate thing. But I suspect tht this can have unwanted side-effects. In any case, it got me somewhere near wher I want to be.
1 Like