ValveSoftware / ValveSoftware/Fossilize

Can I run fossilize manually?

Open
#151 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
780
Forks
78
PR merge metrics
No merged PRs in 30d

Description

Fossilize can take a bit of time when I want to start a game.
Is there a way I can stick a call to fossilize into a cron job and have it run in the background regularly?
I tried the naive approach of copying the call from ps, resulting in the following:

~/.local/share/Steam/ubuntu12_64/fossilize_replay \
  ~/.local/share/Steam/steamapps/shadercache/570/fozpipelinesv5/steamapp_pipeline_cache.foz \
  ~/.local/share/Steam/steamapps/shadercache/570/fozpipelinesv5/steam_pipeline_cache.foz \
  --on-disk-validation-whitelist ~/.local/share/Steam/steamapps/shadercache/570/fozpipelinesv5/steam_pipeline_cache_whitelist \
  --replayer-cache ~/.local/share/Steam/steamapps/shadercache/570/fozpipelinesv5/replay_cache \
  --master-process --quiet-slave --shmem-fd 132 --control-fd 145 --spirv-val --num-threads 3 \
  --device-index 0 --timeout-seconds 10 --implicit-whitelist 0
Fossilize INFO: Attempting to map shmem block.
Fossilize INFO: Using control FD as sentinel.
Fossilize ERROR: Failed to add control_fd to epoll.

Is the file descriptor created outside of fossilize? If so can I manually do it?

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the fossilize_replay invocation and the --shmem-fd, --control-fd, --master-process, and --quiet-slave options shown in the report. Determine whether this invocation is supported outside Steam and document the required setup, or clearly state that manual cron execution is not supported.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
cli
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.