2.3.2 is Out - Page 4

Zurgat · 01/09/08, 12:35 PM

Originally Posted by mek

It's the cubes at Coruu for a Kirin'Var chain. I figured a workaround; you can rightclick the cubes in the brief moment your camera is zooming out after you hit zoom out (mouse scroll for me). Should work with whatever other doodads are currently broken, as well.

That's a seperate issue.
I found it REALLY hard to target those last week as well, but i managed to click them to trying to rightclick right when i'm rotating my character.

I'm talking about the tooltips however, they say "ultis_doodad_1" "ultis_doodad_2" etc instead of "brazier".

Sirloin · 01/09/08, 1:15 PM

Two undocumented things I noticed last night:

Combat log range. My WWS from yesterday was messed up because it appears my combat log range was not 200. I'm at work and can't check my config.wtf, is it possible this reverted to defaults in a patch, or has the range property changed?

Wow and Ventrilo: I use CTRL for my push-to-talk key and this was not functioning at all while playing wow. I had to alt-tab to vent to talk. Anyone else have similar problems?

Buiden · 01/09/08, 2:01 PM

Originally Posted by Sirloin

Two undocumented things I noticed last night:

Combat log range. My WWS from yesterday was messed up because it appears my combat log range was not 200. I'm at work and can't check my config.wtf, is it possible this reverted to defaults in a patch, or has the range property changed?

Wow and Ventrilo: I use CTRL for my push-to-talk key and this was not functioning at all while playing wow. I had to alt-tab to vent to talk. Anyone else have similar problems?

I use CTRL for PTT and it worked fine for me. RE ROS we've never gone OOC since our first kill in July and we finally did last night!

Snowy, the first rule about Shade of Akama is we don't talk about wiping to shade of akama

The only nice thing about the minimap dots are as the raid leader I can tell at a quick glance if everyone is with us... but they are too clunky and take upt oo much space to be much more useful than that. A better system would be to be able to display who you see, healers, dispel/decursers, etc.

constantius · 01/09/08, 2:22 PM

Originally Posted by Sirloin

Combat log range. My WWS from yesterday was messed up because it appears my combat log range was not 200. I'm at work and can't check my config.wtf, is it possible this reverted to defaults in a patch, or has the range property changed?

Combat Logs have been max-limited at the usual 40 yards for a while now. Apparently people were observing buffing/etc by their opponents in pvp arenas (with 200 yard setting), and this gave them advance knowledge of the match, so they nerfed it. This has been true since 2.3 at least.

Kazanir · 01/09/08, 2:46 PM

That's false. Changes were made to arenas to prevent that but the combat log range in 2.3.0 was not capped at 40 yards.

Karmen · 01/09/08, 3:03 PM

Anybody else's ping improve with the patch? I deleted the registry edits and logged in, for over an hour I was at 400-800ms. Put the registry edits back in, re-booted and logged on to a 150ms. A bit disappointing to say the least.

Ele' · 01/09/08, 3:16 PM

Owning a Collector Edition of the game, I was surprised to find in the mailbox of all my toons a letter sent by Master Handler Sylvester giving me the same item as when you create a new character (* Gift Voucher) and who's used to get a collector pet (mini diablo, etc). When I try to use it on a character who already have one of those pets, I get a "You already have completed that quest." message. (So sad, I would gladly adopt a second small friend :'( ).

psk · 01/09/08, 3:16 PM

I just was in WSG near alliance GY, got Blind, and with speed like 2xsprint, ended almost near hut ... (that is lower - never had such strange pathing even with fear)

Anyone noticed something similar with Blind?

Caligula · 01/09/08, 3:19 PM

Since the registry settings affect all games I didn't bother to delete those entries. When I originally made the change a week or two ago I did go from 200ms down to 100-150ms and I didn't notice any other speed increase since the patch.

I'm not sure why you would be disappointed in anything but Microsoft for failing to implement the fastest network latency possible without making obscure registry entry changes, though.

Baalzaman · 01/09/08, 3:19 PM

Originally Posted by Karmen

Anybody else's ping improve with the patch? I deleted the registry edits and logged in, for over an hour I was at 400-800ms. Put the registry edits back in, re-booted and logged on to a 150ms. A bit disappointing to say the least.

