Guild Wars 2

Thora.6428:

I hope they (ANET) is not responding in this thread because they are fixing it right now. Otherwise I will be deeply dissapointed. After all , this is a bug, not a balance feature to be added.

Lol, did you not notice the big red response on this very page? I’ll assume not…

>_<

If it’s not a big deal, I’d try just leaving the guild and getting a re-invite to see if that fixes it. If you’re a guild leader that may not be feasible. :p

For the love of God, please fix the Necro minions once and for all…

Flesh Golem (Elite) and the little Bone Minions (x2) like to pick and choose targets, often standing around doing nothing while I attack/get attacked. The Golem in particular will often (and I DO mean OFTEN) run to random mobs and agro them, effectively pulling enemies I do not want pulled and endangering my life.

Minion AI needs a serious overhaul ASAP, especially considering the Flesh Golem is one of our Elite skills. Come on.

We could also benefit from a pet bar, so we Necros could at minimum put our minions on passive or agressive mode. That should really be in the game IMO. I’d be fine with a tiny toggle button [passive/agressive].

Yep, same issue here for quite a while now actually. Seems to happen more when you RUN → STOP → go to RUN again (that’s when it makes your character freeze position, requiring you to, say, release and press a directional movement key again).

Plz fix!

My guildy noticed last night on his Asuran character (Guardian) that he now holds his weapons incorrectly. It was proper pre-patch. Something is amiss with the Asurans.

I should have SS’d it, but he did report it. Can any Asuran characters post a screenshot of this? I doubt he is the only one affected. IIRC, the weapons clip through the Asurans wrists (like they are choking up on the sword) instead of being in their hands.

Edit: Found a pic of the Asuran weapon glitch from another forum thread (with no responses, 4 days ago) – hope he doesn’t mind me borrowing it.

Same issue – would really liked this fixed. :/

Same issue here. Just started happening, if I had to guess, around a week ago. I also believe this is something in one of the patches because I’ve played since release with no freezing issues like this. My PC has not changed. I was using ATI CCC 12.8 when this issue started happening, and since have tried 12.10 WHQL and now onto 12.11b7 – same freezing issue. Sound continues to play normally, I can CTRL-ALT-DEL and quit the game fine; my PC does not freeze entirely, just the GW2 screen.

What’s goings on?

Intel Q9400
8GB DDR2
ATI Radeon 7870 GHz
ASUS P5Q Turbo
650w Antec TruPower
W7 64bit

System has been Prime/Memtest/IBT/Furmark/OCCT stable for ages. This GW2 freezing issue is new to me and I’ve been playing since launch.

Why has this not been addressed? kitten #8230;

Yeah, this issue is EXTREMELY IRRITATING when you are trying to find a group (say, for a dungeon).

If we can’t have an LFG tool, then this ‘algorithm’ needs to be re-worked.

Have been trying most if not all of the ATI drivers since GW2 released (7870 GHz here), and this issue STILL exists. It was acknowledged by A.Net right after release in the Tech Support forum when people started uploading a bunch of pics.

Why has this not been fixed? A.net, you guys said you knew what the issue was then…why does it still exist months later? You could at least tell us if it’s an ATI issue or if it’s a game issue so we know who exactly to blame/bug about it.

And yes the “lines” will actually draw onto your character if you stand over them.

I would also very much like an update on this issue. What’s the deal?

Wth…so this is what causes it! Aha! I use autorun all the time, no wonder…

Fix this please Anet lol.

Fix this plz!!!

Schakal.6091:

… Or I could in a game where Warriors and Guardians were two names for the exact same thing, same with Thief, Ranger and Engineer and of course Elementalist, Necro and Mesmer were just variant spellings of each other too. Which is to say, I’m unconvinced. Which is a nice way of saying it’s a very uninformed point to even make. Which still is way too nice but I’m definitely digressing now.

+1

This is a terrible idea. No need to give explanations as it’s already been covered.

