Jump to content
  • Sign Up

Raider Jones.5120

Members
  • Posts

    16
  • Joined

  • Last visited

Posts posted by Raider Jones.5120

  1. 40 minutes ago, I am Legion.4153 said:

    I'm a total noob when it comes to things like this.. How/where do i type that?

     

    First, you must have a shortcut to the game in your desktop.

    You  must right-click on the shortcut and select "properties".

    In the new window, you must have something like this: "H:\Games\Guild Wars 2\Gw2-64.exe"

    You must change that information with this: "H:\Games\Guild Wars 2\Gw2-64.exe" -usecoherent

     

    Remember that the letter"H" and the route of installation could be different in your case.

  2. From what I can read, Windows 7 is still supported. The only change they have made to the minimum requirements is the need for DX11.

    About Windows 7, I remember that the developers wrote a letter explaining why they decided to use DX11 instead of DX12, and one of the reasons (among many others), was to allow Windows 7 users to continue playing the game.

    For now, the only solution for the error in the launcher is to use the command -usecoherent.

    • Thanks 4
  3. I have experienced this issue in other places. Usually, in surfaces that receved a direct light source. For example, in Kaineng Docks when it is daytime, but not when it is nighttime. In daytime, you can see flickering the boxes, stairs, columns that are oriented to the west. This issue is more severe when Shandows are put in Ultra.

    Here is a video showing that issue:

    https://imgur.com/zvbCQaa

  4. @Carnius Magius.8091 said:It wouldn't hurt to make sure you have the latest video drivers and the latest Directx 9 or 10 updates. I'm running Directx 12. I assume 12 contains the latest 9 and 10 updates.

    Windows 7 only supports up to DX11 and DX12 is only available on Windows 10. However, GW2 basically requires DX9, which is already updated to its latest version from Windows 7.

    Regarding the update of the graphic card drivers, these affect mainly Windows 10 due to the successive changes of the graphic engine of the operating system. In Windows 7, the update of graphics drivers only affects very specific games and very recent graphics cards.

    I think the problem we are all having in this post is related to the changes that NCSoft is making for the future update of the game, as we have all experienced the error almost at the same time and with different system configurations.

  5. I have the same problem as all of you: Crashing when selecting 'Exit to Desktop'. I have a desktop computer with Windows 7 SP1, i7 3770, 16GB RAM, GTX 1070 8GB.

    The funny thing is that until I reinstalled the game today I never had this problem before. Since GW2 came out, I have had it installed on my main SSD disk (C:) (Sandisk Extreme 240GB). Due to lack of space, and in anticipation of future upgrades, I bought a new SSD (Samsung 860 EVO 1TB). This new SSD has the letter H, because I keep the Sandisk SSD as the main disk. The first time I installed GW2 on the Samsung SSD I noticed this error. But I realized that the game was installed at the root of the disk, so I uninstalled it and reinstalled again but in the GAMES folder. However, the error persisted.

    In addition, I have noticed that some games and programs give problems due to how strict some antivirus are. But the game still presents the problem both by disabling the antivirus and by excluding the game folder.

    I hope that an update will fix this error.

    I have seen that the error does not affect the progress of the game (at least, in the objects of the inventory), but after the error, the character does not appear in the same place. Also, with every error Windows creates a crash dump file that increases in size a lot.

    I get two types of errors, but they only appeared in 8 of 10 exists of the game (I have not included all error report):

    ERROR TYPE 1

    --> Crash <--Assertion: !m_refCountFile: x:\perforce\live\naeu\v2\code\arena\services\Handle/Handle.h(70)App: Gw2-64.exePid: 10660BaseAddr: 000000013FA30000ProgramId: 101Build: 105843

    --> Error Logs <--19:02:21Z Failed to open GFE XML: 219:53:59Z NULL REWARD TRACK: 029FAC9B-F852-E311-8757-78E7D193622219:53:59Z NULL REWARD TRACK: 029FAC9B-F852-E311-8757-78E7D193622219:53:59Z Content is referencing a propID that doesn't exist propId='2494386612279056664'19:54:00Z Texture missing mip chain: 0x04812019:54:00Z Texture missing mip chain: 0x04812219:54:13Z Texture missing mip chain: 0x19d40719:54:13Z Texture missing mip chain: 0x19d40d19:54:27Z Texture missing mip chain: 0x1a1edb19:54:31Z Texture '0x03539b' dimensions too small19:54:31Z Loading '0x03539b' texture failed

    ERROR TYPE 2

    --> Crash <--Exception: c0000005
    Memory at address 00000000`a45327e0 could not be readApp: Gw2-64.exePid: 5384BaseAddr: 000000013FE00000ProgramId: 101Build: 105843

    --> Error Logs <--00:18:20Z NULL REWARD TRACK: 029FAC9B-F852-E311-8757-78E7D193622200:18:20Z NULL REWARD TRACK: 029FAC9B-F852-E311-8757-78E7D193622200:18:20Z Content is referencing a propID that doesn't exist propId='2494386612279056664'00:18:21Z Texture missing mip chain: 0x04812000:18:21Z Texture missing mip chain: 0x04812200:18:23Z Texture missing mip chain: 0x1a1ed900:18:23Z Texture missing mip chain: 0x1a1edb00:18:24Z Texture missing mip chain: 0x01350d00:18:24Z Texture '0x03539b' dimensions too small00:18:24Z Loading '0x03539b' texture failed00:18:56Z Texture missing mip chain: 0x19d40c00:18:56Z Texture missing mip chain: 0x19d40700:18:56Z Texture missing mip chain: 0x19d40a

×
×
  • Create New...