Would be nice but they’ve never done it in the past. Mac support is always putting out fires after they’ve burned a large portion of the barn to the ground.
At least it is playable after you blindly guess your way through the black login window (unlike previous bugs with OS updates that literally completely broke the client).
PS: just to be clear, this is probably mostly an apple and cider issue which explains the silence here (part of the reason I hate the cider layer is it creates problems like this)
Screw that. Kill off the Norn and bring in the Tengu. Sylvari have the most interesting anatomy of any of the game’s races, along with a well-realized culture. Norn are nothing but big, ugly human vikings that kinda-sorta turn into animals.
Other way around. The were polar bears turned into sort of humans, supposedly.
Eir, Logan and Zojja’s seems to be in a little bit of a problem, yes. I don’t think they are dying anytime soon, however.
No. You see, Eir was talking with Braham and saying how they will be hunting together and bonding, finally fixing their relationship. That means they are going to kill her. That’s how it goes.
They were pulling the same tricks with Kasjory near the end of LS1, though and most that happened was Spare-Jory #1 died at the start of LS2. So maybe they’ll just kill Garm. (Where the heck was Garm, anyway?)
Breaks don’t help. It appears to be cumulative. The only thing that prevents crashes is restarting the client periodically (which doesn’t help in queued zones like WvW or world bosses).
To be fair, part of the problem is that the posts asking for details is drowned out by the same old refrain of people demanding the port stop using cider.
We need to stop that. It likely will never happen because they’d have to completely re-write the game. All it does is take focus away from real issues.
Anet is hardly blameless when it comes to treating us like second-class citizens (and taking us for granted) but we need to address some of our behavior too.
Ah yeah, that is the only graphics settings that results in no crashes in WvW. No matter your hardware if you crank it up even a little bit you’ll get WvW crashes. Glad things have improved for you, though.
It is more of a technical limitations issue. They replaced a lot of the guts this feature patch. I doubt they have the resources necessary to make text rendering more standard for us when it is readable.
Yeah, I think most of the issue here is from the last winter when we had bugs with increasing severity and very poor communication from Anet regarding fixes (and the duration of time to fix such issues).
Communication has been improving in small bursts and I hope we continue to fix this trust issue with more things like the post asking us to file bug reports. Hopefully we can get more specifics like general areas that are being improved to help give us a heads up for where we might see troubles and where you’d like us to detail things.
I know we’re not real testers but I’d like to think we could at least be slightly useful.
You want us to submit tickets for crashes we had just after the patch hit or new ones? Only crash that made a log for me was on the first day. The rest were the standard WvW crashes that always happen.
Update, game is just as crashy as ever in WvW. Have to put all my graphics settings down to the lowest (I normally run on basically everything as high as I can and get between 30-60 fps) otherwise the instant the enemy zerg gets near I crash.
Well, I was hoping they finally fixed the issue but whatever.
I think you’re still misunderstanding. One of the new processes (maybe the one responsible for the TP) isn’t shutting down on crash. They’re all named “Guild Wars 2” but they’re not all the game engine that make all the graphics for the characters and worlds. Here is another example to help explain this better.
This is my dock running EVE Online (a cider port just like GW2). You may think I’m running 2 instances of EVE Online (running two accounts). I’m not, the left is the game, the right is the in game web browser (or in the activity monitor the one with the higher PID). We probably have the same thing going on here with GW2 but for the TP instead of for a full web browser.
Yeah, there is a reddit thread up too. I’m okay with the change if they provide us with compelling evidence why it was bad behavior (and get rid of the 4 second count down).
Yeah, this update they completely changed the TP engine. Before it was essentially running on IE (5 or 6, i forgot). That was bad. So they had to change somethings around. Hence why they have this wonkiness with multiple processes now. Don’t worry about it too much, this is all intentional (for the most part) and common for cider ports.
The “extras” are normal. They’re not actually all the same process. It is a weird quirk with Cider. One is probably the new rendering engine for the TP. One is obviously the game. I think another one is the launcher.
So don’t worry about it unless you get a crash. Then make sure they’re all terminated otherwise you won’t be able to relaunch.
I liked the idea of it but yeah, this oddly made things worse. They need to significantly reduce or remove the cast time to make this anywhere remotely good (or buff the actual abilities when they do go off).
The only positive I can see out of this is that it makes us do a glyph casting animation much more often now, meaning people might interrupt this instead of say, a heal.
Only problem I have is the cast time for the “new” abilities is a bit too long so it is hard to make use of the ability in a more strategic way (which is what I assume making the abilities activatable was supposed to do). It makes me almost see the change as a slight nerf.
A restart really isn’t necessary, it looks like there are three Guild Wars 2 processes that start up when you launch the game. When you get a crash, one of them never seems to end with the rest of the processes. This means you have to manually go in and quit that last process using activity monitor every time. Are you doing this and still experiencing the problem of not being able to start the game again?
With the new update the auto login behavior no longer works the same. Before the game would automatically log in to my account then start the game after the 4 second count down.
After the patch the game now requires I click the login button manually (the 4 second count down still works).
Was this an intended security change or is it a bug related to your changing some of the guts for the launcher?
If TreeRhino’s having the same problem as I am then the client doesn’t show up as something you can force quit. It’s like it doesn’t exist except you get this annoying error which assures you that it DOES exist… and you can’t do anything about it except reboot. Nothing fixes it for me yet.
Open your Applications folder.
Open the Utilities folder located in the Applications folder.
Open the app Activity Monitor located in the Utilities folder.
Type Guild Wars 2 in the search box in the Activity Monitor window.
Select Guild Wars 2 in the list of applications in the Activity Monitor window.
Click the little stop sign with an x button in the Activity Monitor window.
Confirm you want to quit it.
The work around is pretty much downloading the patch in your web browser and applying it manually. You an also just copy the patched client/app from a prior OS and it will work (why I have a 10.7 virtual machine with GW2 installed still hanging out).
I haven’t had any TP crash problems. I did have one crash loading into a new zone after about an hour and a half of play (about 30 minutes after doing a big group PvE event with settings cranked all the way up to about as high as you can).
The game hasn’t obviously degraded or improved for me significantly at all as far as crashing.
Are we sure this TP crash problem isn’t a server side issue where the server was sending out something funky that was causing the clients to explode? Also, what OS are you guys using? (10.9.4)
The example of them working over time on a fix happened when we the mac users didn’t know when they started looking for the fix and we the mac users created a work around a day or so before they even showed up to acknowledge the problem.
There is no mac development, they stated there is no mac team. This is a hobby port done by Anet. I’m okay with that but they need to stop pretending we’re anything but second class citizens.
(And guys, lets stop conflating client with native client. The cider port is a client, it just isn’t native/use OpenGL, blah blah blah. There are plenty of decently maintained cider ports.)
Oh come on, when have you ever known Anet to promise more than they deliver regarding the Mac client?
As you said, we’re lucky for them to even acknowledge our existence. It would be nice to know if they’re actually going to test the mac patch during a big engine change (unlike last time where they seemed to act like not testing the mac client is somehow something we should have applauded them for…which probably was not what was happening in reality but they sure communicated what was going on weird).
Best case scenario, a lot of our crashing issues in high pop areas are fixed. Worst case scenario, the game breaks severely and they cannot fix it. Likely scenario (historical precedent), they break the mac port and get around to fixing it in a few weeks.
Basically, I wouldn’t plan to play GW2 just after the patch hits just to avoid disappointment. If it isn’t broken, hey great news. Just feel that not expecting more than we’ve got in the past is a good course of action here.
Personally, if the patch hits and the mac client doesn’t explode I’ll go ahead and buy some gems and maybe get Belinda’s great sword or something.
And if you do crash at the very very end it is sometimes worth it to wait a while before logging back in. This way it avoids you logging back in and unable to join your party members while the boss is killed. When you log back in after the boss dies the chest should be there for you.
I have never heard of this problem. Can you give more information about what system you are running on (OS, hardware, if you have any kernel extensions installed, etc…)
The mac client has pretty much always had this problem (and the Windows client to a lesser degree). Best bet when it flares up is to avoid large groups of people (I moved my characters to the grove long long before we knew of the changes to Lions Arch because it help reduce crashing). The only other thing is to reduce the graphics settings. I don’t think we actually know which graphics setting causes these crashes, though. Sorry for being less than helpful. The nature of these crashes makes it difficult to diagnose them.
Sadly, I think them discontinuing support of the mac client is more likely than us magically getting a native client. Not that either are horribly likely. We’ll probably just get something along the lines of “your call is important to us” and maybe they’ll clean up the stickies in this forum again.
Edit: and the topic for the 26th is: Game Improvements. I’m not exactly sure how we fit into such a vague topic but there you go.
Getting back to the actual topic, was the crash for the OP ever fixed?
Calm down, staff ele did lose the ability to see huge numbers, but a 10k meteor shower is OP anyways and they fixed it. On the plus side you got the best skills that work with the new blinding ashes which looks incredibly strong.
why would anyone take blinding ashes its still utter trash and has no reason to be even master tier, when do we apply burning on staff, only with skill 3 and skill 4, what do we sacrifice ? a second armor of earth, an heal on water attune,reduced cooldowns in water and 2seconds stability on earth attune. so we throw away a ton of survivability to get a little buff for 2 skills, so worth the 3g to buy that
That and there is Burning Precision but that assumes the traits work with each other (I haven’t tested that) and the new Glyph of Storms. But yeah, Eles don’t really have many ways to add burning.
That and they’ve probably been working hard for the new feature patch and various events like gamescon.
I’m frankly more worried about the upcoming second year anniversary of the “beta” label than anything else. It is more of a communication issue (not Anet’s forte).
I know this isn’t exactly what everyone else is talking about but could we get a status update on the mac client? Also, the mac client support forums update notes thread is either wrong or worded poorly. It lists bugs as being fixed that are not fixed (or aren’t really bugs, just bad default settings such as the mouse scroll functionality).
I appreciate the cleanup and update you guys did a few months back, just hoping it wasn’t a one time thing (coming up on 2 years of “beta” here soon, just to give you some reference to why we’re frustrated).
A better example is EVE. It is also a cider wrapper and it is actually maintained fairly well. They even mention the mac client in the patch notes relatively frequently. It is a bit insane that CCP support is better than ANet, sadly.
I don’t see how this is different from what they’ve said for every other balance patch before now. At this point I’m just waiting to see what minor/amusing “buff” we get followed by what attempted nerf they try to put in (how many times have they attempted to nerf our elites?)
I honestly only switch over to bootcamp when we have one of those months where they break the Mac client and can’t bother to fix it.
The rest of the time I find the mac client performance acceptable enough (I have to bump my settings all the way down to lowest though around zergs or the client crashes after about 20 minutes, though). I have a pretty high end iMac so your milage may vary.
I’m wondering if this has anything to do with the connection issues GW2 has been having. If the initial startup requires checking a server before doing anything (for instance, to download all the data since you’re re-installing) it could be timing out in the background. Hence why it looks to be hanging.
That is just an avatar, she is the tree you’re in. :p (but yeah, it is kind of weird that the menders run up to her avatar at the end of the story and then immediately lose interest in the avatar)
I died a LOT on this fight. The main issue is having to stop to cast spells (I was using staff on elementalist), so basically my attacks were restricted to the single fireball and lava pool, which has limited use since the vines love to move around.
I suggest using glyph of storms while in earth attunement. This will blind the baddies and allow you to do more long casts.
But crucially, the biggest problem comes from the adds. The dog is annoying enough since you’re already juggling with 3 vines firing red circles around you and a massive amount of AoE. You can run around to kite him, but you just run the risk of running into an AoE, or a vine.
Use lots of static fields, unsteady ground, and shockwave (as well as the previously mentioned glyph of storms) to keep them off you.
The worst however is that vine spouting flower beast. Fight up close, and you’re going to be pummeled to death by the three other vines, fight at range and it unleashes those deadly smaller vines which are nearly impossible to avoid, even if you burn all your dodges.
Yeah, the vine attack is lame because it ignores blind and forces you to dodge a lot. Best bet is to just constantly run around in circles when they’re up.
Still, all in all it was an interesting fight at least. It’s good to see they’re being creative. I dread doing this fight on my tanky guardian though. I have next to no DPS, and my ranged is very limited.
I did this on my cleric geared staff Ele with ease (never downed, never died). I killed the final boss after 4 rotations (have to make sure you’re in fire and with a meteor storm off cd when you kill the final vine).
