Da Kril.2695

Can confirm, with action camera on, Scepter skill 3 (Twilight Combo) will not work. Enemy is targeted, reticle is on its face, press 3 and it says "You need to have an enemy targeted to use that skill." Turn action camera off, everything works fine.

OK, on my ticket, we've gotten past all the possible things to do on my end.(repair, kill prefs, switch to new user acct, re-install client, etc.)I've been submitting the "ArenaNet.log" with each subsequent crash, so hopefully that will help them. Here is my lastest response, fyi: so, moving forward! =)

Latest hard crash was loading screen even before getting into Divinity's Reach.

I'm running Mojave version 10.14.6 with the same issue, so it can't be Catalina security that is the culprit.(may cause problems though, just not my problems) =) I have a ticket working too. We are still going through the "repair? security exception? delete prefs?" phase.I will post if anything works/fixes it.

Oh yes, had this as well — before getting in game, immediately after the Wintersday patch, the client wanted to repair game data. @Blur.3465 You're runnng a Mac client in Windows 10? o.0

I am having the same issue. Repaired client twice. Hard crashes in Divinity's Reach.(this is very new; been using the Mac client without issue for years)

Ack, I forgot — it's not Control + Right-click on the Mac; it's Command + Right-Click. Setting/resetting auto targeting is working fine. Please ignore post above. Apologies

Just ran across this today, playing Dragon Ball. I can't set auto attack any more. Control + right-click does nothing.Not just in Dragon Ball — everywhere. Anyone else have this problem?(I haven't had reason to change/set auto attack until today with the Lunar New Year and Dragon Ball returning.) I tried switching mice, switching maps, relaunching. Still nothing. I think this is a Mac client issue, since I used to be able to set auto attack with the old 32-bit wine client.I recall setting auto attack all the time while playing Dragon Ball last year (not yet on the new Mac client). Can anyone confirm or deny this issue? Or suggest a work-around?Thanks in advance.