Dancer Archive

---

Panthu wrote:

Bug Name: "Too far away"

Description: When someone tries to /watch a Dancer or /listen to a Musician, they incorrectly get the system message that they are too far away to watch or listen to that performer. This is the normal system message that is given when a patron actually is too far away to watch/listen to a performer, but the bug is that it is being triggered incorrectly: the patron is not too far away, they can be right beside the Ent.

Break down:

1. Patron does a /watch

2. Patron receives system message that they have started watching the Dancer

3. Patron receives system message that they are too far away to be entertained by the Dancer

Notes:

The bug seems to be on the performer and not on the patron or location, because patrons can /watch or /listen to other performers in the same cantina.

Switching to playing music from dancing or vice versa doesn't help, the bug sticks to the Ent.

Can persist through zone changes and travel as well as long log outs.

You used to be able to "work around" the bug by moving your av around a few steps, but this stopped working on the first CU server (and every one after that and I think that there were reports that it stopped working on the Live servers as well during CU testing, but before the CU pub).

*hugs Eshie* I think this is the same old beast that caused our dances to display wrong on the high travel styles and gets both Musicians and Dancers messed up sometimes with the start/stop commands and traveling. No clue on what triggered it though, this one popped up before they changed our base dances.

I think it was about the time of the "snappy movement" patch though, so maybe that's a tip for them? Which pub was that?

Edit: Oops, reposting in the right thread. Ok no, I'm just going to leave this here, lol. *flashes her "Glowies are allowed to be a little nutty" card*

Message Edited by Panthu on 05-28-2005 02:41 AM

Message Edited by Panthu on 05-28-2005 02:45 AM

---

What made our traveling bases display wrongly was the server to client syncing of avatar location in the world. The removal of that went to live in 14.1. This popped up just prior to that and I'm pretty sure it was about the time of "snappy movement".But yeah..it got worse on CU test.I really wish we could at least find a way to make it consistently repeatable. There's a condition somewhere that we're not seeing. Tonight we were messing with it and I was running a macro to /watch Scip and sometimes got the error after he had stopped dancing for maybe as much as6seconds.

I had severe problems with this last night when hunting with a group of guildmates. I had tagged along to provide inspiration buffs (and because we were going to be doing space soon), but only 2 of the 6 could watch me, and they had to move around alot to find the right angle and distance, which only worked for them. Also, it doesn't always apply to the performer alone, as I couldn't watch the other entertainer in the Dathomir Outpost. I noticed another bug at the same time, and I think they are unrelated, but I'm gonna be doing some testing on it.

---

Panthu wrote:

Inoticed in the other thread V asked about cloning and other people started mentioning the new bug with cloning stations (also says you are too far away basically)... so maybe the server is thinking you're back where you last cloned? Or died?

though it must be happening even with out a death, so I'd guess the dieing just made it more likely to pop up...

---

The two chars we were on the other night are test chars on Ahazi. That vers of Esh has never broke a sweat, much less cloned or died..has never even stored cloned data (she was watching). While Scip was repeatedly diseased & db'dby Odi there several months ago (to get Live numbers on bf heal xp), that has been probably 3 months past now. I think what they are looking at is a "line of sight" thing and I think that it might be on the /watcher's side.

"Line of sight?" That might be a "relative" term?

I was trying to "Catch" the too far away bug. (I've only had it happen once and posted the details in V's thread)

I set up my two chars running AFK macros in my private house. A small square Naboo. Char 1 Dancing. Char 2 Watching. Char 2 was sitting in the back corner of the larger room on the right hand side of the house. Char 1 was dancing in the corner directly opposite in the same room. About 3 meters away. Char 2 was able to target and use "watch" from the radial menu. I then changed dance to Tumble 2, knowing she'd eventually dance out of the room or outside of the house (and eventually down the beach or into the lake out front.)

