Showing Posts For Rhizo.5089:
If a warrior is specced for optimum mobility, you can’t do jack to them if they choose to engage disengage at will. Warriors can be specced to be practically unCCable. They usually will disengage if things start to go badly and reengage when their cool downs are reset. Basically they fish you out until YOU make a mistake. These types of warriors are just as bad as the annoying perma-stealth thieves.
Was there any reasoning given to why this change was necessary?
I fail to see how this would be OP except when the opposition is throwing out many conditions? I say if you are playing against a necro you should adjust you game play and be wary of dishing out conditions in the chance they get shoved right back in your face.
I thought Bhawb had refuted this being a stealth nerf and it being a bug?
“Bhawb.7408
[i]Phenn.5167:
It’s really supposed to be fixed? That’s encouraging. The last I heard/read the devs were saying, “Marks are the best skills evar and the ‘bug’ is working as intended.” I’m glad that’s not the case.[/i]
That was in reference to Putrid Mark, and that dev got shot down by another dev who said they have a fix for it and it should be in on the 26th patch (but he wasn’t sure)."
Am I missing something because I have only seen a few TW tags on SOR since Friday’s reset? What has happened to Indo and co.?
I reported this in the bug section, but I’m wanting to know if others are experiencing this bug? I was seeing this and thought maybe it was lag or something else til other necro’s in my guild complained about the same thing.
The necro fear in a down state doesn’t not seem to be working.
The addition of the new heal provided people use it could be considered an indirect nerf to condition builds?
I’m on JQ and after the second patch, there is very bad lag issues with numerous disconnects. Something got broke. ANET needs to look into this asap.
I would be all in favor for sending them some chocolate cake as long as it had plenty of Exlax in it since it seems that some of them are so full of crap they are beginning to suffer from feces on the brain. After a few runs, they might just come to their senses and realize how bad of a idea that was dumbfire. Unless there is some progression they are shooting for and not making the community aware of their plans, how could they have not reversed course instead of making all sorts of corrections elsewhere without concerns of breaking something.?
I wake up and sign on and all of JQ BL is green and all of FA BL is green and TC owns less than half it’s map. WOW. This short clip is kind of summing up this week even before the weekend is over.
Condition damage can be removed before it damages. A big hitting skill that can be mitigated by up to 90% by the foe (or his teammates) isn’t overpowered. Making assessments about the balance of a skill by assuming that the target of the skill won’t apply a counter-skill is a bit naive.
This is so correct.
To tout DOT’s to the greatest amount of damage that can be done and call for a nerf is totally absurd. If someone dies to DOT’s in this game they really deserve to die every single time for not having condition removal of any sort. I am so sorry that certain specs of classes can be burned down due to changes in the game, but you really need to leave your pity party and respec and adjust your gameplay like everyone else will have to do at some point in this game’s evolution.
I run the same spec within a hammer train. Though, in defense I take the adept trait “embrace the pain” and in the master trait I take “last stand.” The grandmaster trait is a toss up but I chose “defy pain.” The whole concept is to be able to build adrenaline to be able to earthshaker as much as possible. The only thing stopping me from earthshaking more is the cool down on the skill because the adrenaline regen with this build seems almost instant refill. Pair yourself with a guardian and become a god. :P
Out of curiosity .. are all these maps the red ones?
Cos a week or two back we (and a couple other servers) had issues like this, but only on the red maps. It eventually got fixed, but took almost a week.
I think there is verification on the fact that the red borderlands have a bug because many of us in our guild including me cannot play at length at all without getting a client disconnect. I am pretty sure that the devs have been made aware of the problem.
I don’t know if this was ever answered. No searches have resulted in an answer for me. Was there a reason ArenaNet made all yellow inanimate objects not affected by conditions? It would seem only logical that conditions would translate to some sort of decay mechanism on these objects. How much it would affect them would be up for debate so that a team of necros would not be able to melt reinforced keep walls and the like. In certain situations like dungeons, not being able to damage yellows is very unfair and makes necro’s in a sense a liability to the group. Personally I would like to see them allow for some damage to yellows with conditions.
There a few improvement that I would like to see implemented. I don’t think these would be too difficult:
Inviting:
I would like to be able to right click in chat and have the option to invite/join a group. I would also be able to open the guild page and be able to right click and invite/join a group.
Guild:
I would like to see a separate color for dots on the mini-map for guild-mates like gold rather than green when ungrouped. This would allow for better coordination in moving a guild around to accomplish a set task .
Speccing for this trait should match what it says. How can 3 sec of protection make the necro OP’d?
It seems that after one too many crashes the game did a “repair” that lasted quite some time and since then it has been running fine. XX fingers. Still, I have already sent for a new system. Christmas is coming way early this year
I finally was able to load the game by setting the graphics to best performance. Going to order a new vid card rather than chase down elusive bugs :/
After today’s first patch I was getting the disconnect error and crashing to the character screen. Since the second patch to fix this problem now my entire system is rebooting upon loading into an area. I have checked the Nvidia control panel and all seems fine. I have launched Diablo 3 and it runs fine. Any ideas?
Attachments:
I don’t know about fixed. I was getting the same error but now I am getting crash/computer restart upon loading into an area. So I can’t even see if it fixed yet.
Attachments:
Yellow mobs are not enemies. They are neutrals. Even so, necro wells should not heal neutrals.
After a few more days playing I have been adjusting the video settings downward one option at a a time until all the options are flipped to best performance settings. I have tested the first three and no crashes yet.
Ok after 3 days of running in auto-detect mode, pve and pvp, I have had only one issue that occurred under my event viewer and zero crashes to report. The error reported in event viewer was : Display driver nvlddmkm stopped responding and has successfully recovered.
The pause and shift to black screen is exactly the same but in low performance mode the driver never recovers, it crashes.
Black Screen/Crash Issue - I just want to play my game...
in Account & Technical Support
Posted by: Rhizo.5089
One does not go buy a Ford expecting to be able to pull the car apart and put it back together again or tweak it just to get it to run. It is Ford’s obligation that the machine will run reliably to satisfy their customer base. It is ANET that has failed to recognize or discover a problem that seems to affect quite a few people including me. It is solely their responsibility to provide a working model on all machines stated within their min specs requirement.
one does not own a ford expecting it to run completely without maintenance, either by the owner or a garage.
We are not talking about general maintenance. We are talking about lemons.
Black Screen/Crash Issue - I just want to play my game...
in Account & Technical Support
Posted by: Rhizo.5089
I really don’t understand people arguing that people should fix their machines to run the game when it seems to be the game itself is causing the problem. One does not go buy a Ford expecting to be able to pull the car apart and put it back together again or tweak it just to get it to run. It is Ford’s obligation that the machine will run reliably to satisfy their customer base. It is ANET that has failed to recognize or discover a problem that seems to affect quite a few people including me. It is solely their responsibility to provide a working model on all machines stated within their min specs requirement.
As of today, I played the game in best performance mode which is pretty necessary to avoid getting rolled by zergs not rendering in time to scoot away, and the game crashes to black screen with sounds still going or a loud buzzing sound. Then I switched back to auto-detect and played the game for hours with no crashes. I will continue to play in auto-detect mode for a few days to see if the games graphic settings is the culprit. Then I’m going to start turning down features one by one to identify the offending setting if it turns out to be stable in auto-detect.
After playing for for a week or so, I think that I may have identified a possible culprit. Running the game in the best performance settings seems to be the one thing in common in all the crashes. I ran the computer all day long today and I had ZERO crashes in the auto-detect mode which selects the higher settings. Tonight I switched to best performance to WvWvW and within the hour the machine crashed. Can anyone else confirm that this might be their problem too?
I have a GTX285 and had zero problems during the beta events. I updated drivers when AN posted how bad the drivers were for the game and since Nvidia updated them. I have been looking for info on this problem in an effort to solve my problem. The bug is very sporadic. It usually causes a hard lock with a buzzing noise causing me to hard boot the system. This last time the screen seized and went black with all the sounds in the background. I was able to alt-tab out of the game. I looked at the bottom of the screen and saw two instances of GW2 running. Why? I did not launch two instances. If there is a bug that is launching a second instance this would explain a lot.
I too was starting to have black screens of death since the last few patches ago. Going to the Nvidia control panel and under manage 3d settings switching multi-display/mixed GPU acceleration to single display performance mode has seemed to fix the problem for me as well, at least for now. This did not happen to me in all the beta’s and for the first few weeks of game-play. What has changed? It seems that GW2 has a few bugs in it causing fatal crashes since the game used to run fine on the same video driver build that ran perfectly until a week ago.
You have green dots to show allies.
You have blue dots to show party members.
Is it too much to ask for yellow dots for fellow guild members?