Known issues

General

— Line jumping from the log is slow/glitchy.
We decided not to optimise it in this release. It will be fixed later.
— Log loading may be slow sometimes.
We partially optimised it, but that’s a work in progress. Wait for an update.
— Some gamepads don’t work.
Gamepad support is to be improved in general, if you are on Windows and your gamepad does not work, try using x360-compatible mode. If that still fails, contact us on the forums.
Certain virtualisation software has compatibility issues in their OpenGL drivers.
* Parallels Desktop may create visual artifacts unless no-texture-reuse argument is present in ons.cfg.
* VMware Fusion 8 as well as VMware Workstation 12 have serious performance issues in OpenGL 3.3 compatible mode (enabled by default). To workaround upgrade to 8.5/12.5 and add simulate-reads and no-glclear options to ons.cfg. Another way is to set VM compatibility version to 11 or lower but is not recommended.

OS X specific

— Force feedback may not work.
Force feedback is not supported on most gamepads on OS X.
— Screen tearing may happen on old hardware.
Try force-vsync option in ons.cfg.

Linux specific

— No sound and ALSA lib pcm.c:7843:(snd_pcm_recover) underrun occurred errors.
Run export PULSE_LATENCY_MSEC=30 in terminal before launching the game.
Newer pulse drivers may have issues with parsing PULSE_LATENCY_MSEC environment variable. As a workaround you might have to pass an invalid number (export PULSE_LATENCY_MSEC=NOVALUE).
Another way is to increase audio buffer to a larger value, to do so try adding audiobuffer=8 option in ons.cfg. 8 stands for buffer size in KB and could also be 1, 2, 4, and 16 (default is 2).
— The game may not start or crash with “Audio target ‘pulse’ not available” message.
Launch the engine with --audiodriver=alsa argument or put audiodriver=alsa into ons.cfg.
— Game dock icon may be generic or completely missing.
This is a known bug of Ubuntu Unity and SDL. We have no solution other than creating a “desktop” shortcut, which may still not always work.
— Game window content may flicker while moving the window.
Ignore this. It happens due to some refresh rate specifics of window managers(?).
— Several paths may create issues to launching the game.
When launching the game from a network share on Linux (e.g. from a path like /run/user/1000/gvfs/afp-volume:host=DataCentre.local,user-anonymouse,volume=Umineko) the engine may report that it failed to obtain selfpath. To workaround this issue create a link to this folder in a path not containing any special symbols.

Windows specific

— The game may show “Memory allocation failure!” message and crash on 32-bit systems.
By default 32-bit Windows limits the virtual memory available to user applications by 2 GB. We do not exceed this value, however, due to specifics of Windows Heap memory manager the allocated memory gets fragmented, and a large contiguous memory chunk allocation we need may fail. Fortunately this limit is mainly left for historical reasons, and you can easily increase it up to 3 GB.
Windows Vista and newer:
Run Command Line with administrator rights and enter the command bcdedit /set IncreaseUserVa 3072, here 3072 stands for the amount of memory in megabytes. Reboot your system. To undo the setting enter bcdedit /deletevalue IncreaseUserVa.
Windows XP:
Go to My Computer → Properties → Advanced tab → Startup and Recovery → Settings → Edit. Notepad will appear with a boot.ini configuration file. Find a line similar to multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /fastdetect and add /3GB /userva=2900 to it, so it becomes multi(0)disk(0)rdisk(0)partition(2)\WINDOWS="Microsoft Windows XP Professional" /fastdetect /3GB /userva=2900. Here 2900 stands for the amount of memory in megabytes, it is not recommended to use a higher value but a slightly lower value might perform better in some cases. Save the file and reboot. To undo remove the added parameters.
— The game may not start with Avast Internet Security 2015 installed.
Avast Internet Security 10.4.2233 and possibly some others have a bug in their DeepScan module causing the game freeze at start time. The process will simply appear appear in the process list without a way to kill it. The solutions are to disable DeepScan or to upgrade to 11.1.2245 or newer, which is preferred.
To upgrade to a new version open the program, go to Settings → Update, and press Update Program button.
To quickly disable DeepScreen open the program, go to Settings → General, and untick Enable DeepScreen.
— Game performance may greatly decrease when using Aero themes (Windows Vista, 7).
Disable the Aero theme globally/in program properties or switch to fullscreen mode.
— The game may crash when starting on Windows 7 Home Basic.
A solution is to select Disable visual themes and Disable Desktop composition in Executable properties -> compatibility
— There may be various visual glitches on some laptops with ATI HD 5xxx video cards on Windows 7 x64.
A solution is to update your GPU drivers. Catalyst Mobility 13.4 is suggested. This dll fix is likely going to be required to fix dxva playback after updating. Put atiumd6a.dll, atiumd6a.cap to C:\Windows\System32\ and atiumdva.dll, atiumdva.cap to C:\Windows\SysWOW64\.
— Screen tearing may happen with Intel HD video cards.
The issue happens due to VSync detection failure and the only known fix at the moment is to force enable it in preferences. Intel HD Graphics Control Panel → 3D → General Settings → Custom Settings (set this) → Vertical Sync → Driver Settings (set this).
— Various visual glitches (like black rectangles, missing textures, random glitches) are known to exist with modern NVIDIA GPU drivers.
New drivers seem to select integrated graphics chip for our engine to some reason. A solution is to manually choose High-Performance NVIDIA Processor for our application in NVIDIA Preference Pane → 3D Settings → Program Settings.
— Various visual glitches (like black rectangles, missing textures, random glitches) are known to exist with certain Intel HD 3000 GPUs and newer
This is partially fixed with our Episode 2 and Episode 3 releases, however, you might need to add an extra configuration option to the ons.cfg file. Firstly try a no-glclear option. If it fails to help, replace it with a no-texture-reuse line. This should fix the glitches, however, you might want a more powerful PC with discrete graphics for a better experience.
— The game may freeze after clicking on “Official Site” button on Windows 8 and newer systems.
This is an issue in the way different browsers register themselves in the system. You either need to reinstall your default browser or set Internet Explorer as the default one (IE → Properties → Browser Properties → Programs).
— Force feedback may not work out of the box on some gamepads.
Try using x360-compatible gamepad interface emulation in driver preferences.
— Black stripes or incorrect picture positioning may happen in fullscreen mode.
We know of two causes of this issue, both are only reproducible on Windows.
* scale ons.cfg argument used together with window-width argument setting window resolution lower than screen resolution.
* window-width argument with higher resolution than screen resolution.

Leave a Reply