Files
Toastconcern--FrameStudio/docs
ToastconcernandClaude Opus 4.8 c1ff887477 Remove the pc-streaming folder
Deletes pc-streaming/ (the experimental Windows D3D11 compositor proxy that
tried to make a home SteamVR's environment on a tethered PC, with its .def,
installer .ps1/.bat and notes) and everything that pointed at its files:

- CMakeLists: the frame-home-d3d11 proxy target.
- build-studio.sh: the Windows pc/ staging and the d3d11.dll build step.
- CI: the pc-home-windows job and the Windows Studio job's download/staging
  of FrameHome-PC-windows-x64.
- Studio: the Windows branch of the "This PC" installer (it ran the deleted
  .ps1); the feature is now Linux-only, where it installs the Vulkan layer.
- README and docs: the Windows PC download row, the PC-streaming highlight,
  and the dead Frame-Home-on-a-PC / pc-steamvr.md links.

FRAME_HOME_PC and the runtime OpenVR/Vulkan loader stay, so Frame Home still
builds for a PC; only the pc-streaming folder and its wiring are gone. The
Linux PC layer (layer/) and its install path are untouched.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
2026-10-21 23:59:40 -05:00
..
2026-10-21 23:22:34 -05:00
2026-10-21 23:59:40 -05:00
2026-10-21 23:59:40 -05:00
2026-10-21 23:22:34 -05:00

Frame Studio and Frame Home documentation

Guide What it covers
Getting started What the two programs are, system requirements, downloads, first launch, a 5-minute walkthrough
Preparing the Steam Frame Developer mode, SSH, the headset's address, an SSH key and a frame entry
Installing Frame Home Three ways to install, what goes where, updating, uninstalling, the off switch
Using Frame Home The Environments panel, adding environments, moving around, every setting
Environments and .fenv The .fenv format, converting homes with fenv-tool, per-world settings and tuning
Performance How Frame Home reaches 120 fps, checking it, fixing stutter, Studio's own pacing
Frame Studio guide The Studio window, tools and panels
Bundles Several environments in one .fbundle file
Building from source Building on each system, the CI, the headset side, the repository layout
Troubleshooting Symptoms and fixes, logs, the self-test