Jon Olson.8439

Take a look at your System Preferences for Keyboard. Specifically, fiddle around with the "Touch Bar shows" drop down and possibly "Press Fn key to".

@SlippyCheeze.5483: there is no DirectX translation layer in the 64-bit client, which is the only client we support on macOS. The 32-bit client used a translation layer, but it has been unavailable for some time now.

About High SierraAs far as we have measured, none of the problems appear to be specific to High Sierra. When there is a problem it seems to relate to some combination of the OS version and hardware, but not specifically High Sierra (for example, some users were not experiencing high disk I/O before High Sierra, but ended up experiencing them afterwards - the bug itself was not specific to High Sierra). About jitteringWe have collected data internally to understand the issue in greater detail, but don't have more to share about this issue at this time. About OpenGL deprecationDeprecated does not mean gone. OpenGL will continue to work in 10.14. We are discussing our options internally. Unfortunately, since this news is new even to us we don't have much to say on it at this time.

Our developer machines are retail iMacs (non-Pro). The difference is the developer tools loaded on them. More machine specs from users experiencing the issues may help, but it might be worthwhile to wait for the file I/O update to see if it's related in any way.

About the high disk usage About slow I/O problems (incl. invisible mobs) About High Sierra

There's not much that's interesting to tell you all right now. We've been investigating the previously mentioned problems.I posted in the AMA yesterday that we have reproduced some of the performance issues and we believe we've eliminated asset loading as the source. We are exploring other possible sources now.

There are no macOS-specific changes in today's update.

Hello all, since it's been a little while I wanted to post an update: Performance issues on High Sierra are being investigated. We had some blockers that prevented us from investigating this, but they were resolved in the last week.Performance issues (disk reads, I/O, shader hitching) are being investigated. Progress has been made, but we have yet to hone in on the specifics of what is causing this.(@Sonicbug.7341 @Hawken.7932) Can you provide some more details on the locations of the texture flickering?

Currently we believe that display aspect ratio and the fuzzy text problem are unrelated. We have an active work item tracking the text issue, but at the moment there is nothing new to share. Other changes and fixes we've added since this thread was opened: The state of DPI Scaling is now saved in a timely manner (among other toggles that were previously not triggering a save).DPI Scaling is no longer effected by graphics presets (i.e. Best Appearance, et al)The launcher now uses the DPI Scaling setting to adjust its size accordingly. (Windows only)The launcher should now center itself correctly when scaled.For Mac users, the cursor being small when not using DPI Scaling matches the behavior of Windows. For anyone continuing to have fuzzy text issuesPlease post your exact DPI setting along with your OS and OS version. On Windows 10, this can be found in Display Settings; on Windows 7 & 8 it's under Appearance and Personalization; for Windows XP it's found under the Advanced part of Settings in Control Panel. On Mac, whether your display is Retina, and what macOS version are probably sufficient.

It's been a little while since I last posted, so I'll give you all a bit info on what we're working on: We're still investigating long loading times and the reported excessive storage media reads. No ETA for fixes, if any.The cursor being small when DPI Scaling is off is expected as this shares behavior with Windows.

There's nothing interesting to share at this time; it's still under investigation.

@cottonling.1368 : We are investigating why it does not save for some. From some of our experiments the app being blurry may be related to either how it was launched, or having a scaling that doesn't quite line up. We're looking into our options on what and how we can alleviate these.

Hi folks! The update of October 17, 2017, included high DPI aware UI scaling. Since many of you seem to have questions and thoughts about this, we invite you to use this thread for your feedback. Here's a brief description of how it works: macOS and Windows provide a UI scaling value, usually based on the monitor resolution and dimensions. As of Tuesday's patch, we use this in the 64-bit client to scale the in-game UI as well. You can change it in your OS settings, but each OS version will have the setting in different places so please consult your favorite search engine to determine how to change that setting, if you wish to do so. We do want you to know that we are aware that there have been crashes related to this feature, and we hope to have fixes for those very soon. In the meantime, please share your other feedback in this thread.

This crash appears across platforms and is being investigated by the appropriate team.

I believe this is related to the DPI scaling update; which I am investigating.

You can locate the dat in the 32-bit client, moving it into the 64-bit client's dat location. It requires a bit of surgery with the internals, but shouldn't prove too difficult to figure out.

When the 32-bit client is installed in the default location, the 64-bit client will attempt to reuse the dat (provided it can find it). Otherwise the 64-bit client will make its own dat. By default both clients store their dat in the app itself, as this is the most portable. There are various command-line/settings options which can alter where each client will store the dat. The apps themselves can generally be moved wherever you wish. There is some runtime and other internal stores kept within your user Library. I don't recommend moving those files unless you are a more advanced user. We are investigating High Sierra issues. This may take a while though, so we appreciate your patience here.

If all goes as planned, we have several fixes in the next release.

@Justin Time.7054 : we are investigating that crash. @Blair.3796 : both crashes you mentioned also appear on Windows.

For anyone having issues that has yet to post their system specs, please do so. It's under consideration. No guarantee though. While it is possible, it is unlikely.

We cannot distribute the 32-bit client anymore. Sometimes these things don't happen for technical reasons. As for your coloring issues, we have several graphical bugs that we are investigating which may be related.

They are included in the normal release notes .

Not at this time. We are still investigating it.

Hey folks,We’re excited to be launching the Guild Wars 2 Mac 64-bit Test Client today (June 21, 2017), and want to offer you an opportunity to provide feedback and ask questions in this forum thread.Read the blog post here.And an FAQ has been posted in our Knowledge Base.Please share your thoughts! This is a recreation from the old forums. All feedback given there has been noted. No specific reason for anyone to repeat their earlier feedback.