Guild Wars 2

Please continue discussion on the new forums.

Hey folks, be sure to give the latest build we just dropped a try.

1083 is a database protection error. It normally clears within a few minutes.

PiXY.6841:

One more log… Does it still make sense to post the logs? The error is always the same…

Unique logs from each person are best, so if it’s the same repeatedly then you don’t need to worry about posting it.

The reports so far have been quite helpful; so thank you everyone for posting them!

We’re still investigating it (and other issues.)

This is a quirk of Windows. Turning off Num Lock appears to fix it.

It’s a bug. We’re looking into it.

“You cannot send to yourself” would suggest OP still has the character associated with their account.

One will likely have to wait for us to clear beta character data before one can use the name once again.

Could you post the *—> Crash <— * section of the details?

Okay. We think we have a bead on what is happening with the keyboard, though it’d be good to get some confirmation from some of you.

Open Terminal, and run the game via command line. If installed in the default location, this would look like:

open /Applications/Guild\ Wars\ 2\ 64-bit.app/Contents/MacOS/GuildWars2

This will open a second Terminal window that will fill with text as the game runs. Play the game as per normal until you encounter the bug. Quit the game. Once the game is shut down the Terminal window should have a final line saying “[Process completed]”. If you could save the entire log from this window and post it that would help us confirm our suspicion and get us one step closer to resolving this frustrating bug!

Saving the log:

1. ?A (Edit > Select All) will select the contents of the window
2. ???C (Edit > Copy Special > Copy Plain Text) will copy the now selected contents
3. Open TextEdit or your favorite text editor
4. ?V (Edit > Paste)
5. Save the file
6. Reply to this thread with the file as an attachment

Thank you!

Here’s an experiment for those of you hitting the keyboard bug: turn off autocorrect.

For newer versions of macOS this is in the Text tab of Keyboard Preferences.
For older versions of macOS this is in the Text tab of Language & Text Preferences.

New theory to test: turn off autocorrect

For newer versions of macOS this is in the Text tab of Keyboard Preferences.
For older versions of macOS this is in the Text tab of Language & Text Preferences.

Menadena.7482:

Sorry, I could not find the mega thread, is it still here?

it’s here

Menadena.7482:

Anyway, I was in my guild hall doing gathering and suddenly my arrows were working but other keys were not working. I had to use my mouse to quit the client and come back. I checked and it did not switch to another keyboard.

Unfortunately this is really something that should be addressed before the 64 bit is the only option for mac people. It is not like this is a graphics bug as you can not predict when it will happen.

As I’ve stated a few times now, it’s been incredibly difficult to reproduce in-house.

I have a couple theories about it that I’d love for you to try if/when it happens again:

The first theory is to press each of the modifier keys, one at a time. Possibly testing if the keys work again after each. Left and right versions of the keys matter here too. The specific keys to try are Shift, Alt/Option, Command and Function.

The second theory is to Cmd-Tab/task-switch to another app and back. Finder works for this.

Thanks

Have you tried starting the game with the -windowed command line argument?

Have you tried this with the 64-bit client? (You can get it from your account page.)

While we don’t recommend using it long term… the command line arguments -email, -password and -nopatchui can be used to bypass the launcher.

The keyboard issues are being investigated.

Consider using this thread for continued communication about issues.

@Illumine.5962: I believe you should be fine to try it. The machines we have listed are the various machines we’ve been able to directly test the client against. It’s not an exhaustive list.

We’re continuing to investigate the keyboard issues and the graphical problems being reported (here and in-game).

@Menadena.7482: Gamma on Mac is interesting: it affects the entire display. It’s currently limited to full screen due to being in parity with the Windows client.

This post may be of interest.

For some users there may be a client crash when entering full screen. This will be hotfixed soon. It may also happen when resizing the window.

Workaround: use -windowed via command line to ensure you play in windowed mode for now.

This was fixed with today’s build. Apologies to those affected.

In preparation for Path of Fire’s release the 32-bit Mac Beta client will no longer be available for download. Existing installs will continue to function for the time being as we prepare to transition everyone to the 64-bit client. We apologize for any inconvenience this may cause anyone.

Nyx.6532:

i am not on a mac. win10.
but after you did this update i have started to have wierd choke lag, like my PC can’t handle it in certain situations.
never had this before, didnt change anything on my system and i am running a Beast of a machine så nowhere near maxing out my cpu, ram or gpu (planty of hardware space, ssd).

not sure how your changes to make it compatible to mac should have any effect on win10 performances but this is my experience since the patch a couple of weeks ago. (didn’t write on the forum before now as i assumed it was on my system and was doing a ton of testing to figure out the issue, however i cannot replicated anything like it in any other game nor benchmark testing).

Your issues are quite unlikely to be connected to the Mac client work.

Menadena.7482:

Jon, what hardware setups are you using? It might be as simple as a physical memory overflow and people are using the stock 8 GB.

Then again, I have managed to crash it rarely with 24. I do concur it seems to happen more often lately though.

Our machines range from 4 to 16 GB of RAM at this time.

We have some fixes/changes going out next week.

Regarding the utility in sending crash reports: it is quite helpful to send them when possible, but not absolutely necessary. At minimum, it let’s us know how potentially bad or how many users it seems to be affecting, which helps us try to prioritize things.

@EchoPadder.7546: Thanks for the video.

For those having the keyboard problem, is it keyboard layout related.. i.e. is the game switching layouts on your or some other behavior?

We are actively investigating the crashing. Unfortunately it hasn’t been easy to reproduce internally.

Thanks for the latest reports! We’re investigating them.

It appears both of you have found the instructions for the 32-bit client. We have yet to complete the hook up for the repair dialog in the 64-bit test client.

If you have the 32-bit client already installed (in Applications) the data is shared there, otherwise (by default) it is stored within the 64-bit app.

That could possibly be the quarantine system in the OS trying to protect you. If you drop it in the Applications folder, run it (to free it from quarantine) then move it I think that might work… (this is completely untested and purely theory)

MaxOS.7531:

Any heads up if there will be an update to the client in the next release? ^^

If all goes accordingly, there are several fixes in this coming release.

MaxOS.7531:

Also, any information if MumbleLink is coming to the new client anytime soon?

We have nothing to share.

It functions just like most other apps: drop it wherever you wish. If you have the 32-bit version installed in the default location it’ll try to continue to use your existing data file, otherwise (by default) it’ll store it in the 64-bit app.

Do note that performance may be degraded when using an external storage device since that puts extra work on the system.

Talek.6795:

Jon, can you please look into the mouse stuck issue?

It’s in the queue for investigation.

Your particular issue is a bit difficult for me to diagnose, given the pictures provided.

Have you tried the 64-bit test client?

Frusen.3761:

• You can’t ctrl+l.click for linking into chat

I wanted to single this out to clarify it. Ctrl+Left-click is an alias of Right-click on Macs, so we use Cmd+Left-click for chat links instead.

Frusen.3761:

However, the addition of Fn to the touchbar for the new type of MacBooks is VERY much appreciated <3

<3

Pretty much everything else you called out, we’ve been investigating at some level.

Thank you to everyone giving continued feedback! We don’t have any particular news of coming updates to share at this time, but are continuing to monitor threads such as this for new issues.

fifteen annoying forum bugs… >_>

There were no changes related to the test client in the latest hotfix. We have a few changes in the upcoming release, with a bunch further down the pipe.

The correct url is help.guildwars2.com

Unfortunately the link from the forums cannot be updated at this time.

There is an option in the General tab under the Camera section which refers to using gestures for turning the camera. Turning this option off may fix your issue.

Draxx.8247:

For the old 32-bit wrapper client, I found this reddit post that helped edit some config files to improve performance:
https://www.reddit.com/r/Guildwars2/comments/3nbh4a/how_to_instantly_boost_fps_on_mac_client/

Will doing these tweaks make the 64-bit version worse? Are these same configurations used on the 64-bit version? Are there tweaks in here that could improve?