There’s a reason this doesn’t exist in any other mmo/game.

You can already transmute armor and weapons…and now you want to look like another class? That’s laughable. It opens up a whole can of worms, whether you believe or not.

This is almost as bad as the Race Change thread. Almost.

Enigmoid.1264:

Stealth and 1200 range weapon in pvp would be very overpowered.

Wha? It’s not like a Thief can just sit in stealth and fire away. They have 3-5s of stealth MAX (if traited into a defensive trait). Thives’ stealth mechanic in this game is meant to get you out of (or into) hairy situations – you clearly can’t sit in stealth and burst someone down. Doesn’t work.

And let’s not be foolish, either. A Thief is NOT the only class with stealth. Mesmers can stealth, Rangers can stealth, and Engineers can stealth. They may not have as many options to stealth as a Thief, but the options DO exist. Should we make those other classes limited to 900 range, too?

http://wiki.guildwars2.com/wiki/Stealth#Weapon_skills_that_grant_stealth

I have an 80 Warrior (my first 80), and I just hit 80 on my Thief last week. I have 4 more characters rolled and leveling – a Necro, an Ele, a Ranger, and a Guardian. But that’s besides the point.

Here it is:

I do miss having the 1200 range option that my warrior has – who ALSO has heavy armor. It puts my thief closer to a dungeon boss than any other class, even when using Pistols, because everyone ranges them since they hit like Mack Trucks. I don’t like to PUG any of the dungeons for this exact reason.

So please someone give me a legit reason why my heavy-armor wearing Warrior (or Guardian) can attack from 1200 range but my Thief cannot [one Shortbow skill doesn’t count, sorry.]? Why is the Thief stuck with the shortest attack range(s) yet has less armor than a Warrior/Guardian? Oh, Thieves also have the least amount of hit points, too. By a large margin.

How is that balanced?

Heck, I’d be happy if they just extended the range of the pistols to 1200, but that doesn’t make much sense considering that is the range of a rifle, which has a longer barrel. I think the best option would be to make all Shortbow skills 1200 range, as this would prevent A.Net from having to do ANY balancing changes.

Just my 2c on the matter.

I would like an A.Net representative to comment here and let us know if this was an intended design decision or if this is something they are considering implementing in the [near?] future.

I would also like to re-state, being a guild leader, that I would VERY much like to see this implemented ASAP. There are several “Unknowns” in my guild and I would like to know what is up with them, in addition to serving other functions.

Nobody is making you re-roll, that is what you fail to understand.

What will you do when (if) they introduce more races?
The same thing you did in GW1 when they introduced new primary classes.

Start a new character.

raphaeldisanto.5478:

No one’s saying that it’s not technically possible. It’s a computer game, it’s made up of 1s and 0s, of course it’s technically possible.

It’s not a technical decision. It’s a policy decision. I’d be against race changes, too. You rolled it, you live with it.

I couldn’t agree more. If you are already 80 (or even 20+, really) before you realized you were unhappy with your character then that’s user error. Asking for an entire race change is ridiculous. Unhappy with your character? Roll a new one. They give you 5 slots for free, and ways to buy more if you have already filled them. All I really hear is complaining about being unhappy with rolled characters with an unwillingness to start a new one. Sounds lazy to me. :P

Now, GW1 did eventually add makeovers (including sex changes), that you could purchase for real money if you so choose to. That’s the absolute max I would expect to see, but I seriously doubt this is an A.Net priority or will be implemented anytime soon, if ever.

+1 totally agree. As a guild leader I am sorely missing this option from GW1. :/

It does not.

/15char

Smelly Bookah.6957:

I actually like it alot more than what we have now. It was one more thing which made GW1 and GW2 speciall If it was so bad, they would have changed it back in GW1. Not my fault there are so many people who have played WoW and dont like the camera work simply cuz they are not used to it…

Liking something that’s bad doesn’t make it any less bad. If you want the option for smoothing, I’m not against it – never did I say I was. However, forcing it on people was a mistake, which has now been rectified. Not sure how you correlate “camera smoothing” to “special,” but whatever…lol…

