Bow error discussion

[Scraap]

You need to be within 30 feet to get sneak attack with a ranged weapon, or to get the benefit of Point Blank Shot.

This bug really only crops up when the monster, or object (I've seen this happen with barrels), is basically standing right in front of you. We're talking inches of space. Probably the bounding boxes that register the monster is overlapping with where the attack originates from the bow, causing the arrow to shoot incorrectly. But that's just a guess.

All I'm saying is that this bug has been around for a very long time, and it's easy enough to avoid. I am glad it will be getting fixed soon though. I hope it comes with other archery improvements.

So now that were not derailing the original thread further: quite agreed that the bugs been around for a while, as well as somewhat simple to avoid so long as you're in control of the situation. Matter of fact, I'll quite often whip out a bow on the current... *thing* (don't really have a forum-approved-build-name for the particular split-class) for a bit of plinking via SA on something with cold/fire-shield or, say, elite DQ (last time I can remember sweating about it much).

The point I was attempting, perhaps poorly, to make was that a greater number of characters given an incentive to be in mid-range rather than far range due to the recent update will most likely have less time to account for things going pear-shaped (as they inevitably do at times), leading to a higher instance of close-in ranged combat while waiting for that weapons swap to cycle through, which will in turn make the notability of the bug higher.

As such, it is good to hear it will be getting fixed, however, it must be expected that that will inevitably reflect poorly for the first (week? two?) on the implementation while that is being pushed through. Which is concerning.

[Solmage]

I think we're talking about two different issues here, unless you fire 40-50% of your shots at point blank range?

Some classes do. On a related note, can you guys PLEASE increase the sneak attack range with ranged weapons by a good chunk? Else we ARE having to fire at point blank range to get sneak attacks. This will be particularly important now that repeaters may become more popular (and viable).

[Phax]

Some classes do. On a related note, can you guys PLEASE increase the sneak attack range with ranged weapons by a good chunk? Else we ARE having to fire at point blank range to get sneak attacks. This will be particularly important now that repeaters may become more popular (and viable).

As I said, this will be getting fixed. Increasing the range would be something for Eladrin to make a decision about but increasing the range due to the current bug is not a good reason.

[grodon9999]

As I said, this will be getting fixed. Increasing the range would be something for Eladrin to make a decision about but increasing the range due to the current bug is not a good reason.

hotfix or U6?

[Borror0]

Some classes do. On a related note, can you guys PLEASE increase the sneak attack range with ranged weapons by a good chunk? Else we ARE having to fire at point blank range to get sneak attacks. This will be particularly important now that repeaters may become more popular (and viable).

An alternative to fixing the range would be to slowly decrease the amount of sneak attack damage dealt the further you are. In closeish range, a rogue would get his full sneak attack and that amount would slowly decrease the further your target is up until it reaches zero.

Given the fast pace of DDO's combat, that sounds like a better alternative because it is more forgiving.

[Missing_Minds]

***? ?

How can such a critical bug fix not make the release?

Ever hear of "delaying the release by a few days to get in a critical patch" ???

Due to the cycles and releases. People in the industry understand this.

[Phax]

hotfix or U6?

Post U5, Pre U6.

[grodon9999]

Post U5, Pre U6.

Cool, and thank you.

[Geonis]

Post U5, Pre U6.

Now that you've settled the ranged bug, any chance of something on the Thief-Acrobat locking out Ninja Spy issue?

Only been like 4 threads with no response.......

[dj.kickz]

I'm talking about the point blank range(which orthons and devils very much tend to be in, as they teleport there.) but there is another bug

The red named pit fiend in shavarath, that fights the warforged titan, I turned on my many shot, auto-target enabled, selected him, turned on manyshot, he never took aggro off that warforged titan and my hits just were not registering, I think out of the 18-20 shots I fired, I'd say about... 8 or 9 got to roll. Some monster seem to be exceptionally hard to hit, and it seems to be the larger ones, as I do not have them problem on kobolds, but I have seen this problem on beholders.

*edit* also, the pitfiend was at 35% hp when I turned my manyshot on, and I was staying completely still, at about, 40-50 feet away, shooting at him, the problem seemed to stop when I disabled auto-attack and aimed it myself.

i have the same problem with abbot.

[rimble]

An alternative to fixing the range would be to slowly decrease the amount of sneak attack damage dealt the further you are. In closeish range, a rogue would get his full sneak attack and that amount would slowly decrease the further your target is up until it reaches zero.

Intriguing...

[ArdanosMerrow]

I'm talking about the point blank range(which orthons and devils very much tend to be in, as they teleport there.) but there is another bug

The red named pit fiend in shavarath, that fights the warforged titan, I turned on my many shot, auto-target enabled, selected him, turned on manyshot, he never took aggro off that warforged titan and my hits just were not registering, I think out of the 18-20 shots I fired, I'd say about... 8 or 9 got to roll. Some monster seem to be exceptionally hard to hit, and it seems to be the larger ones, as I do not have them problem on kobolds, but I have seen this problem on beholders.

*edit* also, the pitfiend was at 35% hp when I turned my manyshot on, and I was staying completely still, at about, 40-50 feet away, shooting at him, the problem seemed to stop when I disabled auto-attack and aimed it myself.

I've noticed the same targeting problem on Atrikos in shroud and other places you encounter the winged demons. Using Polar Ray with an unobstructed view you will sometimes cast the spell and not hit the mob. The spell goes off, you lose mana and the cool down timer starts but no damage is done to the target.

[Alanim]

I think I've found the problem, which might be one, or a combination of them


1. When targeting a enemy, then having your mouse over another enemy in mouse look mode, The target your mouse if over gets priority.

2. Dead spots, I took NUMEROUS pictures of various dead spots on many creatures, from shooting through a creatures head, to their arm, etc. but never their chest, but it might also be this way on live.

3. Auto-aim failure, I've actually sat still, and missed a stationary target, because the auto-aim was shooting it under its arm and too far to the left, and I was far enough away, this isn't as big as the first one though, and could be on live, but I'm not 100% sure, I also have pictures of this happening, but not on this computer, i'll post them when I get home.

*EDIT* now that I think about it, the auto-aim failure/some dead spots(but not all) might just be the creature as a much on a 45 degree angle so the arrows fly by its walls(not sure if this is how it works, but it might?)

[Missing_Minds]

I think I've found the problem, which might be one, or a combination of them


1. When targeting a enemy, then having your mouse over another enemy in mouse look mode, The target your mouse if over gets priority.

2. Dead spots, I took NUMEROUS pictures of various dead spots on many creatures, from shooting through a creatures head, to their arm, etc. but never their chest, but it might also be this way on live.

3. Auto-aim failure, I've actually sat still, and missed a stationary target, because the auto-aim was shooting it under its arm and too far to the left, and I was far enough away, this isn't as big as the first one though, and could be on live, but I'm not 100% sure, I also have pictures of this happening, but not on this computer, i'll post them when I get home.

*EDIT* now that I think about it, the auto-aim failure/some dead spots(but not all) might just be the creature as a much on a 45 degree angle so the arrows fly by its walls(not sure if this is how it works, but it might?)

1. Hard vs. soft targetting issue bug. Been in sense they made soft targeting and it screws up often. I'm hoping they have this fixed with U5.

2 and 3. If you could bug report that data in detail, that will help the devs a lot.

edit: per your edit, just put in the report how you were setting up your testing. They can probably figure it out from there as you have a re producible method. You may also wish to note your skill level, style of play, etc.

[Phax]

I think I've found the problem, which might be one, or a combination of them


1. When targeting a enemy, then having your mouse over another enemy in mouse look mode, The target your mouse if over gets priority.

This is exactly the problem. There was a change to range targeting for U5. This caused the "missing arrows" problem (DIFFERENT than point blank range issue). This has been reverted for U5, and targeting will work like it always does on Live.

[Talon_Moonshadow]

I think we're talking about two different issues here, unless you fire 40-50% of your shots at point blank range?

I haven't tried in on Lamania, but if someone wants to use ranged to kill a monster, he will generally be firing most of those shots at clase range....because if he has agro the monster runs toward him...and his only party friendly option is to run in circles arond the monster (at close range) or stand still and shoot it in the face.

Even running away and kiting, usually has the monsters at barely out of melee range. Close enough to quite often get whacked by larger than man-sized monsters.

So if the bug is within 30', I say uhmmmm yeah.....we do.

[Talon_Moonshadow]

Well, he's right. This bug has always existed (or at least for a very long time).

Guess I should keep reading...lol.

Uhmm, they are saying it's a new bug. On Lamania only.

The old bug only causes the first shot to disappear, or another bug that has trouble hitting targets runing perpendicular to you, at a distance. I've never had trouble at close range....after the first shot anyway.

[Ganolyn]

...or another bug that has trouble hitting targets runing perpendicular to you, at a distance.

The lead tracking in this game is just pathetic. Sorry devs, it really needs work.

[Talon_Moonshadow]

This is exactly the problem. There was a change to range targeting for U5. This caused the "missing arrows" problem (DIFFERENT than point blank range issue). This has been reverted for U5, and targeting will work like it always does on Live.

I guess I need to go try ranged on Lamania to make my own decision, but it soulds from this post that we will see the same performance on live that we see now.....before and after U5.

Which is good....thx.

[Missing_Minds]

The lead tracking in this game is just pathetic. Sorry devs, it really needs work.

There is a difference between pathetic lead tracking for players, and having zero lead tracking for players using targeting.

There is none.