Guild Wars 2 Graphics Settings on Mid-tier Laptops

Okay, so I'm not a big gamer, but I am a computer geek so it's okay for me to spend more time troubleshooting lag or screen stutter in Guild Wars 2 (GW2) rather than actually play the game :-)

Now, there are many reasons why GW2 would stutter; RAM, Swap Space, CPU cores, heat, poor GPU, etc. I can't possibly cover all scenarios. This little write-up is specific to heat issues.

My laptop is a fairly new Samsung Notebook 7 Spin. I got the lower spec'd model with only 12GB RAM and a 5400 RPM drive. I immediately swapped out the drive for an SSD, but I have never once used more than 12GB of RAM on my personal computer, so I left that as is. This laptop has an NVIDIA GeForce 940MX GPU in it, as well as an Intel I7-6600U. None of these are top of the line, but they aren't shabby either. I got this computer because my HP Spectre x360 mobo fried, it was a refurbished model and there was no warranty. That will teach me never to buy a refurbished computer or an HP ever again. I wanted something with a touch screen, which the Samsung has, and dedicated graphics which the HP did not have. My goal was to have a solid performing laptop that could handle Visual Studio, TFS, Office, and the majority of the games I play which aren't particularly high on the graphics scale. Well, that was what I thought.

When I started playing GW2, after only a few moments it would stutter when turning around. This got worse with more players in the map, more feature rich zones (like Verdant Brink), and anytime I upped the graphics settings in the game for a nicer appearance. I thought this PC should be able to handle it. My ASUS is 5 years old, a 4th gen I7 processor, and using the 560M graphics card, why does it render GW2 so much better and at higher settings?

Heat is the reason (well, that and the fact that my old ASUS was a quad core where the U processor in the Samsung is only a dual - the difference being 8 logical cores vs four, the four had to work much harder). However, I didn't know that right away. When I researched the problem, I found lots of possibilities, but the best website was the Guild Wars 2 Performance Guide. It basically led me to using hardware monitoring tools to observe what my CPU and GPU were doing.

Note that only the OpenHardwareMonitor showed the NVIDIA GPU, the standard Hardware Monitor only showed the Intel GPU which was useless to me. 

Anyway, as I played the game, I noticed that the stutter occurred when the CPU core temps approached the mid 80s and on up to over 90°C. Using some of the information in the guide, I tried to tweak my settings to maximize GPU usage while minimizing CPU usage.

Another note from the guide is that GW2 is designed to use CPU by far more than the GPU. 

The guide only gave me an idea of what to do, but didn't answer the question of what the best settings were.

There were two crucial things I did to remove the stutter almost completely. The first was to change my power settings. The second was to use the frame limiter. Both of these would reduce core temps.

Normally, you would think that when the laptop is plugged in you can simply use 100% of your CPU. However, with a CPU intensive game like GW2, extended use at 100% will overheat the cores, as I had witnessed. The first thing I did to try to reduce this was to change my power options (Power Options > Change Plan Settings > Change Advanced Power Settings > Processor power management; change the minimum state to 5% and the maximum to 90%) so that I only used 90%. It seems, at least with this particular laptop, that Windows is more gentle about controlling the CPU usage when you set a value like that rather than letting the CPU itself reduce the frequency when it detects an overheat condition, which it apparently does rather aggressively resulting in the stutter. While the frame rate (frames per second or FPS) does decrease with a lower CPU usage value, the overall effect is that the CPU does not heat up as much. Naturally, you could just have extra fans or some sort of cooling pad under the laptop. I don't want to carry more stuff with me just to play GW2 on the road, so setting this value down seemed the most efficient way to handle this. I decided to create a GW2-only Power Profile so that these settings would only be in use when I play the game.