Char 2 The Watcher had Char 1 The Dancer, targeted and was running two macros -- an anti-boot macro (/mood: none, etc.) andthe stop/start watch macro. Char 1 The Dancer was running only a dance macro, a very simple one to cut out extraneous info. (/flo 2, /pause 20) That made her do the backwalkovers constantly but with lag and the occasional lapse into the base dance and the drift. There was no /stopd or /startd in the macro. (Starting and stopping again resynchs the characters and being able to watch or listen always works again once I do that. Not sure why it doesn't for others?) Inspiration buff and experience gains were functioning normally.

I let that setuprun fora fewhours. When I came back, Char 1 The Dancer had drifted out of the large room, across the hall and had danced herself into the back corner of the smaller left hand side room. Char 2 The Watcher still had target lock on Char 1 The Dancer.Char 2was still getting Inspiration buff. Char 1 was still getting xp gains for having 1 watcher. I scrolled back in the log. No "too far away" messages. So even with the /startwatch and /stopwatch macro running, Char 1 never got the "too far away" bug. Even though "technically" Char 2 The Dancer was now out of "line of sight" behind two walls and in another room.

However... What I saw... On the computer running Char1 The Dancer, both chars were still in the same room, where we had started. But on computer 2, running Char 2 The Watcher, I sawChar 1dancing in the opposite room of the house, to where she had drifted.

I had Char 2 The Watcher stand up, did NOT untarget Char 1 The Dancer, and went into the next room, where it appearedChar 1was at from the view on computer 2. As soon as Char2 entered the other room, she got the "too far away" message. I looked at computer 1/Char 1. She appeared to still be in the first room in the corner where she had originally started dancing. Char 2 tried to retarget Char 1 and restart the /watch. "Too far "away."

Char 2 ran back into the first room. Sat down in the corner. Targeted Char 1. Was able to radial /watch first try. No "too far away" bug.

"Line of sight?"

---

Mystyrys wrote:

"Line of sight?"

---

Players can obviously "see" (& target) the cloner terminal when they're getting the "too far away" error in that scenario as well. What the server "thinks" the av is in position to see and what we see on our monitors may differ.

When Scip & I were last testing;his avnever appeared to be more than 3m from my av on either of our monitors, he wasperforming a non-moving base dance, there were no objects between them, he periodically stopped and restarted, I periodically stood and sat my av. Yet, in 2 hours' time, I successfully /watched him 7 times, usingmacro: /watch scip; pause 20; /stopw; pause 10; /ui action toolbarSlotxx (occasionally I changed the times for the pauses).

I have found that the "too far away" bug applies more to a place/setting than to an individual performer. We have a Jam Session every Friday night. Occassionally we perform in player facilities, be it cantina, theater, home turned into a club. On the evenings when we perform in a player facility everyone in the audience received the "too far away" message no matter who they tried to watch or listen.

We moved to Theed cantina with the same group of performers and same audience and everyone was able to watch and/or listen.

I have encountered the "too far away" bug in the Coronet cantina as well. We moved to Theed and did not have an issue.

I don't see where cloning would add to this as most NPC cloners give the "too far way" message as well as do some player cloning facilities.

for the record, the devs mentioned that the "too far away" bug is a LOS problem that's affecting a lot of things (including the "city info" tab in city halls), and they're looking into fixing it soon.

---

Pappi wrote:
for the record, the devs mentioned that the "too far away" bug is a LOS problem that's affecting a lot of things (including the "city info" tab in city halls), and they're looking into fixing it soon.

---

Had this happen to me in the Dant MO cantina. But it never has happened to me in the Cnet cantina.

Any update on this? Imaji placed a new cantina on Lok and we decorated it heavily. Now it is impossible for people to watch or listen. We tried the trick of having them stand just outside the exterior door and doing /listen which works for about 10 seconds. It has become rediculous, I can hardly find anywhere that people can listen to me anymore. Isn't it bad enough without the few people who still want to hear us being unable to listen?

---

LyteFoot wrote:
Any update on this?

---

---

Esharra wrote:

---

LyteFoot wrote:
Any update on this?

---

Only that it is being worked on as a top priority. It appears this is a result of a Line of Sight problem that is affecting many game aspects. In addition to how it affects us, players are reporting the same problem when trying to access clone terminals, city hall terminals, vendors and harvesters.

---

Last night I was on my bike (mounted) on the side of a hill, and when I opened the radial menu on it, the dismount and store options were disabled because I was "too far away from it". That was just a one time thing, though, and I don't know if there was any other factor that might have contributed to it.

Shi'ann Dinova
Hot Pink Twi'lek of Mystery