OpenSimulator · EN

Cache console commands: fcache

Practical guide based on OpenSimulator 0.9.3.1 source: identify, configure and diagnose caches.

Check the active module and loaded settings before commands. Caches may be cleared, but permanent stores like FSAssets must never be deleted as if they were caches.

Check commands available

These commands are registered by FlotsamAssetCache in the simulator console when enabled. They are not generic ROBUST commands. Availability depends on the running version and module. Consult that process's console help before changes.

fcache status

Displays cache status, hit rates and file/memory asset counts when those layers are enabled. Use this first before considering a purge. It may count many files.

fcache clearnegatives

Clears only the record of assets previously not found. Useful after restoring an asset or repairing a service incident; it does not erase the disk cache or avatar inventory.

fcache clear memory / file

fcache clear memory removes optional memory cache; fcache clear file removes file cache. Bare fcache clear targets both and clears negatives too. Source code also clears negative entries even when memory or file is specified: these actions are not perfectly isolated in their effects.

fcache assets

Scans scenes and tries to cache assets referenced by objects, terrain and other content. It can create substantial reads and remote requests; reserve it for a justified need and quieter periods on large grids.

fcache expire

Purges file-cache entries older than a requested date. Code uses DateTime.TryParse and also accepts “now”; date interpretation can depend on process locale. Do not run fcache expire now without understanding scope: it can force substantial reloading.

Default-asset cache commands: advanced

fcache cachedefaultassets loads default local assets into cache and can override grid versions; fcache deletedefaultassets removes these entries to allow refresh. Source code explicitly warns “use with care”. Avoid using them as generic troubleshooting steps.

What the commands do not do

fcache clear does not delete ROBUST's authoritative assets, persistent FSAssets files, RegionStore objects or Firestorm's local cache. It also does not reset separate user or inventory caches held by other components.

Diagnostic commands

Simulator console commands when Flotsam is active. Start with status; clearnegatives targets missing-result records.

fcache status
fcache clearnegatives

Clear operations: caution

Bare clear targets file and memory layers when enabled. All variants also clear negative entries. Clearing disk cache can trigger substantial reloading.

fcache clear memory
fcache clear file
fcache clear

Heavy or advanced operations

Not routine maintenance commands. expire now is especially aggressive, while default-asset commands can alter cached versions compared with grid assets.

fcache assets
fcache expire now
fcache cachedefaultassets
fcache deletedefaultassets

Managing this cache: practical steps

Suggested order of operations

For diagnosis: start with fcache status. For a stale missing-asset result: use fcache clearnegatives. For a genuinely problematic disk cache: identify the directory, save configuration and plan clearing during a quiet period. fcache assets is a preloading operation that temporarily increases requests and cannot fix an unavailable asset service.

Note on targeted commands

Flotsam source clears negative entries after fcache clear memory or fcache clear file as well. These options are therefore not perfectly isolated among all three layers. These commands belong to the simulator's Flotsam module, not the default ROBUST console.

Identity cache: dedicated command

The fcache commands described here belong to Flotsam. reset user cache belongs to a different module (UserManagementModule) and cache type; its procedure is explained in the account-cache guide.

Full procedure: user cache, checks and commands

More cache guides

Verified sources: OpenSimulator 0.9.3.1