Just published JAI version 1.8.4.1 including additional fixes to the turn instructions estimation atgorithm:
https://greasyfork.org/en/scripts/9192- ... angle-info

This version contains valuable additions contributed by wlodek76 - thanks!

Olestas wrote:So which one should I use, GH or GF? I keep changing them with each update?

Depends on your expectations.

If you are an average user of the script, then you can use official releases of the script linked by @milkboy in the opening post there:
viewtopic.php?f=819&t=61926&start=50#p735439
The recent version published by the author is 1.8.4, which is available on both GH, and GF.

Version 1.8.4.1 (published by me) is say "developer version" and is currently available only on GF:
https://greasyfork.org/en/scripts/9192- ... angle-info
After acceptance by the author a version 1.8.4.1 may become a next offitial version (1.8.5?), but this is a sole decision of the original author, and this may even never happen.

Decide yourself on which version you want to use.

wlodek76 wrote:Probably @FZ69617 will join to GitHub too, and he clean up a greasyfork version, so we will be able to commit all our changes and fixes in one official place!

I recalled also that I have some old account on GH. I will try to use it for any potential future fixes in order to make JAI development easier.

JAI version published by me on GF has been deleted with replacement URL to the JAI version by @milkboy currently synchronized with GH:
https://greasyfork.org/en/scripts/7887- ... angle-info
All future updates triggered by the current users of my version will be redirected to it - the only requirement is increased version number! There are currently three distinct versions (includeing my one) numbered 1.8.4.1 - which is bad, since it prevents from automatic script updates. I suggest a bit more attention paid to the version numbering in order to avoid unnecessary problems with script updates.

milkboy wrote:Oh, and if we'd really want to utilize GitHub, I could set up a separate "development" branch that could then be used for testing new stuff, before merging into master. The dev branch could then be used by brave testers who don't mind occasional problems or something. Master would then be considered "release quality"... just some thoughts.

Good idea! This would likely also help in solving the versions numbering issue.

Olestas wrote:Hmm, actually this was long time ago, just forgot to tell:
Shows as EXIT, but waze gives KEEP.
https://www.waze.com/editor/?env=row&lo ... ,153859370

Indeed, Livemap shows "keep right" for this route:
However, Waze client app gives an "exit right" instruction here:
Exactly what JAI suggests in this particular case.

Arnoniem wrote:So, any chance of getting a uturn colour?

The feature is already developed and is waiting for merge into the official GH repo by @milkboy.

We'll likely use a violet color for the U-turn instructions in a default colors scheme:
http://i62.tinypic.com/2zjieeq.png

If you are interested you may try a JAI development version that supports it.

Arnoniem wrote:just noticed a 168.6 angle gets purple as well.
But on the angles I've done tests with, (without checking the first decimal), a 169 angle still gave a turn left. A 170 degr was a uturn prompt.

The u-turn angle in use currently is 168.24 with a "gray zone" ±0.2 degrees.
These values are based on my multiple map experiments performed last week.

The recent series of these experiments is still on the map and all examples matches the current values:
http://i61.tinypic.com/256dxs9.png
The anomalies - which were a basis for a gray (in fact yellow ) zone approximation - has been observed so far just for the two unselected examples in the above picture.

Could you post the permalinks to examples you mention that violates current rules?
Together we can find better approximation of a u-turn and/or a gray zone angles.

Arnoniem wrote:Did you actually navigate and get a uturn prompt at 168.5 degr?

Sure, see the route going through this segment with a u-turn prompt at 168.47 degrees:
http://i62.tinypic.com/2mwz9c1.png

voludu2 wrote:I found a case where JAI does not reach the same conclusion on BC as the mobile app or route checker:

https://www.waze.com/editor/?env=usa&lo ... 8,75487051

JAI does not catch on to this.

Thanks for finding this.

You may try another JAI development version that correctly handles this case.

The changes in the routing instruction estimation algorithm still requires further testing (all implemented conditions are rather my guessing than knowledge ), but all the cases tested so far looks promising.

bz2012 wrote:After trying the latest development version, I found wild rapid 'scrolling' when attempting to click and drag to move the view.

I'm not aware of any changes in JAI that could cause such a strange behaviour.
I personally experienced "rapid scrolling" even without any addon enabled, thus maybe it just coincidentally happened to you after installing JAI.

bz2012 wrote:So, turned it off and turned regular JAI on, F5 to load, and all works normally now so, there may be a conflict of some kind.

Did you try F5 having only JAI development version enabled?
If the problem persists please describe closer your environment (the browser version, what other addons are used etc.).
I'm currently using latest JAI development version and it works without any problems in Chrome and Firefox with over 20 other WME addons enabled.