evilsofa.7296

This is still a constant problem after the Mad King Says event. When a dozen people are spamming the axe, knocking everyone out and completely resetting their costume brawl progress, it makes what should be a fun brawl very disappointing, sometimes taking me 15 to 20 minutes to get something done that should be done in a minute or two. One person in particular I noticed continuing to axe everyone, even after repeated requests to stop, so I submitted a verbal abuse report for lack of a better way of reporting this kind of abuse. I don't know how support is going to figure out what my report was for other than posting about it.

This is the walkthrough:https://www.eightforums.com/threads/cpu-affinity-shortcut-for-a-program-create-in-windows.40339/And I translated that into this shortcut for GW2 64 bit version:C:\Windows\System32\cmd.exe /c start "Gw2-64.exe" /affinity 55 "C\Program Files (x86)\Guild Wars 2\Gw2-64.exe" -autologin -mapLoadinfoYou will need to change the "55" to what gets calculated by the walkthrough, and other things if you don't have a default installation location for GW2. The last two items are GW2 command line arguments that are there to show you can just add them on the end like that. There are other ways to set CPU affinity but they are either not permanent or involve running other applications, and this is just a shortcut that you can use or not use for easy A/B testing.

The i5 8600K has 6 cores. I don't know specifically how well GW2 is optimized for multiple cores but many games aren't for more than 4 cores, especially older titles. GW2 is also a DX9 title, and I have heard that DX9 itself doesn't utilize more than 4 cores very well. i am using a shortcut to launch GW2 that forces CPU affinity to use only the four physical cores on my i7-6700K, and that seemed to make a lot of improvement in smoother play. Edit: here's the link to the post I made about how to make that shortcut.https://en-forum.guildwars2.com/discussion/comment/386880#Comment_386880

I found that the best way to set affinity permanently is with a shortcut rather than an app. This walkthrough was the best: https://www.eightforums.com/threads/cpu-affinity-shortcut-for-a-program-create-in-windows.40339/ Using that, I was able to calculate that the hexadecimal number for setting my 8-core CPU to use cores 0, 2, 4, and 6 is 55, so my shortcut's Target looked like this: C:\Windows\System32\cmd.exe /c start "Gw2-64.exe" /affinity 55 "C\Program Files (x86)\Guild Wars 2\Gw2-64.exe" -autologin -mapLoadinfo If you have more or less than 8 cores, you will need to change the 55 to something else, and you might have to change other things if you haven't installed in a default location or are not using the 64-bit client. And yes, the Guild Wars 2 command line arguments do work if you put them at the end like that. Edit: I used to crash after several hours of playing. it has been 11 days since I started running GW2 this way, and I have not crashed since.

I wonder how many of you are being hit with coinhive, since GW2 players so often have a browser going in the background. Cryptocurrency mining is taking over the malware industry by storm. https://bleepingcomputer.com/virus-removal/remove-coinhive.com-in-browser-miner

No dragons?

I think that in Windows 7, the default DPI setting is always 100%; that in Windows 8.x, the default DPI setting increases to 125% when the vertical resolution is more than 1080; and that in Windows 10, the default increases to 125% when the vertical resolution is 1080 or more.

The good: I have a 24" 2560x1440 monitor, and for the first time I am now able to use the native resolution, set Interface to Larger, and be able to read everything. The bad: well, almost everything. I am now doing the Personal Story, and the text in the Cinematics is extremely tiny. I don't think I've seen any other example of text unaffected by DPI scaling yet. I am using Windows 10 and in Windows' Display settings, I have Scale and Layout set to 150%. I do not seem to have the blurry text problem.

Most of the times I've had PCs shut down, it was bad RAM. PoF uses significantly more RAM than GW2 did before. GW2 may be hitting a stick of RAM that has not otherwise been getting stressed before now. While no software RAM test can be perfect, Memtest86+ has not been supported since 2013, has known problems and should not be used at all. The original Memtest86 is now being supported by Passmark but is not as good as the others. HCI Memtest is the best of the "Memtests", and should be run with as many instances as will fit in available memory (for example, if you have 16GB RAM, run 7 instances of 2047MB each). Finally, the best choice is Google Stress App (GSAT); I have linked how ASUS prefers RAM to be tested with GSAT. I'll quote ASUS on HCI Memtest vs GSAT: "The Windows version of HCI Memtest is a good test for hammering the cache and memory simultaneously. Googlestressap is more memory focused and picks out memory related errors faster than HCI Memtest does." GSAT should be run for a minimum of an hour. An overnight test of 10 hours with either HCI Memtest or GSAT is best to declare RAM or motherboard problems to be extremely unlikely. I have also seen unupdated motherboard BIOS and chipset drivers cause RAM to act bad until they were updated. If you look at changelogs for PC BIOSes, they often consist mostly of "improving RAM compatibility". If you have never updated your motherboard's BIOS or chipset drivers, you may want to try doing that, especially if the RAM tests only throw errors very rarely.

Known good way to save DPI scaling setting without mucking about with files: While in game, toggle DPI scaling to whichever setting you want.Toggle Shadows to any other setting (doesn't matter what)Quit to desktopRelaunch the gameToggle Shadows back to the way you had it beforeDPI Scaling will now be saved the way you want it. This is apparently a long-standing issue that has worked with other settings that wouldn't save in the past. If things still aren't working, did you set your settings file (whichever it might be) to be Read Only in a previous attempt to force settings to save and then forget about that?