CyberCoveLLC/obs-streamer-tools-plugin
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 1 Wiki Activity

docs: the Windows plugin dir is ProgramData, not the config dir #2

Merged
jknapp merged 1 commits from docs/windows-plugin-path into main 2026-09-09 23:44:21 +00:00
Conversation 0 Commits 1 Files Changed 1
+13 -4
1 Commits
Author SHA1 Message Date
shadowdaoandClaude Opus 5 bfc38f45ca docs: the Windows plugin dir is ProgramData, not the config dir
Build / macOS (macos-latest) (push) Successful in 36s
Details
Build / Linux (ubuntu-24.04) (push) Successful in 55s
Details
Build / macOS (macos-latest) (pull_request) Successful in 33s
Details
Build / Linux (ubuntu-24.04) (pull_request) Successful in 1m9s
Details
Build / Windows (windows-latest) (push) Successful in 10m51s
Details
Build / Windows (windows-latest) (pull_request) Successful in 10m27s
Details 
The packaging section claimed `<config>/obs-studio/plugins/<name>/bin/64bit`
is "exactly the layout OBS searches on Linux and Windows". The layout is
right; the base directory is not the same on both. obs-studio's
`AddExtraModulePaths()` uses `GetAppConfigPath` on Linux/macOS but
`GetProgramDataPath` (`CSIDL_COMMON_APPDATA`) on Windows, so Windows scans
`C:\ProgramData\obs-studio\plugins\`, never `%APPDATA%\obs-studio\`
(`CSIDL_APPDATA`) — which on Windows is where OBS keeps its config.

This bit a director on 2026-09-09: a correctly-shaped install under
`AppData\Roaming` produced an OBS log with zero mention of the module. Noted
here because the failure is silent — OBS names any module it finds but cannot
use, so an absence of any line means the file is not on a scanned path at all.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AzGnvQ6wfD7bw7PZN35ft9
 2026-09-09 16:44:06 -07:00