OpenXcom Forum
OpenXcom => Troubleshooting => Topic started by: Mathalor on January 20, 2021, 09:23:36 pm
-
I'm trying to start a new game in tftd. I read the FAQ, "https://www.ufopaedia.org/index.php/Installation_FAQ_(OpenXcom)" (hyperlink won't take the last paranthesis, don't know why), and I've installed the files accordingly, minus the common and standard folders, and the optional folders. The game certainly picks up on the UFO files, which are installed in the same .local/share/openxcom directory. TFTD files are in a TFTD folder, UFO files in a UFO folder. I've searched both the mods section in the game and the options section in the game. The mods section has a slider for base game but it will only offer me UFO.
How can I get this working?
-
Most likely there is still an error in your installation.
In order to help we need some more info, can you attach/post the output of:
tree -d -I "xcom?|standard|common|mods" ~/.local/share/openxcom/ > ~/Desktop/openxcom.tree.txt
* The -I option ignores a bunch of standard folders
* The ">" construct will create a file on your desktop
* -d is there since at the moment I am only interested in the folder structure, not the files under it.
-
I don't have "tree"
Using Ubuntu, if it makes a difference
-
Nevermind, I installed it. Results:
/home/user/.local/share/openxcom/
├── TFTD
│ ├── GEODATA
│ ├── GEOGRAPH
│ ├── MAPS
│ ├── ROUTES
│ ├── SOUND
│ ├── TERRAIN
│ ├── UFOGRAPH
│ └── UNITS
└── UFO
├── GEODATA
├── GEOGRAPH
├── MAPS
├── ROUTES
├── SOUND
├── TERRAIN
├── UFOGRAPH
├── UFOINTRO
└── UNITS
19 directories
I run the nightly appimage file from the openxcom folder
-
That looks correct on first sight.
Although still in the process of determining if you found some edge case "bug". Perhaps you can try the following (hackish) command and see if openxcom allows TFTD afterwards:
touch ~/.local/share/openxcom/TFTD/foolTheApplication.empty
Please note i cannot reliably tell you if it breaks some other part of TFTD.
-
Yes, that worked. I'm looking at the TFTD new game screen.
-
Thanks to your report it was discovered that the basic check was a bit too strict when it came down to users putting the absolute minimum (according to the FAQ) in those base folders.
This will be fixed in the next nightly appimage. Once you are on that one it should be safe to remove the hackish workaround file.
Thank you for the report and interaction.