Also, I played GW1 for over 6 years, what point were you trying to make talking about WoW? I’m sorry, but it’s not just WoW players that don’t want a laggy camera system, it’s every decent PC gamer out there – minus those that like to hamper their own performance. But to each their own…

MajorMelchett.6042

I do love it, we are asking for a choice and your acting like we are trying to force it back to how it was.

You like the new way (good for you), well I don’t like the new way and i want the OPTION to have the old way – so what exactly is your issue with that?.

Don’t start directing me questions if you can’t even answer mine. Did you just now get overly sensitive to motion after the patch, or are you using some b.s. excuse (like I know some of these others are) about getting sick with a relatively normal camera system?

Oh and FYI, I already said I wasn’t against perhaps having a slider. Please read all my posts before accusing me of saying certain things, okay? K.

ButtonMasher.8245

Different people are different. Why is this hard to understand?

First, this is an MMO, not an FPS, and I kind of doubt that the CounterStrike camera is the same as the WoW camera. Second, I don’t know what the difference is, I just know that it is not good for some of us.

Lol. Okay – I guess I need to break it down for some people. It’s not that I don’t understand that different people are different. I actually understand how a high latency camera (i.e., the “old” camera) could make people sick. The camera rotation didn’t coincide with their physical motions (their hand movements), and this in turn can cause sensory confusion in a select few people, resulting in nausea or “motion sickness.”

What I do not understand, is how a person that had NO prior illness, even using the old high latency camera can now claim to be physically affected by a camera that has little to no latency – the same type of low latency camera system found in nearly every other game in the market – yet doesn’t have issues with any other game, just GW2s “new” camera. If you truly had issues with low-latency, high-response camera systems, then you would have issues playing almost every game on the market.

MajorMelchett.6042:

And if the new camera does the same to people who didn’t have an issue before?.

We aren’t asking for it to be forced back to the old way, we are asking for the choice to have it the old way as the new way isn’t good for us.

What, like you all of a sudden became more sensitive to motion after the update? LOL.

Buttonmasher.8245:

It is not just a personal preference for the old camera. The new camera makes me feel dizzy…

So, wait, a camera with no artificial lag makes you dizzy? I really don’t understand some of you who are complaining.

Have you ever played any FPS (Battlefield, CoD, Doom, etc.)? Do those make you sick, too?

Again, this “new” camera is much closer to what you’d find in those games, or any other game. I don’t see a bunch of posts in their forums about dizziness due to a snappy camera.

What’s the difference?

alphacentari.7692:

The new camera is much better i didn’t like it the other way.

Yeah, pretty much. Just reading topics like this make me laugh, because I swear GW2 must be the first game for some of these people (no camera smoothing makes you sick? what?).

I swear that you guys complaining about the “new” camera have NEVER played any other game before. Ever. I mean…seriously? This is a lot closer to the way every other game camera handles. Don’t come to the forums complaining about how you want some kitteny camera back. That’s LOL material.

Now I’m not at all against a slider maybe, but reversing this change? No way in hell.

Great change with camera A.Net, please keep it up.

Camera/mouse smoothing (interpolation) is terrible, inaccurate, and never implemented properly or reasonably. It should not have been introduced into the game in first place. 95%+ of games do NOT use it.

“I just logged into the game and spotted right away that something is wrong.” – made me laugh. Also the few posts titled something like “The new camera makes me sick!” is just straight LOL material, I mean kitten people…

From the patch notes:

Camera

We’ve updated the camera to reduce the amount of camera smoothing currently in the game in order to lower the frequency of related bugs. We’re still looking into other camera issues, but we decided to make this quick change because it greatly improves the gameplay experience.

Camera/mouse smoothing was removed due to player feedback. The camera now acts like it should, without added latency. This is also how cameras work in 90%+ of all other games. Please explain how that is “awful” or “jerky.” Sounds more like your mouse movements are awful or jerky.