WoW Forums -> 2.3.2 Nagle's algothim not fixed (screenshot)
Remarkably, this is the first time a "blue" has commented on this issue that I can recall.

In short keep using the registry changes, the Blizzard "fix" is ineffective.

PSGarak · 01/09/08, 3:25 PM

Emeraude: WoW Forums -> [Bug]Whirlwind offhand crits, Flurry/Rampage
Offhand whirlwind crits not procing flurry (or rampage) have been added to the known issues list.

♦ pewsey · 01/09/08, 4:56 PM

Originally Posted by Aoife

He wasn't bugged for us tonight, but as someone else said it's been off and on.

First attempt wasn't bugged. He respawned with 6 spectators. Bugged.

Mekasha · 01/09/08, 4:59 PM

"Hortus: The tooltip for Icy Veins is a bit misleading, it provides 20% haste not 20% cast reduction. 20% haste as Duman explains provides less than 20% cast reduction. The ability is working correctly and the tooltip is going to be updated in a future patch."

Obviously I'm bad at math and missing something. Right now IV brings fireball from 3.00 to 2.50, which is something in the realm of 16.5% haste? 20% of 3.00 should be 0.60, making fireball 2.40s. I vaguely recall this wording being used when they changed Mind Quickening Gem ages ago, but even applying that in this case it would make your cast time 80% of base which should in theory still be 2.40s unless I'm horribly mistaken and making some obvious oversight.

Docjowles · 01/09/08, 5:04 PM

My understanding is that haste works like this:

Hasted Cast Time = Cast Time / (1 + %Haste)

Using fireball, HCT= 3 / (1 + .2) = 2.5

So no, if you see IV reducing your fireball cast to 2.5 seconds, then it is providing exactly 20% haste as Hortus said.

Kyth · 01/09/08, 5:20 PM

Originally Posted by Jitka

WoWInterface Downloads : Alternate Blips

Found it with Google. WoWInterface's default search isn't fuzzy.

It's a Gello original mod updated by a fan for 2.3, which is located here:

WoWInterface Downloads : Alternate Blips Fan Update for 2.3

I didn't find that the mod changed the dots enough to make it clear, but I modified the tga to also change the alpha of the raid icons.

Attached is a tga that puts a lower alpha on the "raid members" minimap dot than on the party dot to make it possible to see your raid, but yet VERY easy to see your group.

