Environment-dependent bugs

This is the problem of Kirikiri and its countermeasures caused by the environmental problem of the end user (secondary user).
We make every effort to avoid environment-dependent problems in the production of Kirikiri, but since the computer settings and configurations are so diverse, environment-dependent problems will inevitably occur.
In some cases, it is possible to deal with individual symptoms, but in general, please take the following measures.
Most of the options that can be set for the Kirikiri engine are for dealing with environment-dependent bugs. See also Command line options.

Environment-dependent symptoms

In the following, "engine setting" refers to an end-user setting tool (engine setting.exe).
The installed data is corrupted
Symptoms include reading error errors such as "Reading error", "Freezing while running the work", "EAccessViolation error", and other unpredictable behavior.
There is a possibility that the installed data is corrupted. Please use "File Corruption Check Tool" etc. to check if the installed data is damaged.
Freeze when switching or skipping screens
If the screen freezes when screen drawing occurs frequently, such as when switching screens (at transition) or skipping with KAG, there may be a problem with the display driver.
Please make sure that the display driver version is the latest stable version, and if it is older, please change to the latest stable version.
Alternatively, it may be improved by changing the setting of "Double buffering method" or "Vertical synchronization wait" in "Engine settings".
If you are using "nView Desktop Manager", a utility that comes with your nVIDIA graphic card, please uninstall or disable this utility.
Screen drawing is abnormally slow
In particular, when the image is enlarged and displayed by Kirikiri when full screen, or when double buffering is explicitly enabled, if the screen drawing is abnormally slow, use the "double buffering method" in "Engine Settings". Changing the setting of "Waiting for vertical synchronization" may improve the situation.
Also, if the enlargement is performed on the engine side instead of on the monitor side, performance may degrade with the enlargement. In this case, if you set "Screen resolution at full screen" to "Nearest resolution" in the engine settings, enlargement will be performed on the display side, but depending on the display, images may not be displayed with the correct aspect ratio there is.
The screen remains black or the image is distorted
Especially when Kirikiri enlarges the image at full screen, the screen remains pitch black, or if the image is disturbed or freezes, "Double buffering method" in "Engine Settings" It may be improved by changing the setting of "vertical syncronization wait".
Video playback fails
If the overlay fails to play the video (displays an error or freezes) or freezes immediately after playing the video, disabling hardware acceleration may help. Displayed by pressing the "Advanced" button in the "Settings" tab of "Display Properties" (a dialog box displayed by selecting "Properties" from the context menu displayed by right-clicking on the desktop) Please move the knob of "Hardware Acceleration" on the "Troubleshooting" tab of the dialog box from the maximum to the direction of "None" and try again.
It is also recommended that you set the script to not play the video.
Alternatively, it may be improved by changing the setting of "Double buffering method" or "Vertical synchronization wait" in "Engine settings".
Intermittent or no sound, or freezes during sound playback
Depending on the sound card and the environment, the sound may be choppy and interrupted, noise may be heard, or sound may not be heard midway. In some cases, the sound may freeze only while the sound is playing.
If it occurs during a transition (switching screens) or heavy effects, set "General-Low Priority" to "Yes" in the engine settings, or set "General-CPU Reduction" to "Yes". It may be improved by setting to.
In addition, it may improve even if you change the setting of "Sound-DirectSound software mixing" in the engine settings.
Alternatively, open "Advanced" of "Sound Playback" on the "Audio" tab of "Multimedia" (or "Sounds and Multimedia" or "Sound and Audio Device Properties") in the control panel, and open the "Performance" tab. Please try moving the "Hardware Accelerator" slider gradually toward "None".
Operation is not successful
If software such as mouse movement support or mouse gesture realization tools is resident, you may not be able to operate the work. Please cancel the resident of such software.
If a third-party (non-OS standard) mouse driver is installed, it may cause problems in the operation system. In such a case, disable or uninstall the third-party driver and use the OS standard driver.
If a gamepad (joystick) is connected to the gamepad compatible software, you may not be able to operate the work due to a malfunction of the pad. Make sure that the button on the pad has not been pressed because something is on the pad.
Also, if the game pad (joystick) is not connected, there is an environment where the pad button is detected as being pressed. In such a case, please disable the pad driver.
Incorrect operation of the center of the gamepad or joystick axis may cause malfunctions. In this case, please adjust the game controller from "Game controller" on the control panel.
If you can not disable the pad driver by all means, you can disable the pad on the Kirikiri side. Please set the "pad availability" to "do not use" in the engine settings.
If you are using a third-party mouse driver, you may not be able to type on the wheel. In this case, setting "Mouse wheel rotation detection method" to "Window message" in the engine settings may improve the situation.
Frequent thrashing
Thrashing (a lot of swap-in / swap-out) can occur frequently due to lack of memory.
It may be improved by setting "General-Memory usage" to "Low" in the engine settings.
However, performance will be reduced, so do not change the option for "General System-Memory Usage" and set "Graphics-Image Cache Limit" to a relatively low value such as "4 MB" or "8 MB" so memory usage may be reduced without significantly degrading performance.