File Explorer

File Explorer keeps the scripts, models, and environments for a workflow in one working directory.

Working Directory

Use the folder button to select a working directory. You can unset it later without deleting the folder.

File Actions

Right-click files or empty space to:

• create a directory;
• use New → Titan Two for a GPC2 script (.gpc), header (.gph), or Input Translator (.git);
• use New → GPC3 for a script (.gpc3) or Input Translator (.ipt);
• use New → Computer Vision for a Python script (.py), C++ source (.cpp), or Python environment definition (.henv);
• rename or move an item to the Recycle Bin;
• show an item in Windows File Explorer;
• compile a .gpc3 into the active GPC 3 slot or assign a .gbc3 to that slot;
• set a .py or .dll as the matching active CV script;
• publish supported scripts, environments, or ONNX weights when publishing is enabled.

Moving to trash asks for confirmation. If Windows cannot use the Recycle Bin, Helios asks separately before permanent deletion.

Drag to Script Slots

Drag recognized local files directly from File Explorer to a compatible slot:

Controller source files are compiled before they are loaded into the destination slot. You can also drag .py and supported CV .dll files to the matching CV script selector. Creating a template refuses an existing filename; choose a new name instead of overwriting an existing script.

Compatible loaded destinations can appear temporarily while you drag a supported resource, including panels hidden by the current layout. Drop onto the matching selector or slot. If no destination is available, load the required plugin and check that it is ready for a file change.

Notes

• Keep script assets beside the script or use paths relative to the working directory.
• Set the correct active script from the context menu instead of repeatedly browsing in its plugin.
• New CV C++ files use the current CVWorker ABI; build them with the SDK included in the matching Helios release.
• Publishing requires Developer Mode, sign-in, a linked Discord account, and a verified email. New uploads also have account-age and size limits. Local scripts can run without publishing access; restricted downloads require their own resource access.