You are not facing XXX/spell fizzle

[Psiandron]

Wanted to point out I also get this often with disabling traps on my rogue.
1. Search for and find trap box.
2. Run to box, start disabling.
3. Get 'not facing trap box' error.
4. Wait for disabling animation to finish.
5. Start disabling again. Works 2nd try.

Yup, I get this too.

[jkm]

It does the same thing with the acid blast SLA, but the regular acid blast spell does target foes like it should.

Yeah, there is something borked with all of the Sorc SLAs. Shocking Grasp SLA has about 1/3 of the range of the normal spell.

[TheDearLeader]

Wanted to point out I also get this often with disabling traps on my rogue.
1. Search for and find trap box.
2. Run to box, start disabling.
3. Get 'not facing trap box' error.
4. Wait for disabling animation to finish.
5. Start disabling again. Works 2nd try.

I experience this on my Rogues, as well. Good call.

[Malky]

Yeah, there is something borked with all of the Sorc SLAs. Shocking Grasp SLA has about 1/3 of the range of the normal spell.

Not all of them : melf's SLA works exactly like the melf spell, and acid spray too iirc

[Produktion_Malphunktion]

A fix for this will not make it in U13, but it is under investigation.

[Missing_Minds]

A fix for this will not make it in U13, but it is under investigation.

Major, why does it take Turbine QA/Devs to hunt the forums to find out about bugs still? Or is this still a remnant of the old bug system not working and people not figuring out it wasn't working?

Would it not be wiser to create a bug report section of the forums? It would also have the hind sight aspect that you could see what forumite feel are very frustrating, and hence higher priority due to emotional strain.

[Produktion_Malphunktion]

That is what this forum right here is for.

It is not the 'we didn't know' more like ' bigger pain point that we thought'. As a QA tester irritations after a while just become noise. Be it animation glitches, or facing issues like this. When it is 8-10 hours a day, you work around it, and at some point it becomes WAI for us. Sometimes we need a reality slap be it from the community players, or new testers. Fresh eyes is never a bad thing.

[Malky]

That is what this forum right here is for.

Except it's for lasagna, a forum section dedicaced to live servers bug hunting could be of some use as well imo.

Any word about fireball/acid blast SLAs bad targetting behaviour btw ?

[Missing_Minds]

That is what this forum right here is for.

It is not the 'we didn't know' more like ' bigger pain point that we thought'. As a QA tester irritations after a while just become noise. Be it animation glitches, or facing issues like this. When it is 8-10 hours a day, you work around it, and at some point it becomes WAI for us. Sometimes we need a reality slap be it from the community players, or new testers. Fresh eyes is never a bad thing.

I'm referring to live, Major. We have been dealing with this bug for a heck of a long time. I always figured the bug was caused by either client/server positioning failures (also seen as the ladder hitching, jump warping, etc.) or the fact the mob wants to stand right in the center of your character as witnessed when two AI start to do the square dance, circling each other but can't because they are solid.

Heck, every time I can't attack with the weapon in my hand via keyboard just because the mouse is over the hotbar, a map, or hasn't moved after selecting treasure I want to deck someone at Turbine. Broken combat is not fun.

Or at the very least, grab the dev responcible by the collar, slam his or her face into the scream and shout "BAD DEV! BAD DEV! YOU WILL FIX IT NOW!" However, by this time, I'm betting that developer has left so I'd use a rolled up newspaper or be extremely belligerent to the manager's face. This issue is #1 on my list that ticks me off during game play. On a scale of 1 to 100, it rates right up there at 100+ for irritation/anger. The next issue on my list probably rates oh... 30-35 if that tells you anything. (That is an "Argh... figg'n annoying." Yes, "frigg'n", not any other term.)

If you do not have this bug in your stack, how long has the bug gathering device been broken as I've reported it every mod/update ever since it broke in Mod 3.

[danotmano1998]

Heck, every time I can't attack with the weapon in my hand via keyboard just because the mouse is over the hotbar, a map, or hasn't moved after selecting treasure I want to deck someone at Turbine. Broken combat is not fun.

Or at the very least, grab the dev responcible by the collar, slam his or her face into the scream and shout "BAD DEV! BAD DEV! YOU WILL FIX IT NOW!" However, by this time, I'm betting that developer has left so I'd use a rolled up newspaper or be extremely belligerent to the manager's face.

Wow!
Someone needs to switch to decaf.

Or learn the art of meditation?

[Missing_Minds]

Wow!
Someone needs to switch to decaf.

Or learn the art of meditation?

I seldom drink coffee, and it is better to solve the issue rather than to treat symptoms.

[LightBear]

That is what this forum right here is for.

It is not the 'we didn't know' more like ' bigger pain point that we thought'. As a QA tester irritations after a while just become noise. Be it animation glitches, or facing issues like this. When it is 8-10 hours a day, you work around it, and at some point it becomes WAI for us. Sometimes we need a reality slap be it from the community players, or new testers. Fresh eyes is never a bad thing.

Sadly enough, I know that feeling.

Edit:

It's also why I try to play this game instead of winding up testing it.

[Riggs]

