Austerim wrote:

Blue wrote:I tested it in a clean environment. Stand with back to my target and macroed:

1. /face
2. cast

works every single time. Wheres the problem?

You do it fast enough and you get "Target not in view" every single time.

I DID it very fast. I could bet my key hits were not more than 50ms away nearly pressing both keys at the same time.
Well I tested it locally without any delay to the server. But that should not matter as the order of /face and spellcast is still the same even when approaching the server 1 second later.

I can do another test on Uthgard to see whether there are any differences but I can't imagine what could cause the wrong order spellcast => /face

on uth you have a delay about 100ms up to 500ms (subjective feeling)

Magicco wrote:on uth you have a delay about 100ms up to 500ms (subjective feeling)

The delay is not the problem if the order 1. /face 2. cast is still the same. A problem can only arise if 1. cast 2. /face happens

Blue wrote:

Magicco wrote:on uth you have a delay about 100ms up to 500ms (subjective feeling)

The delay is not the problem if the order 1. /face 2. cast is still the same. A problem can only arise if 1. cast 2. /face happens

i will fraps it
of course it cant work if i try to cast without facing if it is not in view
but as already some said it here /face than cast has a delay, but i'll upload later one

Magicco wrote:

Blue wrote:

Magicco wrote:on uth you have a delay about 100ms up to 500ms (subjective feeling)

The delay is not the problem if the order 1. /face 2. cast is still the same. A problem can only arise if 1. cast 2. /face happens

i will fraps it
of course it cant work if i try to cast without facing if it is not in view
but as already some said it here /face than cast has a delay, but i'll upload later one

But /face cant arrive later than cast. Normally. I have no idea how to solve it if /face comes after the spell cast command. This is impossible to fix then and Mythic must have the same problem then. Perhaps not in view means something different.

I dont know how its hapening but its anoying as hell! i had the target in front did /face and he just came to me hited and made me turn 90 degrees i couldnt mezz it with quicast anymore cause i had i not in view . How the hell i had it not in view??? i have to play caster with the fear that all of a sudden i can have not in view ..?
http://imageshack.us/photo/my-images/406/sshot026.jpg/

MotaroReloaded wrote:I dont know how its hapening but its anoying as hell! i had the target in front did /face and he just came to me hited and made me turn 90 degrees i couldnt mezz it with quicast anymore cause i had i not in view . How the hell i had it not in view??? i have to play caster with the fear that all of a sudden i can have not in view ..?
http://imageshack.us/photo/my-images/406/sshot026.jpg/

Never mix up "You cant see your target from here" with "target out of view". Completely different code.

Blue, as I have posted earlier - even pressing the "self-target-macro" and then a heal or something, I get the "not in view" msg, even though I der get "you target Jezzmite" (my cleric) before. (There's 2 "Target-Msgs". on says "you target x" the other says "you target [x]"...I guess the one with [] is more important and the other one is just some local confirmation of the macro...)

and when I target myself actual LoS shouldnt be a problem...instead its some lag-issue (whereever it occurs) that prevents me from casting the spell right after selecting me...

edit: just had the issue again, so I made a screenshot



as a u can see: I "target myself" and then (I tried healing myself) I get the "not in view" msg...after the []-msg appeared healing worked...really not sure, but I believe that is related to the issue reported in this thread...

Well it seems that the first message (white) is only a "useless" information (not useless but you can only see the name of target)
and the second is the real server/client check.

just tested something with a HoT on pend...had the same problem there -> self-target + HoT right afterwards -> "you need a target for that spell" even though it already said I was targetted ;(

Huhu,

I have that nearly every fight on uthgard. Because of that i face + jump, somehow it look faster, and hit the my spell three times.
Then i get like:
Your target Bla
target is out of view
target is out of view
You cast
Resist ( )

I did report it because someone here told that it is just the lag between the client and the server.

Greetz Luydor

The client sends the LOS bits directly with the same packet as the spell cast request. So it can't be a lag problem imo. Its important that I can reproduce it to fix it. Currently I'm unable to. It doesn't wonder me that on live there is the same problem.

I consider both a problem, the 1st thing i reported and the not in view one, they r anoyying as hell: )

Zai, I've seen you on your BD run from my ranger and from my screen it doesnt even look like you stop running and you manage to /face me and quick cast and keep running. So how are you doing that if the /face command is broke? i know what is being talked about, but I've seen it both ways. Where a person couldnt cast because of this and I've seen others (mainly Zai) that made it litterally look like he never stops running when he does the /face + quick cast on me. I dont even gain ground on him chasing behind him its so fast.

RonELuvv wrote:Zai, I've seen you on your BD run from my ranger and from my screen it doesnt even look like you stop running and you manage to /face me and quick cast and keep running. So how are you doing that if the /face command is broke? i know what is being talked about, but I've seen it both ways. Where a person couldnt cast because of this and I've seen others (mainly Zai) that made it litterally look like he never stops running when he does the /face + quick cast on me. I dont even gain ground on him chasing behind him its so fast.

I don't face, and you do catch up.