EdgeTX
Linux Appimage Companion Simulator possibly pointing to older EdgeTX version.
Is there an existing issue for this problem?
- [x] I have searched the existing issues
What part of EdgeTX is the focus of this bug?
Simulator
Current Behavior
Was going to replace a model image on one model on my radio and in Companion/Simulator.
This new image
No problem on the radio.
The model listing
and the situation before in Companion/Simulator
and then selecting the new image
Strange image in Simulator!
(I tried that on another Debian machine with a fresh installation and no image at all when selecting that image ...)
That are the EdgeTX versions, I am holding on my main machine in case I have to revert.
I have those two config files in ~/.conf/EdgeTX/
This is the Companion 2.11.conf
To find out, what is happening here, I started Companion 2.11.1 not from the start menu, but in a terminal and add the end of the terminal protocol the Simulator is pointing not to 2.11.1, but to 2.10.6.
And that strange image is to be found here in my 'old' data 2.10.6.
It is not obvious to me, where I made a mistake, which points the Simulator to an old existing EdgeTX version.
Could it be an issue in the Appimage? Running 2.11.1 and the Simulator pointing to 'old' data 2.10.6 ....
br
Expected Behavior
SIM pointing to data of current version.
Steps To Reproduce
See current behavior ...
Version
2.11.1
Transmitter
FrSky X10 Express / X10S Express (ACCESS)
Operating System (OS)
Linux
OS Version
Debian 12 bookworm
Anything else?
Took me 2 days to find out ;-)
Did you have a look here?
I see this in Companion on 2.11.1
I don't see me pointing anywhere to 2.10.6 ......
Some of the simulator run settings are saved to the conf file under each profile. You could try a new profile for the same radio.
I assume, Companion 2.11 looks into this conf. file here
and there is nothing pointing to 2.10.6.
OK, I also hold a 2.10 conf. file, just in case I have to revert. But something makes me think, NOT Companion 2.11.1, but the Simulator, which comes with it, is looking into the 2.10 configuration .....
You can also see it in the terminal output, when starting Companion 2.11.1 from the terminal here.
Everything is fine, and then it starts here.
The SIM in the Companion 2.11.1 appimage is looking into the 'old' 2.10 config.
I checked your configuration and the profile sd path is pointing to 2.11. The simulator run settings are a long binary string and not humanly readable.
I checked your configuration and the profile sd path is pointing to 2.11. The simulator run settings are a long binary string and not humanly readable.
I only can see the messages provided by starting Companion 2.11.1 in the Linux terminal.
Find this screenshot interesting. And I think, it gives a good impression of the issue here
Companion 2.11.1 in the background picks the image from 2.11.1 and the Simulator in front the image from 2.10.6 ...
Here the two folders with the 'Companion image' in the foreground and the 'Simulator image' in background
Quite strange