Import/Export
Wolvenkit Import and Export explained
Last updated
Wolvenkit Import and Export explained
Last updated
This section contains general information and workflow documentation about importing and exporting files with Wolvenkit.
For a documentation of the UI, check Import/Export Tool:
JSON export will generate a text file. If you don't know what that means, ignore this option, or read more about it under Import/Export as JSON
For a detailed explanation of the different settings and their workflow, check the nested pages or use the "next" button at the bottom of the page.
raw folderMoving or renaming files usually breaks the import. Read on to find out why.
When exporting a resource, Wolvenkit puts the exported file into your project's raw folder. In the UI, you can find it in your project explorer:
The relative paths (starting under archive/raw) are the same, as will the file name (without extensions).
You can import your_file.glb via Import Tool.
You can not import your_file_mesh_export.glb via Import Tool, because Wolvenkit won't know where to put it.
Wolvenkit knows to ways of exporting files: to JSON, or via the Export Tool.
Exported files will be created in your project's raw folder. The will be the same.
Unless importing from JSON, Wolvenkit can't create files.
When using the Import Tool, we can only import into already existing containers (see #file-structure for more information)
The easiest way to do that is:
export an existing file
overwrite the new file in raw with your changes
import the file
This option is in the right-click menu.