-
-
Notifications
You must be signed in to change notification settings - Fork 379
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Regression? New mixes being forgotten. #3367
Comments
I didnt catch this bug on 2.8.1, but yesterday I upgrade EdgeTX to 2.8.2, and get this problem. |
Experiencing the same issue on 2.8.2. UPDATE: still exist on 2.8.3 |
Issue persists on 2.8.4 |
2.10-nightly still not fixed |
I saw recent reference to this suggesting it only happens on the existing models, not new models... can you try creating a new model and seeing if this still happens. BTW, main / nightlies are in no way safe to fly atm. Stick with 2.8.x or the 2.9 branch for now, other than for testing. |
Oh, indeed. Newly created model does not suffer from this issue (on 2.8.4). |
I am encountering the same issue, my radio is the RadioMaster Pocket. Here is an example of a model with this issue, if I set mixer CH7, I loose it after a reboot (or simply switching to a different model). Workaround: I manually edited the YAML file with a text editor, removed the mixers content (under mixData section) and then recreated everything from scratch thru the radio. It is now working fine. |
@paulo-serrao thx for the file! What happens here is the following:
When such file is loaded in the destination radio, the following happens:
If I make a quick & dirty patch to take the ![]() Now the issue is that due to the how we store mixer lines in memory, it gets quite hard to patch so that it always works. The easiest way to reproduce is to set the source of a mixer line to |
Oh, and btw: I believe this bug is present for quite some time now (probably as old as the YAML parser). |
@raphaelcoeffic, this is the original model file from X9D before I started making changes in the new radio to adjust to new button layout: model02_x9d.zip The previous file I uploaded was after many changes on other menus/settings and also trying multiples times to set a mix on CH7 to Switch D (just a direct assignment). PS: On X9D I had CH6 set to Switch G, that switch does not exist on RadioMaster Pocket, maybe that's the root cause? This is how it looks like on my Taranis |
This is it, yes. That transforms it into |
I am using the BetaFPV LiteRadio3 Pro, |
As was mentioned before, the workaround it to create a new model. The issue persists only in models created on pre-2.8 versions. |
@ValorLin @oloendithas as you can see, there is a code change proposed in #4008 which you can try (backup your SD card before, you will need it to go back to 2.9). We need feedback from you guys on that. |
I've recreated my model and can't reproduce the issue any more 🤷🏻♂️ |
You can edit the yaml, clear out the section for the mixer and then recreate it on the radio. (this will avoid having to recreate the whole model and all settings) |
Exactly, the issue is the mixer source |
Thanks! It works!. Below is the original yml that caused this issue. |
The below issue occurs only with 2.8.1, not 2.8.0.
Is there an existing issue for this problem?
What part of EdgeTX is the focus of this bug?
Transmitter firmware
Current Behavior
When setting up a mix other than the 5 defaults (them being the 4 stick movements as well as Arm/Disarm on switch SC), and then rebooting the transmitter, any additions made to the Mixes tab are then gone again.
Changes to one of the 5 defaults are retained, only additions are forgotten.
Expected Behavior
Adding a mix and rebooting retains that mix throughout reboots.
Steps To Reproduce
Transmitter
BetaFPV LiteRadio3 Pro
The text was updated successfully, but these errors were encountered: