Preferences & engine
Use the bundled local engine, choose an optional external installation, and set CPU and working-file preferences.
On this page
Open WQuads in Edit → Preferences → Add-ons, or use the gear icon beside the source name in the WQuads sidebar. The standard platform package includes its engine and runtime files.
Choose the engine location
- Automatic
- Uses a compatible user-installed engine for this version when available; otherwise uses the engine bundled with the add-on.
- Bundled
- Explicitly selects the engine included with the add-on.
- Custom file
- Uses a compatible WQuads engine executable you select. Keep its companion runtime and package files beside it.
- Check
- Checks the selected engine and reports its status. Run this after installation or changing the engine location.
A missing or incompatible selected installation requires repair or an explicit location change. WQuads does not silently switch away from a damaged installation.
Install or repair an external engine
- Choose the matching package.
Use the official engine ZIP matching the add-on version, operating system, and architecture.
- Choose an install folder if needed.
Leave
Install folderempty to use WQuads' user-data location, or choose a writable folder. The folder icon opens the current engine location. - Click Install / Repair.
Select the ZIP without extracting it yourself. After installation, run
Check.
An external engine is optional. For the normal bundled setup, follow the Quick start installation.
Finish running jobs, including jobs in other Blender sessions, before repairing or removing an external installation. To return to the included engine, choose Bundled. Removing the add-on does not automatically remove your external engine folder.
CPU and working files
- CPU threads
- Limits CPU worker threads. A value of 0 uses available capacity up to the add-on's limit of 64 threads. Choose a lower value to leave capacity for other applications.
- Run directory
- Sets the temporary working-file location. Leave it empty to use the system temporary directory, or select a folder you can write to.
Keep files for a support report
Keep successful mesh files is off by default. Enable it before repeating a successful run with an unexpected result if you want its mesh files available for a report.
Keep failed mesh files is on by default. These preferences retain local working files; including them in an exported support ZIP is a separate choice.
See Export a support report for the report contents and export steps. Reports are not uploaded automatically.