1. Client crashes on configurations with 32-bit OS or a small amount of RAM Hello, everyone! The amount and quality of the content in our game is constantly increasing, and a lot of new functionality is being added. This, unfortunately, does not come “free”, in terms of the use of computer resources. On high-performance configurations, players very rarely encounter any problems related to insufficient resources, but on the configurations with the 32-bit OS’s or a small amount of RAM the client may freeze or crash. In theory, you may never face this problem at all, unless “the stars align” in a certain manner – for example, you get a “heavy” map with the high tier ships. Still, recently the number of resorts to the support related to the World of Warships client crashing on 32-bit OS or small amount of RAM increased. Because of this, we would like to share some advices, which will help many players to up the “survivability” of the client. From the technical side, the problem is related to the physical limit of the maximum amount of virtual memory allocated for the process in the operating system. Official information can be found on the Microsoft website - https://msdn.microso...a366778(v=vs.85).aspx The first line in the table is what is of interest for us, namely: What does it mean? It means that for the game process on x86 systems (Windows XP 32bit, Windows Vista 32bit etc.) the maximum amount of "virtual" memory for the process is 2 Gb, even if the RAM installed is bigger. For the x64 operating systems, the limit is 4 Gb. What is the “virtual memory” of the process”? It’s a full amount of memory, including all the application memory allocation + system calls + DirectX + mapping files into the memory + mapping the video-memory into the process space. It’s important to understand that the “virtual memory” of the process is not the same as what you see in the Windows Task Manager. With the 2 Gb limit, you can only play with the “Low” graphics preset, even if your configuration technically allows playing comfortably with the “Very high” (“texture quality” setting affect the likelihood of crashing the most). Currently, we are actively working to minimize the likelihood of this kind of crashes, but if you are experiencing this problem, try the possible solutions listed below. If your computer has more than 2Gb of RAM, it is recommended to install a 64-bit OS. If for any reason you can’t do so, read on. 1. Increasing the limit on the use of the virtual memory by the process up to 3 GB (only for x86 OS) For 32-bit versions of Windows Vista/7/8, you should do the following: 1. 1. Run the command prompt as an administrator. To do so, in the Start menu/start display enter cmd, press the icon with the right mouse button click and pick “Run as administrator” option. 2. Enter bcdedit /set IncreaseUserVa 3072 in the Command Prompt window 3. Restart the computer. Video instruction 2. For the systems with small amount of RAM (2 Gb) and integrated videocard (IntelHD and others) (for x86 and x64 OS) Switch on the “paging file” (also called swap file). This solution may cause a small drop in performance when the available physical memory limit is hit, but will prevent the crashes by the in-memory system starting to use the swap file. Video instruction 2. Long loading time on Windows 7 In the Windows 7 OS, there’s a defect, which can slow down the time of loading to port and battle more than twice. This problem manifested itself the worst after the client packing. This defect was fixed in one of the Windows 7 updates after the Service Pack 1. The issue appeared in the build "Windows 7 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_rtm.101119-1850)", and was solved in "Windows 7 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_ldr.160408-2045)". Accordingly, this defect affects all builds between them. If you are experiencing a very slow loading into battle (over a minute) and you have Windows 7, try to install the latest updates for this operating system - likely that the problem will go away.