Docs

Troubleshooting

Common problems and what to do about them. If none of these fit, report it with the log (see the end of this page).

An edit does nothing

Edits land in the keyform the parameters sit on. When the parameters sit between keys there is no keyform to change, so dragging points, the Temporary Deform Tool and pasting a form do nothing, and the log says the parameters are between keys. Move the parameters onto a key (the key dots in the Parameter palette show where they are) and edit again.

The Deform Brush says it on the canvas: The parameters are between keys: edits land on a key, with Snap to nearest keys to move the parameters that bind the brushed meshes onto their closest keys.

A mesh can't be selected on the canvas

Hidden and locked meshes can't be picked on the canvas, and neither can a mesh inside a hidden part. Check the eye and the lock in the Part palette, or use the shortcuts:

Key
Ctrl+Alt+2 unlock all
Ctrl+Alt+3 show all

The model looks blurry or low detail

When the textures need more video memory than the budget, the canvas says: Video memory ran out: textures beyond the budget draw at lower detail. Close other models or windows to give it back. Close what you don't need, or raise Settings > Performance > Texture memory.

The editor is slow or the fans run

  • Settings > Performance shows what the open model costs under This model.
  • Animation frame cap at 30 or 60 holds playback, physics and Follow to a steady rate and is easier on laptops.
  • A lower Model anti-aliasing costs the GPU less.
  • Renderer shows whether the GPU or the software fallback is drawing. The software fallback is for machines with no usable graphics driver and is much slower; if it is in use on a machine that has a graphics card, try updating the graphics driver.

Video formats are greyed out

MP4, WebM and MOV need ffmpeg. GIF and PNG sequences work without it. You don't have to install it yourself or touch PATH:

  • When Ayatsuri2D starts without ffmpeg, it asks whether to install it. Click Install ffmpeg.
  • Or click Install ffmpeg under the formats in the Render window.
  • The Windows installer and the Linux install.sh offer it too.

It is downloaded for Ayatsuri2D only, checked against its published checksum, and kept with your settings: no admin rights, nothing added to PATH. An ffmpeg you already have on PATH is used first. If you chose Don't ask again, turn Offer ffmpeg back on under Settings > Updates.

A render takes very long

The Render window falls back to the CPU when the GPU can't draw, and a large canvas is then slow. Turn Smooth edges off (a quarter of the work) or lower the Width. See Render.

The model doesn't open in VTube Studio

Export with moc3 version 5.0. VTube Studio and OpenVT read moc3 up to 5.0, so a 5.3 export doesn't open there yet. See VTube Studio.

After a crash

When something goes wrong inside a frame, the editor catches it and keeps running. Something went wrong says the step that failed was undone where possible, where your model was saved, and where the full details are. Copy details puts them on the clipboard, Open log folder shows the log, Keep working closes the message.

If the editor closes before work is saved, the next start shows Recover Unsaved Work with each copy left behind, how old it is and its size:

Recover opens the copy. It opens unsaved, so Save asks where it goes
Delete throws that copy away
Delete All throws every copy away
Later keeps them and asks again next time

Autosave keeps a copy of unsaved work every two minutes.

Logs

The log is the first thing to look at, and the most useful thing to send.

  • The Log palette (a tab beside the Deformer palette) shows what the editor did and any warnings. Open log folder opens the folder the log file is in.
  • Settings > General > Log file: Copy path puts the log's location on the clipboard.
  • Settings > General > Log level: raise it to Debug before reproducing a problem, send the log, then put it back.

Reporting a problem

Open an issue at github.com/Yoru-KenomoVT/ayatsuri_2d/issues. Say what you did, what you expected and what happened, which version you run and on which system, and attach the log. A model that shows the problem helps most, if you can share it.