Jump to content

caloyski_65

Member
  • Content count

    24
  • Joined

  • Last visited

  • Battles

    9618
  • Clan

    [PHNAV]

About caloyski_65

  • Rank
    Lieutenant (junior grade)
  • Insignia

Profile Information

  • Gender
    Male

Recent Profile Visitors

252 profile views
  1. [PH] Wargaming Gift Grab

    Hoodies + Bonus Code for WOT & WOWS just arrived.....Thanks WG!
  2. Free Signals code

    many thanks and many more to come.....
  3. Why I keep crashing?

    im sure when WOWS is already out of Open Beta and is a regular game, WG may compress and re size the game client like what they did to WOT and it would probably eliminate that game client crashing problem......WOT had similar problem before when the game client file size was @ 24GB, while playing WOT, my PC would post thIs error message VIRTUAL MEMORY TOO LOW and moments later, the screen would just freeze. hopefully WG wont just move away with win xp / vista x86 / 32bit O/S....but maybe they will stop supporting these O'S in the future.....League of Legends PH already stop supporting win xp SP2 and early version of windows vista only this November.....so for the moment, we may have to start saving some money for a newer computer
  4. Philippines WoWs Community

    IGN: caloyski_65 LOCATION: Majayjay, Laguna
  5. Critical Error

  6. Critical Error

    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) a. 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 б. For the Windows XP it’s different. You need to carefully edit the Boot.ini file 1. With the right mouse button click My Computer and pick Properties. 2. Click Additional tab, click Startup and Recovery, and click Edit next. 3. The Boot.ini file will open, there will be a line looking like: multi(o)disk(o)rdisk(o)partition(2)\WINDOWS=""Microsoft Windows XP Professional"" /fastdetect 4. Copy this line to paste it below, then change the line you pasted to multi(o)disk(o)rdisk(o)partition(2)\WINDOWS="Microsoft Windows XP Professional 3GB" /3GB /userva=2900 /fastdetect 5. Restart the computer. The system will ask you, which version of the OS you’d like to download. Pick "Microsoft Windows XP Professional 3GB". If everything goes right, use the version of OS with 3 GB. If not, you can go back to the initial version by picking the version without 3GB. 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. Edited by Santcoder, 17 August 2016 - 10:08 PM.
  7. Why I keep crashing?

    did tried this fix on my PC that keeps crashing while playing WOWS and it did help minimize crashing.
  8. Why I keep crashing?

    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) a. 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 б. For the Windows XP it’s different. You need to carefully edit the Boot.ini file 1. With the right mouse button click My Computer and pick Properties. 2. Click Additional tab, click Startup and Recovery, and click Edit next. 3. The Boot.ini file will open, there will be a line looking like: multi(o)disk(o)rdisk(o)partition(2)\WINDOWS=""Microsoft Windows XP Professional"" /fastdetect 4. Copy this line to paste it below, then change the line you pasted to multi(o)disk(o)rdisk(o)partition(2)\WINDOWS="Microsoft Windows XP Professional 3GB" /3GB /userva=2900 /fastdetect 5. Restart the computer. The system will ask you, which version of the OS you’d like to download. Pick "Microsoft Windows XP Professional 3GB". If everything goes right, use the version of OS with 3 GB. If not, you can go back to the initial version by picking the version without 3GB. 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.
  9. Why I keep crashing?

    http://forum.worldofwarships.asia/index.php?/topic/17553-performance-qa-useful-info/
  10. that things is probably something that when an HE or AP shells hits the whole ships disintegrates....
  11. SEA Premium Shop

    for whatever WG is offering like DOUBLOONS, PREMIUM ACCOUNT, PREMIUM SHIPS, SIGNALS, SPECIALS, DISCOUNTS in EU, RU, NA, ASIA SERVER should also be given in SEA SERVER......its soooooo unfair that SEA SERVER is being left behind whereas there are also lots and lots of players in the SEA SERVER who are willing to spend money on all these items and more often, SEA SERVER are left with "crumbs".....sigh
  12. USS Missouri. BB-63 is on her way!

    if WG will make the Missouri a premium ship.....it will sell like pancakes like what happened to other Premium Battleships....and WG will probably follow it up with another Premium Battleship.....the Yamato's sister ship Mushashi....so more pancakes to sell.....cha-ching!! $$$$$$
  13. duwing WW1 & WW2 these smoke screens are used to protect other allied ships from the enemy ships....for example a destroyer escorting convoys of transport ships would employ smoke screen in event of submarine or enemy ship attack....however in world of warship, there are few players did employ smoke screen to protect teammates....more often these destroyers are too far from other friendly ships to employ smoke screen effectively and more often these destroyers employ smoke screens to protect protect themselves when being attacked or attacking enemy ships.
  14. what i mean is if secondary guns are already firing on their own whenever an enemy ship or an aircraft is within range, at least make their turret move in the direction of the enemy when firing.....we dont need to control them, we just want to see them, move when firing on their own.
  15. Why do so few Cruiser players use AP ?

    its much easier to destroy any ship that is continuously burning using HE shells.....HE shells easily damaged guns / turrets, torpedoes, disabled engines compared to AP shells..... but if an AP shell hits a magazine below the turret (which is very difficult to do then ur ship and ur enemy ship is moving) then its game over for the ship on the receiving end of an AP shell...for HE shells, you just fire and fire and fire as many HE shells as u can but for AP shells, it has to be a either a well placed shot or a lucky strike.
×