Browser: add your own folders of brushes, alphas, materials and textures

クローズ
  • 何か問題がありますか？
#170 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

関連するプルリクエストがすでにマージされています。

  • #173 @combwizard による — マージ済み

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
python
領域
desktop

調査の方向性

Start by reading the existing path settings and browser indexing code referenced in the issue: studio.json, radial.json, brushes.keep_index, find_or_rescan, and get_library; then trace how Studio path fields and browser source labels are handled. Add per-kind folders for ZBrush 2026 and newer, searched after ZBrush’s own folders, and preserve old index entries when an added folder is unavailable. Done means picks and browser listings work from added folders, with the listed docs and changed Studio screenshots updated.

索引モデルが issue の本文から書いたものです。

説明

browser enhancement studio

ZOrbit only looks for brushes, alphas, materials and textures in ZBrush's own folders (brushes.brush_sources, assets.sources). There is no way to add a folder of your own, so a library has to sit inside a ZBrush folder to show up in the browser or load from a slot.

That is a big gap for anyone with a large kit:

  • ZStartup is the obvious place for a brush pack, but as far as we know ZBrush loads everything in there at startup. A big kit is exactly what you would want to load on demand, which ZOrbit already does.
  • A library kept outside ZBrush would not need moving when you change ZBrush version.
  • The only workaround is a junction inside a ZBrush folder such as Lightbox\Brushes. The walker follows junctions, but nobody would guess that, and it has to be redone for each ZBrush.

A pick already turns a name into a full path and hands that to ZBrush, so loading from another folder should work as it is. That has not been tried yet.

Scope

ZBrush 2026 and newer. ZBrush 2022 to 2025 keep searching only their own installation for now. A pick there of an item that only an added folder has gives the existing "could not be found in ZBrush" message, as an item that only a newer ZBrush has does today. Extending it to them is a separate step: it needs a test of how an older ZBrush reacts to a .zbp it cannot read, and a check that asset picks refuse a path the plugin cannot be given (not plain ASCII with no short name, or too long), as Tool and Project items do.

Design

  • One list per kind. A single root folder cannot work, because alphas and textures share .psd, .png and other extensions.
  • Searched after ZBrush's folders. The first folder with a name wins, so adding a folder cannot change what an existing slot loads.
  • Stored per PC, beside studio.json and not in radial.json. The paths belong to the PC and often hold a Windows user name, and radial.json goes out with a profile export. The app and the browser are separate processes and both need to read it.
  • Set in Studio, with Browse... buttons, as for the other path fields.
  • In the browser, each added folder shows under its own name, with two folders of the same name told apart. get_library already passes unknown source labels through.

What has to change with it

  1. Unplugged drives (the main one). Any folder that cannot be read makes brushes.keep_index keep the whole old index, and the browser keeps its old list. With a library on a USB drive that is unplugged, a brush just saved in My Brushes would not be found, and every rescan would report an error. Only the missing folder should keep its old entries.
  2. Slow drives. The walk holds _index_lock, and picks look files up behind the same lock, so a slow folder would delay picks. A pick for a missing name also starts a rescan (find_or_rescan, at most once every 5 seconds).
  3. Thumbnail cache. A rescan trims it to 8000 entries (cache_prune(8000) in get_library). One large texture library could go over that and keep regenerating thumbnails.

Left out

  • Lists per profile or per ZBrush
  • Reordering folders, or letting one override ZBrush's own
  • Exclude patterns (a _ at the start of a folder's name already skips it)
  • Network paths, refused as they are for Capture, Tool and Project items. A NAS is a natural home for a library, so this is the limit people are most likely to notice. Fixing the lock in point 2 would make it possible to allow them later.

Docs

menus.md (the search order in Brush and the asset sections), browser.md, studio.md, files.md (the new file), troubleshooting.md (a folder that cannot be read), and the Studio pictures of any screen that changes.

主要言語
Python
スター
2
フォーク
1
平均マージ
47分
マージ済み PR（30日）
62

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

combwizard/ZOrbit のほかの issue

combwizard/ZOrbit の issue をすべて見る

似ている issue

Python の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。