camera smoothing has been disabled (at the request of many, many people), this means that the game now has the latency of every other PC game. I’m not sure what there is to complain about, unless you haven’t played very many games before?

Shifty.6357:

Same issues here with a Rat5 mouse. Tested with ventrilo key clicks. Right click never actually deactivates when it loses focus in game.

This alone proves that it’s not mouse-related but is instead some issue with the game.

Strange issue indeed…still not sure why some people have this problem while others don’t, and how I just started being affected by this within the last couple of days.

This is a game issue – which I am actually suffering from now. I wasn’t when this post started, that’s for sure. Some update or something has broken proper mouse support.

This is on a brand new Logitech G700 (I replaced my old one with a new one 2 weeks ago due to ACTUAL button issues).

I don’t even run Setpoint software – the mouse has onboard memory and I just loaded my old profile to the new mouse via my Laptop (that’s where I keep Setpoint installed as I don’t want bloatware on my PC).

Needs fixing.

Good catch, and even better that you found the issue before you suffered hardware damage from extended heat exposure.

+1 for thermal junction throttling!

That is yet another strange CTD. I can only assume you’ve fixed the original CTD issue (c0000005) – but by doing so you may have uncovered a separate issue. I don’t think your [new] CTDs are related to the c0000005 errors you were getting…have you ran MemTest86+ over night to check your system RAM? That’s probably where I’d start if all your system temperatures check out okay.

Well, unless you are running AfterBurner for separate fan profiles, I don’t really see the need for you to run it at all if you aren’t overclocking. Or do you get the same crashes running CCC instead of AB? If not, I suggest you don’t run either AB or PX, just stick with CCC and see what happens – if you haven’t already.

edit: I assumed you had an ATI card. Even if you have NVidia you can just try running their display driver software in place of AB if you aren’t overclocking.

It’s not your hardware or WinXP. See:

https://forum-en.gw2archive.eu/forum/support/bugs/Collection-of-graphics-glitches
https://forum-en.gw2archive.eu/forum/support/tech/strange-lines-on-floors

It’s either a driver issue or game-related issue pertaining to certain ATI hardware. There have been community manager responses about it in at least one of those threads.

Yes, I necrobump’d this because this issue is still relevant and has not been fixed!

The thread was lagging, trying to figure out who to cull and who not to cull, thus the low performance.

:P J/k of course, but sounds plausible…

IMO (and have had this opinion for a while) AMD should just concentrate on making great GPUs – and perhaps make just enough CPUs to keep Intel in check.

This way perhaps AMD/ATI would have a decent driver programming team, and come out with driver updates more than every 1-2 months (I don’t count CAPs, sorry). Their GPU hardware is solid but after being with Team Red for several generations I can say all of this with honesty…I also used to build AMD CPU based systems, too – back in the day when they were comparable to Intel. The sad fact is I haven’t touched their CPUs since Intel released their first generation Core processor and I don’t see that changing any time soon.

These guys are right though, stick with Intel if you’re looking for a modern performance-oriented CPU.

I’m starting to think that AMD may have issues (driver-related) with their implementations of Tessellation and also possibly Geometry/Occlusion Culling (hence the disappearing terrain – I’ve seen this EXACT issue running Unigine Heaven on my 7870). Hoping they get this junk straightened out ASAP.

Again, PLEASE report these issues to ATI/AMD! Here is the link:

http://www.amdsurveys.com/se.ashx?s=5A1E27D20B2F3EBF

A Core 2 Quad is enough for this game; you do not NEED an i5+.

It is more about clock cycles (MHz/GHz) and core efficiency than the number of cores, etc. Since C2Qs are still very efficient, if you could overclock that C2Q over 3.0GHz you’d see a substantial improvement, and the more the merrier. However, if you can’t overclock on that motherboard and want performance improvements, you’re looking at purchasing either a cheap LGA 775 board that can overclock, or just coughing up the money for a newer i5/i7 setup, but then you’d also need new RAM (requires DDR3).

