Auto-mapping broken

[Former user]

Upon jumping a new connection the tracked character disappears from the system they were in, but the dialogue to choose a sig doesn't come up and the new system isn't added to the map

[David Hofmann]

Having the same problem. Log out back in and no change. Also notice the automap icon is missing now.

[Josh Glassmaker]

Going to need a little more to re-create the issue and fix. I have tested the automapper feature with the new ESI tracking without issues.

[David Hofmann]

Daimian, Let me know what you need and I'll provided it. I've included the image of the missing tracker icon

[Sardit]

since reloading the browser from the last update i've experienced no autmapping at all. Upon jumping through a wormhole there is no prompt for a sig id, no creation of a new signature either. The character jumping simply vanishes off the chainmap. After manually editing the wormhole into the chain it tracks just fine. The issue seems to be in sig creation or "mapping" a wh jump into the chain. Even with sigid's all setup to go it will not track a character making an unknown jump.

[David Hofmann]

Found the missing >>> was due to character not being selected. Now have that back, but still not tracking as I go through wormholes.

For those missing it, click on your name, then select your character under the tracking section.

[Josh Glassmaker]

@david_hoffman Are you still missing the automapper icon - you need to make sure that is enabled (orange)

@Sardit You will need to follow what David said - you now have to select which character you want to track after adding them.

[David Hofmann]

So it wasn't tracking. But the second worm hole I jump through after selecting the character it start tracking suddenly.

[Sardit]

I've followed those steps and have tripwire seen updating one signature jumping through a wormhole. However currently tripwire is very slow to load, it throws me 502 errors on the signin screens, seems to log me off. Every once in a while it will show the red desynch errors or just throw out blank pages that show nothing. Reloading those results in errors like {"proccessTime":"1.0722"} Which to me looks like timeouts from the ESI.

Invalid reponse from ESI during token authentication. {"error":"invalid_request","error_description":"Authorization code not found"}{"proccessTime":"0.5230"}

After repeated log ins i just managed to get a tripwire screen. in the time that it took me to scan down the first wormhole tripwire has allready become unresponsive and shows me the red. "Problem Syncing with server" error.

[Amra Ni]

Ok, got issue, no toons showing, yesterday, no issue. I connect today and nothing. I saw a new option and clicked on it : https://puu.sh/tJElV/455fdb60c9.png (next to the research option) but still doesn't work. To show this option I had to go under character, double click on it (to put it in silver then orange) to be able to see this new option called : follow me in game.

[Nekomancer]

On the first day of the tracking update, everything worked fine. But since yesterday I can't get my character tracked: I have the char and the autotracking selected but tripwire doesn't detect where I am neither what ship I'm flying. I cleared browser cache, cookies and everything. Reset the ESI token. Logged in tripwire using every option. Nothing worked.

UPDATE: A message appeared about tripwire being rebooted and that I should log out. After that I attempted to log in, but it didn't let me. Some time after that I managed to log in and my system/ship is being tracked since then

[Josh Glassmaker]

So Tripwire had some session server issues which seems to be fixed now but CCP were also having ESI server issues lately also. Right now things should be on track and working on both ends so lets see how things go going forward.

[Josh Glassmaker]

I did some basic testing last night with the automapper, forgot I didn't uncomment the pod check code so made that change last night.

After initial testing I am considering implementing a check to make sure if the ESI API call for your location hasn't returned successfully within a small time frame to ignore a system change as it could have skipped a system you had been in while it was having connection troubles with the EVE API - this would only be for the automapper.

[Ahmet Kabasakal]

I have same issue with @Nekomancer except nothing worked for me so far.

[Ashy]

Issue 3 months old. If more issues then please raise a new ticket and quote Issue #203