Distance lines stuck bug

[Bruno Guimaraes]

Well, meanwhile...

[Gergely Csernak]

I am not sure that what you see on the screen is a quick distance tool result. That should normally disappear on next click. On the other hand you can create normal distance elements between the same points to look like this. Try eg.:

distance2 A A

from command line.

I am not sure how they are added to the screen, but at least they can be removed from screen by a right mouse click. Can you test it?

[Marcelo Barretto]

Using the command works, if you type at least the first point - eg.: .distance <fix> (mouse click somewhere)

If you try .distance, but instead of typing try to click on two points with the mouse, the problem occurs as soon as you click on the first point/TAG.

Drag'n drop from the Heading field on the TAG has the same issue. This somehow only affects the tools when the mouse is used

Edited November 6, 2021 at 06:54 PM by Marcelo Barretto

[Martijn Rammeloo]

I did not see Gergely's post in time 😞

I had the bug tonight. I was trying to connect a distance line between waypoint ARTIP and KLM0427. Instead, the line snapped to the SPL VOR.

Martijn

 

[Thimo Koolen]

Yes, it's possible to right click and remove the line. That still does not solve the bug of being unable to draw distance lines correctly. 

[Andrea Mazzoni]

Luckly I'm not alone with this. I had experience this issues few times. Luckly I know which are the headings for my airports. I will try in case in the future the solution which Gergely has published previously.

[Matteo Massini]

Happened to me as well on Milano and Malta... and to a lot of other APPs and CTRs over here in VATITA. It also makes the heading tool useless so I need to give vectors without any precise reference, very annoying. An ES restart always fixed it all temporarily, but it's something that needs to get sorted out. Speaking of Gergerly's solution post, I tried left and right mouse buttons, creating another distance line by dot command and praying, nothing worked but a restart.

Matteo Massini, VATITA

S3 - P1 - S1/S2 ATC Instructor - DevTeam (GNG)

Edited November 10, 2021 at 11:15 AM by Matteo Massini
Missing Signature

[Marcelo Barretto]

Had the bug again yesterday during World Flight, which made the approach on São Paulo a bit of a nightmare.

Have the logs if it helps figure out the issue somehow.

[Matisse VanWezer]

For those using topsky, you could draw a heading line by clicking the radar target of an aircraft.

[Jonas Kuster]

This issue is becoming more regular and urgent repairs are needed! It basically renders all measuring/heading tools unusable.

Wasn't able to prove it in a reproducable way yet, but I've observed this issue to be present with high reliability when another controller is using r29. I've clearly advised controllers in my vACC to refrain from using this version.

[Thimo Koolen]

Happens with R26 as well.

Yesterday during an event it happened twice in a short period of time. After that I just gave up on the tool, which was a pain.

I don't know why it happens much more regularly now (it happens generally every session), but I most certainly know it needs an urgent bug fix.

[Jonas Kuster]

13 minutes ago, Thimo Koolen said:

Happens with R26 as well.

Are you sure nobody in your proximity used r29? I'm not using R29 either. But I have indicators pointing towards any user with r29 also affecting controllers in the vicinity. You may use ".inf" to retreive the version information of nearby fellow controllers.

[Mateusz Zymla]

Cause R29 still hangs around... It should be taken down from the website and clearly communicated not to use it unless solved!