OK, using those I re-produced the problem and have the fix. I'll post a P5 when I've built all the files.
The problem was caused by needing to allow model data to exceed 4K. The model files contain 2 copies of the data, but I've needed to move where the second copy is from 4K into the file to 8K. To maintain backward compatibility, I still look for data at 4K. Under certain conditions, there is random data at 4K into the file and this was being loaded instead of the data at 8K. I've added more checking of the data at 4K so the random data is now very unlikely to be considered valid.
I tested this change with your model files and the model at slot 10 loaded correctly.
Mike
Edit: P5r229 now posted.
erskyTx/er9x developer
The difficult we do immediately,
The impossible takes a little longer!
OK, the test versions for r229 have a new feature. As well as independent trims in flight modes you may define a trim in a flight mode to be that from another mode with a flight mode specific value added to it.
I thought I had this backward compatible, but it seems the encoding of these new options doesn't always pick up the old encoding correctly.
Using one of your models, I reproduced the problem. I fixed it, on that model, by going to the flight mode menu and editing the entries showing R,E,T and A, changing to something else, then changing back. After that, the independent trims appear to work as expected.
I'll investigate what is causing the problem and see about sorting it. Test versions with such new features may have these problems as testing all possible things is quite difficult.
Mike
erskyTx/er9x developer
The difficult we do immediately,
The impossible takes a little longer!
I've changed the source files to fix these.
However, the reason for the problem is the addition of VARS. These are an alternative to GVARS, but are MUCH more useful and very powerful. You may even use a VAR to set the value of a curve point.
To change to using VARS, there is an option in the Model Setup|General menu, near the end.
With VARS enabled, there is a new option visible under Model Setup|Globals (option is VARS).
I've attached a pdf file with details about VARS and how to use them.
If you are not using GVARs for anything, then enabling VARS in each model will fix the display!