Currently my gaming rig runs a Q9400 @ 3.60GHz (2.66 stock), 8GB DDR2 @ 900MHz, a Radeon 7870 (1150/1400), and has adequate frame rate in GW2. I didn’t see much improvement in GW2 when I upgraded from my 4890 to the 7870 (and that’s a huge upgrade) – some, but not as much as one would expect. Battlefield 3 – now that’s a different story. That game is way more GPU-bound than this one will ever be, though. I can run any game that I’ve tried on my system at the highest settings (for GW2 I run @ 1080p/60 with AA and Distance Blur off*, High Shadows, and Native Render Mode) and in no way feel that my C2Q is “outdated.”

*I turn AA distance blur off as a personal preference; it doesn’t seem to affect frame rate either way (I despise FXAA and Distance Blur for the same reason: blurriness). The only thing that really seemed to negatively affect frame rate was selecting Ultra shadows.

Loyram, I’m not sure what that crash relates to (I’ve never even seen it – and I’ve seen a whole lot of different CTDs with GW2), so more than likely you have some settings wrong somewhere [display driver, AfterBurner, Windows] or your overclock isn’t stable – I assume you are oc’ing since you’re using AB/PX? One thing I noted with my specific card (7870) with using AB is that it will set the voltage a bit lower than what you manually set it to, so you may want to verify your unloaded/loaded voltage using GPU-Z and FurMark. That may be a specific issue with my card – I’m not sure, but it’s worth checking. If you are not over-volting the card, then you can completely DISABLE low-level hardware access, as it seems to only be needed for voltage control, as far as I can tell. Also, which version of AB are you running? They just released 2.2.4, but I did all my testing with the previous version (I think it’s 2.2.3). I recall them making some Nvidia-related changes in the newer version, so if you get to your wits end, maybe try the previous version.

Thisisdell – I need more info than just “didn’t work” – such as the error you are receiving (full crash report plz), AfterBurner settings, video card make/model (full specs would be better), etc.

I have still been able to play just fine with no CTDs since making the changes in my OP.

FWIW I fully updated Win7 x64 last night and my FPS is still the same – no changes. As in, same fps pre and post updating.

Caedmon.6798:

At all times you should set windows update to Disabled using Services.msc and only enable it whenever you want to check if windows has any updates available.

Yeah, this is a really good idea, and I’ve been doing this ever since WinXP released.

I advise everyone else to do that as well.

^ Methinks this guy replied in the wrong topic. :P

I’ll just add my .02c here for what it’s worth and say that I agree that the mob respawn timer is a little too short. I wouldn’t mind mobs taking 15-30s longer to respawn, as I’ve ran into a few issues such as yours.

Ty sir

I’m hoping for a little optimization both from points 1 and 2, however you are definitely correct in the fact that we won’t see gains of 200%+ and people would be foolish to expect that. We’ll probably still see a bit more FPS gains from new AMD/Nvidia drivers (especially for the newest line of cards), but only a small increase in performance via internal game optimization – unless they decide to overhaul the entire engine.

Good deal. Glad to hear you got it fixed!

Glad to say that I have still not experienced any more of these ‘memory’ CTD – 5 days later, and still going strong!

I’d still like to hear some feedback from other affected users.

Loyram.1829:

I have been experiencing these exact errors since launch/first few new patches. I made my RivaTuner stats match yours, but I use EVGA Precision X and there is not a compatibility option that I see.

Right. I couldn’t find it in Precision X either. It’s one of the options that’s missing from the main settings page vs. MSI AfterBurner.

You should give MSI AfterBurner a shot if you’re still having CTD issues with Precision X. It’s literally the same program, written by the same author, with a different skin (and more options). Just use the settings I recommended and you should be good to go with AfterBurner. You don’t have to uninstall Precision X, either. Just disable it from startup etc., as you don’t want both AB and PX running at the same time.