The 64-bit client does not support tweaking it in the same fashion or really any fashion that isn’t supported via in-game settings (or existing command line arguments.)

Talentix.3719:

If I Play with the New Client my Menü Bar from Mac comes up everytime if I go with my mouse over the skill Bars in The Game. So I can’t play because my Mac Menü/Bar is in my way.

What OS version are you running? Can you post a screenshot?

For anyone having login issues, we’d like you to contact customer support as they are best equipped to help you there.

We’re busy investigating things and working on improvements. Keep the feedback coming in!

Thanks!

Thank you everyone for your continued feedback and reports.

Aradream.2475:

Hey, I can’t get my “@/#” key (mac keyboard) working with the new mac client. How come ?

Have you tried the <> key (next to left shift)? There is some internal code that can swap <> and the @# keys. We should resolve that mix up in an upcoming release.

Lorelei.7809, could you post your Macbook’s specs including OS version?

Thank you!

Mighty.7548:

One thing I have come to realize is that the “Magic Mouse”, which comes with new Macs, has default settings which make it behave similar to a track pad. If you swipe with two fingers, for example, it will move you to another Spaces desktop. There are other gestures like that, too, such as gently double-tapping will do the Mission Control (or Expose’ as it was once referred to). These gestures cause the game to crash. Go to Settings, Mouse, and then there are two tabs: Point & Click, and More Gestures. Uncheck all of those features, except for the “Secondary Click” feature under the “Point & Click” tab. The Secondary Click option merely allows you to right-click on things.

I suffered through dozens of crashes all day long, then I turned off those features and I have yet to crash since I did that about an hour ago.

As far as I know we haven’t seen crashes from any of these behaviors. I’ll be interested to see these crashes when we get back into the office Monday.

Mighty.7548:

Also, within the game, there is a setting which allows you to alter the gesture so that instead of angling the camera, you zoom in and out when swiping up or down. That default setting seems very backwards to me.

The direction is based on your mouse scroll direction settings.

Silverkey.2078:

the game does not recognize which scrolling mode you selected (the default new scrolling or the reverse).

Odd, it should. Have you posted your hardware information and other details? What mice are you using? I’m curious to see it.

Thank you!

RavBunneh.6854:

For me, both the normal mac client and the 64 bit client now get 66% lower frame rate at all times in all areas. Pretty much entirely unplayable. I don’t know what you did, but for me it isn’t working; it is working a lot worse.

Can you post your system specs, what resolution you are using in-game (and if you are scaling your display), what in-game settings you were using at the time and the map(s) you tried this in? Thanks!

You may have an extension blocking some of the content.

Mighty.7548:

It turns out I spoke too soon. My mac is brand new and amazing, yet the game crashes constantly. Its not as bad as it was on my macbook because now only the client crashes, and not the whole computer, but the game us UNPLAYABLE right now because it simply crashes like crazy. I login, and it crashes within seconds now.

Is this with the 64-bit test client?

We’ll be looking into options to help alleviate these where possible. I cannot guarantee if or when that will happen though, given prioritization of issues…

Full screen resolution choices are currently limited to whole number divisions of the system given screen resolution. I cannot guarantee that this will change, but we’ll see.

Burrden.2579:

Module: nvd3dumx.dll

This seems to suggest something is going amiss in your Nvidia (graphics) drivers.

Moira Shalaar.5620:

ok, I guess the issue isn’t with [FN] keys as a whole, but only F11 specifically. I tried toggling the Mac settings for the keyboard [FN] key but that does not change F11 not working at all. I do not have that key bound to anything else either.

F11 among several others are system level keybinds by default. We chose to not override this behavior.

Depending on the key and ones hardware fn and/or alt/option may need to be held to bypass the system level setting.

Alternately one can switch the system level setting in System Preferences in the Keyboard panel. Look for something to the effect of “Use F1, F2, etc. keys as standard function keys” However this will generally still require alt/option for some keys unless you also turn off the system level Shortcuts.