We've received reports about these particular issues before, is there any more information you (or anyone) could provide us with about the circumstances surrounding when these happen?

ie: Were you moving, were the enemies moving, what enemies have you seen this happen to, where has this happened.

Any information you can provide would be great!

Enemies are always moving. The AI that makes most monsters, including oozes and 'mindless' monsters always go for a back attack extremely annoying in this regard.

The amount of spells my casters have failed over the years because of that circling behavior is quite high, and is quite frustrating every single time.

Because while players are always a half second behind the game engine it seems wherever they are - hence the delay in moving or facing response - monsters are always a half second ahead.

Which is why even when you dodge a ray spell from a monster - it hits you even if you are behind a wall and see the spell hit the wall - because when they targeted you they could see you.

Or why if I trip or stun a monster moving towards me - I have to hit the action when they are basically 20 feet away - and time after time, I have tripped or hit or stunned a monster, and all my followup swings MISS because I somehow hit a monster 20 feet away that is now stunned/tripped that is out of my combat range.

Conversely - if you try to hit a monster that is approaching you, and swing when it looks in range - its too late - its already registered as behind you. And if you are casting spells - poof spell fail not facing monster - even when you can SEE it in front of you.

This has ALL been a problem since like mod 4 when a change was made in the engine - because before then you could chase monsters running away - and be hitting them in the back the whole time(and monsters still get to do this to players today) - however after that change, you can be chasing a monster, and your weapon visibly passing through the monster - and get no to hit rolls.

It is great that it is getting some attention now. However this has been an issue for years, and has been pointed out twenty times over - with developer responses - and is still ongoing.

Yes there are a great many issues large and small - but I would think that a change in the game engine that results in everything in the game being a half second ahead or behind of what you can see would have seen greater attention on Turbine's side than it has.

[Thrudh]

but I would think that a change in the game engine that results in everything in the game being a half second ahead or behind of what you can see would have seen greater attention on Turbine's side than it has.

Let's not exaggerate... this doesn't happen ALL the time... EVERYTHING in the game is not a half-second ahead or behind...

Most attacks sync up very well.

[Thrudh]

It happens to me when I'm very very close to a mob.

[GoRinNoSho]

It occurs when an enemy attempts to flank you and due to client/server delay due to natural round trip time, the server identifies the monster as flanking you, your targeted spell gets lost because they are in the back 180 degrees on the server.

That is typical not facing when a mob is close. Solution is 360 degree targeting for players. Monsters already have this. Run in circles around an enemy archer. They will shoot you no problem.

[Ikuryo]

Wanted to point out I also get this often with disabling traps on my rogue.
1. Search for and find trap box.
2. Run to box, start disabling.
3. Get 'not facing trap box' error.
4. Wait for disabling animation to finish.
5. Start disabling again. Works 2nd try.

You can actually skip step 4. When you get the "not facing" error trigger disable again (use item) and the disable timer will start up, without restarting the animation, and continue after you finish the disable animation. The box will then be disabled.

Saves you a couple seconds, and with barbs eager to jump into that trap you need to get it disabled as fast as you can..

[CelestialRat]

Sorry to cross post, but I couldn't resist - this thread applies to my frustration on the live servers and a dev is reading! So please forgive ...


I get this all the time now (since summer?) and it's a game killer.

It's definitely worse when lag is high, but happens even when lag seems only moderate.

I've also noticed that hard targeting no longer sticks - I hard target a foe and bump (not click!) the mouse and focus jumps to a different foe, this is also awful.

It is painful on my casters, but also affects ranged combat and even melee - I'll target a nearby foe and start swinging and catch nothing but air with no rolls in the combat log.

Just to give you an idea how big an issue this is, when RL friends ask me about DDO I tell them to wait until these issues get resolved. It's not just the "not facing" bug - the blink dog foes, rubberbanding off cliffs, and unresponsive hirelings contribute too - but all of these got really bad at around the same time.

I like the fact that you must face your opponent, it adds flavor to the game, but if you can't get the client and server to agree where "facing" is, you should remove that requirement until such time as you can. If a wizard is smart enough to master complex spells, he's smart enough to turn and track his opponent.

[Urist]

Let's not exaggerate... this doesn't happen ALL the time... EVERYTHING in the game is not a half-second ahead or behind...

Most attacks sync up very well.

I'd agree with this assessment, actually. Attacks do sync up quite well, but movement, IME, does not.

When everyone is standing still, all is well in the world. But as soon as someone starts moving, it's like their attacks come from their position half a second into the future (assuming their future is traveling in a straight line). The same being true for landing attacks on a moving target - you have to aim where they will be in a few moments, not where they appear to be now.

[kraaal]

I play from china so my latency is probably higher than most 350-400 ms , and it happens all the time. The mob can be staring me in the face with those dead black eyes of his and ' you are not facing '. I would say I get this error once every 4 casts ,even stopped playing squishy sorcs, switched to wf so I can be more stationery. Serioulsy this bug has made me change my playstyle and yeah the Sorc SLAs are even more screwy.
If you fix this it would make my game experience a gabillion times better.
Also I found lam land even worse than live. I got the error consistently with FOD.