Differences

This shows you the differences between two versions of the page.

--- client:crossfire [2018/03/11 03:57] – Add image-cache folder entry karl
+++ client:crossfire [2025/04/18 13:08] (current) – external edit 127.0.0.1
@@ Line 17: / Line 17: @@
 either by the option in the //Menu// Client > Configure > Display & Image Cache Options , \\
 which then would change the entry line [[gdefaults#cacheimages]] in the gdefaults file; \\
-or by the [[command line parameters|command-line parameter]] //-cache// , then, \\
+or by the [[optional parameters|command-line parameter]] //-cache// , then, \\
 if there are not found any cached images in the CF_DATADIR, the client should download the images herein.
@@ Line 40: / Line 40: @@
 in red, which could confuse many users.
-The solution is usually to create an empty file in //share/crossfire-client// to suppress this annoying error message; \\
+The solution is either to create an empty file in //share/crossfire-client// to suppress this annoying error message; \\
-on Linux it would be ''touch /usr/local/share/crossfire-client/bmaps.client'' \\
+on Linux it would be the terminal command ''touch /usr/local/share/crossfire-client/bmaps.client'' , \\
+or to download the "crossfire-client-images-X.YY.Z.tar.gz" version package from the sourceforge repository \\
+and to extract it inside the //share/crossfire-client// folder.
-Rationale would be to have a shared image folder on a shared computer, so that not every user would need his own image-cache files. This image cache directory has some 10 to 20 thousand files at a size of 10 - 20 MB for both image sets //default// and //classic// .
+The crossfire-client-images-.tar.gz package is available since around version 1.2.1 and for most versions of the client, and if one version folder on sourceforge misses it like 1.12.0 and 1.8.0, then likely the version before would fit. \\
+The content of the client-images pkg is different, than the storage of the server-send images : Two archive files, one README text file and a bmaps.client text file.
-If desired, one can move the image-cache content into share/crossfire-client/ , which would then add around 260 directories to that CF_DATADIR folder, where the //themes// folder is located and the //glade-gtk2// folder for the gtk-2 client.
+The process to create an images.tar.gz for the client is described in the Release Guide [[:crossfire release guide#Client]] :
+>>Make an image archive for the client. Need a server tree with a properly linked arch tree.
+>>cd lib; adm/collect_images.pl -archive
-:!: The client unfortunately does not (yet) download the files into //CF_DATADIR/image-cache//
+A rationale would be to have a shared image folder on a shared computer, so that not every user would need his own image-cache files. The .crossfire/image-cache directory has some 10 to 20 thousand files at a size of 10 - 20 MB for both image sets //default// and //classic// .
+If desired, one can move the .crossfire/image-cache/ content into share/crossfire-client/ , which would then add around 260 directories to that CF_DATADIR folder, where the //themes// folder is located and the //glade-gtk2// folder for the gtk-2 client.
+:!: The client unfortunately does not (yet) download the files received from the server into //CF_DATADIR/image-cache//
 ===== crossfire-images folder =====
@@ Line 55: / Line 64: @@
 The older clients used a variable named DATADIR : \\
 ''sprintf(bmaps,"%s/bmaps.client",DATADIR);''
+====== sound.cache folder ======
+The [[:client:changelog_0_92_1_70_0|ChangeLog]] says :
+>>The sound files are expected to be in either ${HOME}/sound.cache/
+>>or CF_DATADIR/sounds/. No provision exists yet for sound file installation.
+The variable is defined in //client/sound-src/common.h// : #define USER_SOUNDS_PATH "/.crossfire/sound.cache/"