Troubleshooting

Overview

This page summarizes common problems and their solutions when using AITuberKit. We will continue to add typical errors and issues along with their causes and solutions, providing detailed explanations based on specific cases to support smooth operation.

High CPU Usage in Chrome or Brave Browser on Windows

Symptoms

On Windows environments, running AITuberKit in Chrome or Brave browser causes abnormally high CPU usage (70%) and may freeze.

Cause

This appears to be a compatibility issue between Chromium-based browsers and Windows environments. This phenomenon does not occur when using Chrome on Mac.

Solution

Use Microsoft Edge browser

• Edge browser keeps CPU usage around 15% and operates normally
• You can also try other browsers like Firefox or Safari

AI Repeats the Same Response

Symptoms

AI characters sometimes repeat the same content twice in one response.

Cause

This is likely caused by the AI being influenced by previous responses.

Solution

• Edit or delete conversation history
• Add instructions in the AI character's prompt settings to not repeat the same response
  • Example: Please respond without repeating the same content.

TypeError: _currentFrameNo when loading Live2D models

Symptoms

When selecting a custom Live2D model in AITuberKit, the following error appears and the model does not render.

Unhandled Runtime Error
TypeError: Cannot set properties of undefined (setting '_currentFrameNo')
  at Cubism4InternalModel.updateWebGLContext (...)
  ...

Cause

• This is a known bug in the pixi-live2d-display library family.
• If the model does not have any clipping masks (ArtMesh ▶ Drawing ▶ Generate Mask), the _clippingManager is not created and remains undefined.
• Inside Cubism4InternalModel.updateWebGLContext, this._clippingManager._currentFrameNo = ++frame; is executed, causing a TypeError.
• Additionally, models exported in Cubism 5 format (.moc3 v4) are not compatible with the libraries included in AITuberKit.

Solution

1. Open the model in Live2D Cubism Editor.
2. Select any ArtMesh, then enable Generate Mask in [Inspector] ▶ [Drawing].
3. Select [File] ▶ [Export] ▶ Model(.moc3), and specify the following in the dialog:
   • SDK: SDK for Web
   • Version: Cubism 4.2 (or 4.0/4.1)
4. Place the output folder in public/live2d/model-name/ and reselect model-name.model3.json in AITuberKit.
5. To enable lip-syncing, add LipSync to Groups in model3.json.

Hint

Adding a mask to lightweight meshes like eyebrows or highlights will also resolve the issue. If you want to avoid visual impact, you can create a new invisible small mesh and generate a mask on it.

Quick Reference for Relevant Live2D Settings

Setting Location	Requirements for Normal Operation	Notes
ArtMesh ▶ Drawing ▶ Generate Mask	At least 1 ON	Any part can be used (eyebrows, hair highlights, etc.)
Model Export	Select SDK for Web / Cubism 4.2 or earlier	Cubism 5 format (.moc3 v4) is not supported
model3.json → Groups	Add EyeBlink and LipSync	No error occurs without them, but expressions and lip-sync won't work

If your model renders correctly in AITuberKit after following these steps, you're all set. For Live2D settings, please refer to this page.

Game Commentary Mode Does Not Show the Screen Share Mini Window

Symptoms

Screen sharing permission is granted, but the mini window that should appear in the top-right corner is not shown. The game commentary countdown continues, but capture fails and no commentary is generated.

Cause

• The screen share preview is hidden or stopped.
• Screen sharing has ended in the browser.
• The selected model does not support multimodal input, or another mutually exclusive mode is enabled.

Solution

1. Start screen sharing from the "Capture" button in the menu and select a sharing target.
2. Confirm that the mini window appears in the top-right corner. If it was hidden, restore it with the show button.
3. In Game Commentary settings, confirm that a multimodal model is selected.
4. Confirm that mutually exclusive modes such as Realtime API, audio mode, external integration, idle, presence detection, or slide mode are not enabled.
5. Check the browser screen sharing indicator. If sharing has ended, start Capture again.