apache.1958

I Just completed the meta at Gyala Delve and while Gorrik was speaking as I finishing the scanning the haze hot spots, the map closed and now I cannot progress any further in the quest line (the "Examine strange on-goings..." and "Scan haze spots" tasks show as completed with check marks and are greyed out). This happened to a few others on the same map as mine. We stayed on the map for the next meta, but the issue did not resolve the bugged quest line. Closing and reopening the game did not fix either.

I just had the crash when I tried to switch map instances (right click on a person on another map while in a squad) and when I tried to login, the game would crash before the character load screen with the .exe crash dump window. This happened repeatedly so there was no way to login to the character load screen. Fortunately this exact thing happened to me during the dx11 beta testing period a few months back, and I was able to resolve back then and again today with the same workaround. - These repairs did not work: 1) Relaunch with -repair extension. 2) Relaunch with -dx9 extension. 3) Have the game rebuild by deleting the relevant guild wars 2 files found under AppData/Local and AppData/Roaming. - This worked: 1) Restart my computer under safe mode with networking, 2) Launch the game (Character login screen loads now with no error), 3) Go to settings and toggle off dx11 rendering. Reboot the computer as normal, and no more login issues to GW2. So basically DX11 still is buggy for me though it was toggled on and was stable for me for the better part of a month without this login error. I guess back to DX9 until all the issues with DX11 is worked out.

I agree that 15 achievement pts are lost related to Story Journal EoD Act 1 Mastery, as it went from x/18 objectives to x/19 objectives to complete after this patch. I had mine complete at 18/18 before the patch and now I’m at 18/19. I did not do the hidden achievement “Can Never Be Too Careful” which would be a 19th achievement for me as this wasn’t needed before.

I’m running Windows 10 (old laptop can’t run Windows 11 yet). I ran the game with DX11 beta enabled and I had no issues in the morning until I consistently failed to login in the evening. I checked my Windows update log and there was no update ran between those times. I ran the memory scan suggested. No errors detected. Chkdsk on my C drive (my hard drive is not partitioned) came up clean too. If there is something corrupted, it’s not showing in those logs. Note that I am able to login and play the game after I reverted back to DX11 beta turned off. I did toggle it back on once to recreate the error upon re-logging, and sure enough, it crashes on the login after clicking ‘play’. It’s not something I plan to repeat all that often as it requires me to reboot in safe mode before I can login to the game again and change the settings back to DX11 disabled under settings. Then I reboot my pc again and can play but with the original DX9 settings. It’s unusual as I didn’t have this issue with DX11 enabled until yesterday, and while those update and memory checks make sense to me, they didn’t yield any errors reported on my end. I’ll try this same set of tests after the next patch that includes various DX11 fixes, because I had pretty good performance experience in the beta when it was working. I should also note that running the .exe with “-“-dx9” in the target didn’t seem to work last night during my testing as I would still crash at the login. I thought this was supposed to use the normal version, but for some reason it crashes just like when DX11 is enabled.

I was using DX11 beta daily since the release last month with only seldom in-game crashes, which seemed to stabilize if I lowered the animation settings to the lowest. Performance-wise, I was consistently getting slightly improved FPS and with running slightly higher graphic settings with the DX11 rendering beta on my old Alienware 13 R2 laptop (note that I can't run at highest settings with this old laptop, but most settings could still be tuned up with DX11). Tonight (Tue Oct 13) was a different story. In the morning, everything was as normal, but in the evening (EST), I was getting a crash on login that I never saw before "Exception c0000005 Memory At address 00000000 000000000 could not be read....". I started troubleshooting the wrong way using old developer notes, none of which worked (i.e., I tried the .exe with each of -repair, -dx9, -windowed), cleared the GW folder in the temp cache, did a clean boot from msconfig disabling all non-Microsoft services on startup and disabled other excess tasks from task manager) and none of these incremental changes would get me to the character selection screen as the crash window with the above message would pop up immediately after initiating 'play' on the login menu. The only way I could surpass this was to run my PC off same mode - network, and this allowed me to start up the game with the normal .exe file. While graphics and performance is completely shot in safe mode, at least I was able to login now and change the settings, which I promptly turned off DX11 (and set to windowed to fullscreen). I believe a developer had made some post to this earlier, but I just want to note that this error is new to me as I had not encountered over the last few weeks of DX11 beta testing (and I login everyday), and because it occurs right at the login screen, this may actually prevent testers to enter the game if their settings was already at DX11. Hopefully this gets patched up as I did not have this issue prior to today

DX11 working great in most zones except for Shiverpeak areas. With screen set to windows, my screen will freeze upon performing one or two actions in a zone, like mining a node or mounting/dismounting (Frostforge Sound and Lake Doric - DRM). The same just happened with Fullscreen, but I lasted a good 10 minutes in the area before it crashed. Haven't had crashes in other areas, including WvW which I can play for over hours with DX11 beta, but these PVE areas consistently crash for me with DX11 beta enabled.