-
-
Notifications
You must be signed in to change notification settings - Fork 413
Description
Checklist
- I am using an up-to-date version.
- I have read the documentation.
- I have searched existing issues.
Description
Current limitation:
At the moment, there’s no dedicated button alongside a field to store and access a path to a file’s original working/DCC source file (e.g. .blend, .psd, .sp), which makes it harder to quickly access and iterate on assets or files.
Why this matters:
Speaking as an environment artist, I’ve worked in several large AAA UK studios where this kind of functionality is commonly built into in-house meta-data tools and file management systems. In game development pipelines, it’s standard practice to maintain two branches of a project:
- A source branch (for files that go into-engine/project — .fbx, textures, audio, etc.),
- A working branch (for original authoring files — Blender, Photoshop, Substance files etc.).,
Often, multiple exported files/assets come from the same working file. Having a per-asset/file working file path field with a button to open in explorer makes it much faster to access that file's source for editing, re-exporting, or actioning feedback — without having to manually track it down in explorer or in the version control package, or manually paste the field in explorer either.
Moreover, if a viable file path is provided by the user (e.g. C:\Users...\Desktop\myfile.blend), clicking the button would open that file directly in its associated software by leveraging native File Explorer behaviour, win-win!.
While this is drawn from my games experience, I believe this feature would also benefit a great many other disciplines with similar workflows (photography, film, music, VFX, arch-viz etc.).
Extra note:
I'm aware of there being a 'Source' field so this feature is somewhat already implemented, but i'll leave the description as is due to the rest of the feature request.
It would also be very useful if this field were included in any backup data files as part of TagStudio, so the information can be preserved across projects or even used in team settings. I love the philosophy behind this application so far and want to see it succeed, so even a basic version of this feature would add huge value for professional users, both commercially and for personal use for a variety of disciplines.
Solution
Suggested solution:
-
Add an optional field where users can paste a path to the original working file (labelled something like Working File Path or DCC Source Path - or just use the existing 'Source' field option).
-
Next to this field (alongside the edit and trash icons), add a button that opens the file path in File Explorer when clicked.
-
Maintain this field's data within the save library backup file.
Alternatives
No response