(I may also change the file so the raid icons are a different color, not just light/dark blue differences, but I'll do that after I test it tonight this way.)

Kyth · 01/09/08, 5:39 PM

I went to AV and that still didn't stand out enough once you got people overlapping, so I re-added the white border to your party members. It's in the attached file (making a separate post because I'm not sure how much the forum likes uploading two files of the same name as attachments to the same post.)

Also, a screenshot (the semi-transparent blue circles without the border are raidmembers):

Mjollnir · 01/09/08, 5:51 PM

I've been having lag spike issues since 2.3.2 hit. I've updated xperl UF, removed xperl, checked processes on Task Manager... nothing.
My screen will freeze randomly between 5-20sec at random intervals. Only twice now have I been d/ced. Standard ping is 140ish (pre-patch I hovered around 230ish), but once these spikes hit, I'm in the 1k range for about half a minute following.

Has anyone else experienced these issues? Have you managed to resolve them, and if so, how?

KooZ · 01/09/08, 6:54 PM

1st attempt akama : 'normal' pull
2nd attempt : bugged again...

expertise buff for warriors in battle/zerker stance is quite nice for prot farming

Katria · 01/09/08, 7:10 PM

Originally Posted by Mekasha

"Hortus: The tooltip for Icy Veins is a bit misleading, it provides 20% haste not 20% cast reduction. 20% haste as Duman explains provides less than 20% cast reduction. The ability is working correctly and the tooltip is going to be updated in a future patch."

Obviously I'm bad at math and missing something. Right now IV brings fireball from 3.00 to 2.50, which is something in the realm of 16.5% haste? 20% of 3.00 should be 0.60, making fireball 2.40s.

A common mistake with haste...haste is a % increase in casts over time, not a % reduction in cast speed. Think of it this way...what if you had 100% haste? Your cast speed should be 1.5 right (casting 2 fireballs in the time you usually cast one)? By your math, 100% of 3.00 is 3.00, making fireball have a 0s cast time. That's obviously not right. Imagine a melee character with 100% haste...with a swing time of 0s, you'd instant-kill anything.

I vaguely recall this wording being used when they changed Mind Quickening Gem ages ago, but even applying that in this case it would make your cast time 80% of base which should in theory still be 2.40s unless I'm horribly mistaken and making some obvious oversight.

With a cast time of 3s, you cast 5 fireballs in 15s. 20% haste means you cast 6 fireballs in 15s, or 2.5s per cast.

20% haste means you can cast 20% more spells in the same amount of time...and from that you can derive your actual casting time reduction. If instead it was a flat reduction in cast time, more haste would give exponential (instead of linear) benefits. Clearly there are limits for casters due to the GCD...but haste works the same way for melee attacks. Not that I would mind an exponential benefit from haste...

zeidrich · 01/09/08, 7:20 PM

Originally Posted by Mekasha

Obviously I'm bad at math and missing something. Right now IV brings fireball from 3.00 to 2.50, which is something in the realm of 16.5% haste? 20% of 3.00 should be 0.60, making fireball 2.40s. I vaguely recall this wording being used when they changed Mind Quickening Gem ages ago, but even applying that in this case it would make your cast time 80% of base which should in theory still be 2.40s unless I'm horribly mistaken and making some obvious oversight.

DocJowles explained the actual formula.

Extrapolate what would happen if your situation was in fact the case. Then imagine what would happen if you had 100% haste. Your spells would all take 0 seconds cast time.

Now imagine what would happen if you had 100% melee haste. Your autoattacks would have 0 seconds cooldown. You would be doing infinite white dps.

The problem is, if you use your method of haste, it increases returns

Hasted cast time = cast time * (1-haste percentage)

Then:

25% haste = 75% cast time
50% haste = 50% cast time
75% haste = 25% cast time
100% haste = 0% cast time

Hasted dps = white DPS / (1-haste percentage)

At 25% haste you would do 33% more damage
At 50% haste you would do 100% more damage
At 75% haste you would do 300% more damage
At 99% haste you would do 9900% more damage
At 100% haste you would do infinite more damage

Using Blizzard method of tracking haste, which is:

Hasted cast rate = white cast rate / (1+haste percentage)

Then:

25% haste = 80% cast time
50% haste = 66% cast time
75% haste = 57.1% cast time
100% haste = 100% cast time

And damage dealt equals:

Hasted DPS = White DPS * (1+Haste Percentage)

So:
25% haste = 125% damage
50% haste = 150% damage
75% haste = 175% damage
100% haste = 200% damage

Which is much easier to deal with and balance around.

If we used the other formula, haste, and haste stacking would be wildly overpowered.

Brakar · 01/09/08, 7:32 PM

Originally Posted by KooZ

1st attempt akama : 'normal' pull
2nd attempt : bugged again...

expertise buff for warriors in battle/zerker stance is quite nice for prot farming

Has anyone that one shot Akama have it bug? As I mentioned earlier, it bugged for my guild but like the others it was on the second pull after the first pull got us (barely) to a free Akama though the adds killed us before we got Akama dead. Initially, I'm guessing it's something about the Channelers respawning after a wipe so they don't keep Akama controlled.

Playered · 01/09/08, 7:37 PM

The new ready check stuff is really quite handy, not to mention it seems to of fixed the bug where when someone was disconnected, or clicked not ready = fucked up ready check that never told you a result.

Kyth · 01/09/08, 7:51 PM

Originally Posted by Brakar

Has anyone that one shot Akama have it bug? As I mentioned earlier, it bugged for my guild but like the others it was on the second pull after the first pull got us (barely) to a free Akama though the adds killed us before we got Akama dead. Initially, I'm guessing it's something about the Channelers respawning after a wipe so they don't keep Akama controlled.

Yes, last week.

Ele' · 01/09/08, 8:12 PM

[Netherweave Net] now stack by 20

.

Orestus · 01/09/08, 9:26 PM

We've had times when Akama has been bugged from the moment we saw him, and other weeks where after a wipe it bugged.