Troubleshooting
This page collects answers to common questions and issues. If your problem is not covered here, please contact us.
The application will not start, or the viewport is blank
Ornatrix App renders its viewport with Vulkan and requires a GPU and driver that support Vulkan 1.2. If the App fails to start or shows nothing in the viewport, update your graphics drivers to the latest version, and confirm your hardware meets the Minimum System Requirements.
An operator does not behave as expected
Many surprises come from operator order or strand type. Operators are evaluated bottom to top, and each expects a particular kind of input - some need guides, some need dense hair. If an operator seems to do nothing or the wrong thing, check that it is in the right place in the stack and acting on the right strand type. See The Operator Stack and Hair and Guides.
Hair does not follow my guides well
Poor interpolation usually traces back to the guides. Keep guides sparse and evenly distributed; clustered or uneven guides produce artifacts. Adjust the guide distribution in Guides from Mesh Operator rather than adding more hair. See Hair from Guides Operator.
Roots shifted after I changed the mesh
Root generation is topology dependent: changing the distribution mesh's topology can cause roots to regenerate and disturb a groom. Finalize your base mesh topology before investing in detailed guide work. If you subdivide the surface at render time, use the Smooth Surface Operator at the top of the stack to keep roots aligned.
The viewport is slow on a dense groom
Reduce the load while working: display a fraction of the hair (see Hair and Guide Viewport Display), lower viewport detail with the Detail Operator, or edit a thinned version with the Strand Filter Operator. Raise these back up for final output.
Animation flickers
Some operators recompute every frame and can flicker during playback - the Normalize Strands Operator is the common culprit. Bake such operators before rendering or animating. See Baking Hair and Guides.
A referenced file is missing after moving a groom
If a groom cannot find a texture or cache after being moved, its file paths may point at locations that no longer exist. Add the file's folder to the search paths, or embed the file in the groom. See Managing External File Paths and Editing Operator Properties.
Multiple windows hang the application
The optional multiple-window mode is experimental and can occasionally cause the App to stop responding, which is why it is off by default on Windows. If you hit this, disable the option and save your work regularly. See Multiple Viewport Windows.
The application says I cannot save
The demo version cannot save your work. To save and load grooms you need a purchased or evaluation license. See Evaluation License and Demo.