I See Dead Pixels! (AF Related)

[Eileah]

<p><span style="font-size: medium;"><span style="font-family: 'comic sans ms', sans-serif;">If you don't use the autofollow mechanic this probably won't relate to you.</span></span></p><p><span style="font-size: medium;"><span style="font-family: 'comic sans ms', sans-serif;">For quite a while now there has been a problem with an AF toon hanging in spots in zones, it was mentioned in the fix af thread but not much beyond that.</span></span></p><p><span style="font-size: medium;"><span style="font-family: 'comic sans ms', sans-serif;">The problem is that the AF toon will stop moving, AF does not break, the AF toon is still hooked up to the lead toon but it just sits there. If you move the lead toon around in an arc the AF toon will turn to face the lead. The only way to get past the dead spot is to break AF, move the toon manually to the lead and reattach the AF to the lead.</span></span></p><p><span style="font-size: medium;"><span style="font-family: 'comic sans ms', sans-serif;">Quite a hassle considering how often it happens every day.</span></span></p><p><span style="font-size: medium;"><span style="font-family: 'comic sans ms', sans-serif;">Over the last month or so I have been taking screenshots of the loc whenever ther AF toon hits a dead spot and I have a list of them to share in hopes of getting this fixed.</span></span></p><p>Zone/Loc:</p><p><p>OoA -1.16, 1.35, -1.25</p><p>OoA 0.16, 1.97, -1.02</p><p>Guk: HoTF -1.17, -1.50, -1.06</p><p>Guk: HoTF -2.09, -1.33, -0.30</p><p>Vek: ST -2.07, -3.61, -1.05</p><p>Vek: ST -4.07, -2.00, -1.05</p><p>Atrebe 1.13, 0.22, 1.43</p><p>Sebilis -0.27, 0.00, -1.43</p><p>Sebilis -0.51, 0.00, -2.43</p><p>Seafury Hideout -1.56, 0.33, 3.47</p><p>Rescue the diplomat: -0.96, -0.29, 2.27</p><p>The Coallition Factory 0.68, -0.18, 2.99</p><p>The Dismal Den 1.23, -0.29, 1.84</p><p>The Defector 1.71, 0.33, 1.77</p><p>DFC 0.51, 1.00, -2.10</p><p>EL 1.75, -1.70, 0.13</p><p>Befallen: CoA -0.97, -0.39, 1.58</p><p>Befallen: CoA -1.62, -0.25, -1.58</p><p>Befallen: HotF 2.93, 0.00, 1.90</p><p>Befallen: HotF 2.30, 0.00, -0.65</p><p>Befallen: HotF -2.34, 0.00, -0.68</p><p>Befallen: HotF 0.92, 0.00, 3.35</p><p>Befallen: NA -2.06, 0.28, 0.90</p><p>Befallen: NA -2.39, 0.28, -0.05</p><p>Befallen: NA -2.45, 0.28, -038</p><p>Befallen: NA -2.24, 0.28, -0.11</p><p>Befallen: NA 1.98, 0.00, -1.24</p><p>Befallen: NA -2.32, 0.28, -0.36</p><p>Befallen: NA 1.61, 0.00, -1.36</p><p>DF 2.14, -0.01, -1.22</p><p>DF -1.97, -0.01, 2.13</p><p>CoA (Crypt) -0.02, -0.35, 2.55</p><p>CoA (Crypt) 0.49, -0.35, 4.45</p><p>CoA (Crypt) -1.72, -0.29, -0.21</p><p>Nek Castle 2.11, -0.96, 0.26</p><p>Nek Castle -2.08, -0.86, 0.96</p><p>Kaladim 1.16, -1.98, -0.84</p><div></div></p>

[ashen1973]

<p>the actual 'dead spots' are all 0, 0, 0</p><p>If you 2-box, place 2 chars on exactly the same spot and you wil notice their locations can differ by 1 or 2 points in each co-ordinate.</p><p>This has been reported and discussed for ages, it has also been reported as fixed before, but still doesn't seem to be :/</p>

[Bratface]

<p><span style="font-family: tahoma, arial, helvetica, sans-serif;"><span style="font-size: medium;">I have boxed since launch and I never had this problem until a month or so ago so it is new to me.</span></span></p><p><span style="font-family: tahoma, arial, helvetica, sans-serif;"><span style="font-size: medium;">Do you have links to the previous posts about it and this fix?</span></span></p>

[TSR-DanielH]

<p>I actually haven't noticed that myself when 2-boxing with an AF character.  I'll see if I can verify it on my end, though.</p><p>That said, the best way to report this issue is to use the /bug command.  That actually sends the information over to the QA team so it can be verified and then corrected.  It's certainly possible that a dev will see this post, but the /bug command is probably the best option.</p>

[Bratface]

<p><span style="font-family: tahoma, arial, helvetica, sans-serif;"><span style="font-size: medium;">Well I sent a few /bugs in when it first started happening, but they are so prevalent that I decided to collect them all and post them. </span></span></p><p><span style="font-family: tahoma, arial, helvetica, sans-serif;"><span style="font-size: medium;">I hope you do check it out, it's not random, it happens every time without fail.</span></span></p>

[TSR-DanielH]

<p><cite>Bratface wrote:</cite></p><blockquote><p><span style="font-family: tahoma,arial,helvetica,sans-serif;"><span style="font-size: medium;">Well I sent a few /bugs in when it first started happening, but they are so prevalent that I decided to collect them all and post them. </span></span></p><p><span style="font-family: tahoma,arial,helvetica,sans-serif;"><span style="font-size: medium;">I hope you do check it out, it's not random, it happens every time without fail.</span></span></p></blockquote><p>Based on the waypoints you posted, it sounds like an equation used for AF becomes invalid when both the X and Y coordinates are equal to zero.  It sounds like something that would be pretty easy to fix if you can find it.  I'll certainly pass along that information but /bug is still the better option in most cases.</p><p>Thank you for compiling so much information about this issue.  If you do submit another bug report then you might want to link this thread in the comments.</p>

[Bratface]

<p><span style="font-family: tahoma, arial, helvetica, sans-serif;"><span style="font-size: medium;">Thank you Daniel, I will be sure to send a link to this thread in any /bug I send about it.</span></span></p><p><span style="font-family: tahoma, arial, helvetica, sans-serif;"><span style="font-size: medium;">I do have a question about that though, should I send in more /bugs about these locations or just new ones I find?</span></span></p>

[TSR-DanielH]

<p>I would only submit additional /bug reports if you have significant new information to add.  Based on the information you posted, I'm betting that almost any zone will produce the same effect at 0,0.  It shouldn't be necessary to submit a new bug report for each zone you see it in.</p>