I'm writing a LUA script for OpenTX, to be used with simulation, mainly with neXt. And I've hit a very weird issue. Running the script results in a quick change of the elevator from -100 to 100 at some point, but neXt ignores this change.
I was able to reproduce the issue by just using a 3-pos switch, which is directly mapped to elevator channel. So changing switch position results in elevator being -100, 0 or 100. Just used a switch as an input for the mix.
Please see the video. Please compare channel 3 in the input monitor and the right stick at the bottom of the screen (I'm using mode-2).
As you can see, as long as I'm switching the switch slowly, everything is fine. Both stick and input monitor show proper value. But as soon as I flip the switch quickly, from one extreme position to another, the stick at the bottom of the screen is not updated. However, in Input Monitor everything is fine.
What you don't see in the video is, that helicopter movements are also incorrect. It is rotating with elevator in the wrong direction.
What can it be?
Running latest neXt version.
It's a serious problem for me, as I'm stuck with development now..
I think you probably misunderstood me. It sounds to me, like the filter you mention would affect it, if I would switch a channel from -100 to +100 for 0.1 second and then back to -100. Then neXt could miss this short change to +100.
But the case here is different. I switch the channel from -100 to +100 and leave it on +100 for minutes. But neXt thinks it is -100 for minutes. Surely receivers don't work like that.
As for script, I had some changes and at this point it does not switch from -100 to 100 anywhere. And then it seems to work fine. It does quick switches between 0..100 and it mostly works fine, but I believe sometimes neXt gets confused with that too. I still think it would be great to have that resolved..
The simulator reads the transmitter signal 60 times per second. And if a value jumps more than a defined value, the last valid value is used. We can call this function failsave or filter. This function is still required for certain remote controls.
Have you ever used the Showcase Player? You can take control of the flight at any time while playing a flight. Open the recorder with v, click on Menu, click in the empty box to the left of a flight name and then on Run Playlist.
Do you need a start function that starts the helicopter in a random position at eye level in front of you?
Zitat von Klaus-Eiperle im Beitrag #7The simulator reads the transmitter signal 60 times per second. And if a value jumps more than a defined value, the last valid value is used. We can call this function failsave or filter. This function is still required for certain remote controls.
Then I could just avoid jumping that much. But what is this value?
Zitat von Klaus-Eiperle im Beitrag #7Have you ever used the Showcase Player? You can take control of the flight at any time while playing a flight. Open the recorder with v, click on Menu, click in the empty box to the left of a flight name and then on Run Playlist.
Do you need a start function that starts the helicopter in a random position at eye level in front of you?
The script does not orientate it just randomly. Heli orientation comes from a learning process, and then it's a tricky way to put the heli in this orientation, to make sure it still has speed at this point.
But let me look at the showcase first, how do you prepare these .anim files? I googled "showcase" thinking it's some common tech, but googling this keyword returns all half of the internet..
