Since I vaguely remembered this error did not manifest on OXC appimage I decided to do some comparison tests.
Using the following setup:
* A fully operational folder structure on the game default path (``~/.local/share/openxcom`` for linux)
* A test folder for the binaries (``~/oxce``)
With the following binaries
1) OXCE AppImage: ``OpenXCOM_Extended-v7.11-x86_64.AppImage``
Using OP's download (wget) link.
2) OXCE Binary: ``OpenXcomEx, v7.11-8e9fdfc...``
From
https://openxcom.org/forum/index.php/topic,5258.0.html3) OXC AppImage: ``OpenXcom_20210611_8d45159bf_x86-64.AppImage``
Using download link from website (
https://openxcom.org/git-builds/)
4) OXC Binary
Compiled from commit "f2e509c4" since I could not find a binary only download.
And the following test scenarios:
A) test folder contains **only** the binary.
B) test folder contains binary and **empty** folders ``UFO`` & ``TFTD``.
The results are summarized in the table below.
Binary | Scenario A | Scenario B |
1 | fails (I) | fails (I) |
2 | works | fails (II) |
3 | works | works |
4 | works | works |
(I) Message: No installations found
(II) No message, but got presented with a black screen (no crash).
From this i would conclude that OXC and OXCE differ in behavior in that:
OXC seems to test if the required folders (UFO & TFTD) have some content and if not keeps searching.
OXCE seems to test only for existence of those folders, where the first one wins.
-> Kinda weird since ``OpenXcom::Options::_gameIsInstalled()`` suggests OXCE does actually test.
Hope this helps.
P.s.
The installation instructions for the appImage as seen when following the docker link from forum topic mentioned before are still technically correct.
It states that one has to create (and fill with correct data) the UFO and TFTD folders in the **same** directory as the AppImage.
It does not mention that the AppImage does not work with the default data folder (~/.local/share/openxcom). Even though one might assume it does.
P.p.s.
Logs for the 8 tests performed are available as attachment.