The power setting wasn't quite enough though. I also used the setting within GW2 that limits the framerate to 30 FPS max (Options > Graphics Options > Frame Limitation). Why did I do this? Well, if you hover over the option, it indicates that it will reduce power consumption and heat. Oh really?!? It was effective, provided that the settings are such that the FPS would have been increased otherwise. I was able to maximize the graphics settings in GW2 to give me a nice balance of features that used GPU more than CPU and even those that use CPU would not overheat the CPU cores.

Now, one thing to note is that different zones (maps) use different features, so these settings may not be optimal for all zones. That is why I picked 3 zones to play around with, Lion's Arch (generally the most populated zone), Gendarran Fields (a fairly simply PvE zone), and Verdant Brink (a graphically dense PvE zone requiring a lot more CPU and GPU cycles). In the end, I optimized for Gendarran Fields and LA first, then went to Verdant Brink to lower the specs just enough to make it function smoothly there.

Settings in Lion's Arch, FPS sits nicely at 30, GPU usage is high while CPU cores are below 75 degrees.

Same settings from previous in LA, notice FPS is down to 12 and CPU core temp is over 80. A few minutes playing here and the stutter came back. Even without the stutter, camera movements were not smooth.

The biggest change here was to reduce Shadows from Ultra to simply Medium. I also got rid of Depth Blur, it didn't offer much.

You can opt to change whatever settings suit you and experiment with how your system will handle them. I liked using the Windowed mode to observe in real time how changes I made affected both CPU and GPU. However, I would not use Postprocessing as that is done entirely by the CPU. Every time I set that to Low or High, the stutter would come back. As a last ditch effort, you can change the full screen resolution. I know the other guide said it would look terrible, but I found you could still get a decent looking screen by upping the graphics settings and adjusting things like the camera zoom levels, the interface size to small and so on so that it looks closer to native resolution. Hey, what more can you ask of a mid-level laptop?

Audacity Project Check Error

In an odd turn of events, my laptop died. Now, I have a backup on network storage, so I wasn't too concerned about all my Audacity project files. At least, not until after I attempted to restore them.

It turns out that at some point in the past, maybe during backup, maybe at another time, my Audacity .aup files all got renamed to include something like a date and time stamp "Filename (2016_04_27 02_27_25 UTC).aup" Some of my .aup files are duplicated with different values. When I attempt to open the .aup files, I get a message similar to the following:

I've tried to rename the .aup files but I get the same error. Further research shows that the .au files in the _data folders have also been renamed. I confirmed that if I renamed those files by removing the date and time information, the count in the message above is reduced by that number of files for which I've renamed. Furthermore, I can see the audio in the file that was added after clicking OK which wasn't there before. Therefore, the solution to this error is to rename all the .au files by removing the date and time information.

Unfortunately, that is easier said than done. The .au files are small chunks of audio and for my meager library of recordings, there are literally thousands of .au files. Additionally, some of those files do not have the added date and time information and if I were to rename the files, they would either replace the one without the date and time information or they would create a (Copy 1) type designation. Neither of which I want to do.

The short answer is that we need PowerShell to do this if we don't want to spend days correcting these file names.

If you do not know PowerShell and aren't able to follow my instructions, please Google it. I'm not a PowerShell expert and don't have the time or energy to train someone on what I do know. The internet has a lot of tutorials out there so use them first before asking me questions. 

Naturally, the absolute first thing you should do is back up your files. I will not be held responsible for any damage that befalls your data as a result of this solution. I also recommend that you copy the damaged projects to a new directory that is short and easy to get to. My script is using C:\TEMP\Audacity.

Now, copy the following lines and paste them into a file of whatever name you like, just make sure that the file ends with the .ps1 extension. I'll call my file "FixAudacity.ps1".

Get-ChildItem C:\TEMP\Audacity -Filter "*(*).au" -Recurse | Rename-Item -NewName {$_.Name -replace '\s\u0028.+$','.au'} -Force -ErrorAction SilentlyContinue

Get-ChildItem C:\TEMP\Audacity -Filter "*(*).au" -Recurse | Remove-Item -Force -ErrorAction SilentlyContinue

