It is worth making sure that your device is running in the most performant mode, usually called "performance mode" or similar. This will be the mode that uses the most power, so it may help to disable "lower power" mode or equivalent. Some laptops might run faster when plugged into a wall outlet since they do not need to conserve power when they are not running on battery.

Anukari uses your device's graphics card (GPU), so other applications that use the GPU can slow down Anukari. For example, Anukari is not likely to work well while a graphics-intensive 3D game is running on your device.

Anukari's own 3D graphics are heavily optimized to avoid causing problems with audio rendering, but for very large/complex presets it may be worth reducing Anukari's 3D graphics quality by going to the Options > Preferences > 3D Quality / Effects menu and clicking Max speed.

If you are a MacOS user, see also: [MacOS] What version of MacOS does Anukari perform best with?

First, once you have lined up the window you are recording, if possible turn off the preview in the screen recording. For example, in OBS Studio you can right click on the video preview and uncheck Enable Preview. This often helps a lot.

Second, you can try changing your settings to use the CPU for video encoding. Note that this may slow down encoding quite a bit, so you will have to experiment to see if it is a viable option. For example, in OBS Studio you can change Settings > Output > Recording > Video Encoder from Hardware to Software. This will increase CPU usage, but may help with Anukari performance.

Finally if you are still having issues, it is often helpful to make the Anukari window smaller and record just the Anukari window and not the whole desktop.

If you wish to use Anukari with a Radeon card despite the lack of official support, one tip is that if you are having weird graphics issues, you can force Anukari to use OpenGL instead of Vulkan by creating an empty file at: C:\Users\YOURUSER\Documents\Anukari\prefer-opengl.txt. AMD's Vulkan support is especially buggy, so this sometimes helps.

Unfortunately, given the unique way that Anukari uses your GPU, MacOS may not notice that there is demand for the performance state to be increased, and fails to turn the GPU hardware up to full power. When this happens, the performance of the GPU is so poor that Anukari is virtually unusable.

So to ensure that MacOS sees that the Anukari is putting demand on the GPU, Anukari has to create an artificial load on the GPU that MacOS is guaranteed to notice. Anukari makes sure that this artificial load uses the absolute minimum GPU resources, but the way it shows up on the simplified MacOS system monitor is as 100% GPU usage.

Highly technical readers may enjoy reading more about this on the Anukari devlog.

An Anukari environment preset is a file with the extension .env.zip, which is a plain zip file that contains two required files (ibl.ktx, skybox.ktx) and one optional file (model.glb). The *.ktx files provide the texture and luminance data for the skybox, and the *.glb file provides a 3D model that will be rendered at 1:1 scale at the origin (see the Vaporwave.env.zip environment for an example). You can look at the Factory environments in the following directories:

The *.ktx files can be generated from any *.hdr or *.exr image file in the equirectangular format. There are many websites that have free skyboxes in this format. To convert the *.hdr or *.exr image file into the *.ktx files that Anukari requires, you can use the free cmgen.exe tool from Google Filament. Download the latest Filament release for your OS and extract the files. In the extracted bin directory there will be an executable called cmgen.exe (Windows), or just cmgen (MacOS). To convert the skybox, the commands look like:

The --size parameter can be used to increase the quality of the skybox, at the expense of larger files. It has to be a power of 2 like 512, 1024, or 2048. Generally 2048 produces very large files with very good quality. The cmgen command will produce two *.ktx files in the Output directory, which you need to rename to exactly ibl.ktx and skybox.ktx. Zip these up and rename the zip file to *.env.zip and then place it in the appropriate UserEnvironments directory, and you'll then be able to load it in Anukari. Make sure the *.ktx files are at the top-level of the *.zip file with no subdirectories:

To include a custom model.glb file, see the section below on how to create *.glb files, and then give the file that exact name and include it in the *.env.zip file that you create.

An Anukari skin preset is a file with the extension .skin.zip, which is a plain zip file that contains all of the 3D model files that Anukari needs in the open glTF 2.0 format. Specifically, the files are in the *.glb binary format. To see a list of all the *.glb files that are required, you can look at the Factory skins in the following directories:

There are many tools you can use to edit the *.glb files, but the simplest starting point is the free Blender tool. Technically you can import the *.glb files directly into Blender via the File > Import > glTF 2.0 menu, but most of Anukari's *.glb files have been compressed using EXT_meshopt_compression which Blender does not yet support. If you really want to import the *.glb, you can do it by using a tool like gltfpack to output the *.glb in a non-compressed format, which you can then import into Blender.

However a much simpler place to start would be with the actual *.blend source files for one of the Factory presets, which have been made available for the Pre-Alpha Classic skin here. This simple skin has everything you need to get started. Be sure to carefully examine the orientation and scale of the 3D models, and note that Anukari's renderer is limited to simple PBR materials. Also, look carefully at the animation timelines. All the animations are done from t=0 to t=1, but some of them (like the oscillator or bow) require that the animation loops, while others (like the mallet) do not.

Once you've made a 3D model, you can export it via Blender's File > Export > glTF 2.0 menu. Be sure to choose the glTF Binary (.glb) output format, and give the skin the right filename for the object it is associated with. Finally, zip up all your *.glb files, making sure that they are at the top-level directory with no nested directories, and rename the zip file to *.skin.zip. Place that file in the appropriate UserSkins directory and then you can load it in Anukari:

Note that Anukari does NOT support all valid glTF 2.0 files. If Anukari is unable to load your model, it will render it as a pink cube. In some cases, Anukari may be able to log information about why it could not load your model. Log files are in these directories:

If your 3D models take a long time to load, or are very large, you can consider using the gltfpack tool to compress the vertices using the -cc option. This can substantially reduce the file sizes and speed up loading.