Get-ChildItem C:\TEMP\Audacity -Filter "*(*).aup" -Recurse | Rename-Item -NewName {$_.Name -replace '\s\u0028.+$','.aup'} -Force -ErrorAction SilentlyContinue

Get-ChildItem C:\TEMP\Audacity -Filter "*(*).aup" -Recurse | Remove-Item -Force -ErrorAction SilentlyContinue


Save this to C:\TEMP. To run the file, you'll need to open PowerShell, search your computer for Windows PowerShell and right-click, then select Run as Administrator.

At the prompt, you'll need to set the execution policy that will allow you to run PowerShell scripts. type the following and press enter:

Set-ExecutionPolicy bypass

You will be prompted with a warning. Go ahead and click on "Yes". After running the script, if you are concerned, you can change "bypass" to "restricted" and PowerShell scripts won't run anymore.

Now, at the prompt, type the following and hit enter:

.\FixAudacity.ps1

Depending on the size of your library, it may take a little while to complete, but you'll know that it's done when the prompt reappears. That's it, all you have to do now is test the *.aup files by double-clicking them. If Audacity opens without the error then this worked and you can now copy all the files back into your Audacity Projects folder. Remember to have a backup elsewhere and it is best to delete all the projects that you were correcting prior to copying the fixed ones in. This will ensure that we do not keep any of the bad files.

On some occasions you may get the following error about orphaned files.

As the dialog states, there is no real harm in keeping the files. I have found that all my files work just fine, some data may have been lost but I wouldn't remember what it was so I opted to choose the delete permanently option (after I first verified there were no problems with the continue option).

Incidentally, I believe that the source of the problem with the files being renamed (and probably orphaned) had something to do with Windows backup or File History. My suggestion is that you may want to manually back up this folder to date-named folders on a separate drive to prevent this from happening again.

Cannot expand disk in VMware vSphere Client

Since searching online did not provide a clear answer for this, or at lease not for my exact situation, I've decided to post my resolution in my own blog for whoever might need it. However, the resolution was ultimately gleaned from this other blog.

I have a Server 2003 VM with two virtual hard disks (ignore disk3 as I added that later), I need to increase the disk size of the second disk. This should not have posed any problems. All disks were SCSI and Thin Provision. The second disk is not the OS, nor is it defined to be used for swap space. VMware Tools are installed. There are no snapshots of the VM either. I CAN increase the disk size on other Server 2003 VMs. So, what makes this one different?

To start, here is a screenshot of disk1:



And here is a screenshot of disk2:



Even though disk3 is listed, I added that after the fact. But here is the screenshot of that one and you can see that it can be modified:



I searched the internet for a reason for the differences and couldn't find one. Many mentioned the drive was being used for swap space, others mentioned it would be IDE, and so on. None of that seemed to cover my problem. Until I noticed the drive names. Each of the previous two drives had a -000002 as part of their name, where the third disk simply has _2. I looked at various other VMs that worked fine and noticed that disk1 was ALWAYS the VM name.vmdk and disk2 was ALWAYS the VM name_1.vmdk.

So this suggests something to me about the problem. It is obvious that the disk file isn't correct. A disk migration was attempted and that did not fix it.Then I found the blog that I previously mentioned. In that, post, it referenced the numbers -00001.vmdk as an indicator that there was a snapshot. However, there isn't a snapshot. So, it looks to me that this VM was moved previously (and most likely from one version of VMware to another) while there was a snapshot. I'm guessing that it kept the disk names but consolidated the VM.

My resolution: Make a new snapshot. It will rename the disks to indicate that a snapshot is present. Then I will consolidate the VM to remove the snapshot and hopefully rename the disks appropriately and finally gain access to the Disk Provisioning section. See the screenshots below for proof of the renaming:







As you can see, each has been renamed and they are all unavailable for Disk Provisioning. Now, to consolidate. Consolidation alone won't fix it, you have to delete ALL snapshots which will also consolidate. But once done, you get this:



I can now perform Disk Provisioning as necessary.