No update
Could be that they have more then enough cases going on since the Event started. ?♂️
I truly doubt that they will make any update for it, I had this issue long time. Remember it took them 20 hours to get this buggy boxes out. This new UL is just bad, it is.
???
???
???
[MEDIA=imgur]a/0rIlGnp[/MEDIA]
That’s that then…
2 Likes
It seems only some avatars are affected by this otherwise no one would hunt argonauts at all. Maybe 3/4 years ago we had a problem were some people would have a break (avatar would just freeze for like 30 seconds) like 2 or 3 times per hour. I remember it very well because it went for like six months without fix.
In the end it was like our packets took the longest route possible until reach their servers. It was really annoying because 30 seconds with some mobs interaction can be a lot and you end up dyeing.
Hope this can be fixed quick and the people affected this time don’t have to wait six months for a solution.
1 Like
With hopes of helping someone, I will repost this here also:
Unfortunately, I think I had a similar problem, and it can still happen occasionally. What seemed to help me was verifying the local data. In the client loader, go to Tools, select Folders, and click Verify Local Data. Let me know if this helps you as well.
1 Like
Thanks for sharing. ?
It is like this allways with such bugs, as long as they do not cost MA Peds they are extremly slow in solving it, if we, the user of their service, profit of such a Bug they will instantly correct it or even stop the game until it is corrected. The problem with this Bug, at least in the Argo caves is that the coordinates of the mob where its hitbox is is not updated as the coordinates of the image of this mob.
Here the support case I wrote with the description how to still be able to kill the affected mob. In short, shoot at the place where the mob was standing when you first shot at it and you will be able to deliver damage and kill him. To loot you have to click at the image and not the place you where able to hit the mob. So for MA it would be the simple task of verify that the coordinates of the hitbox are the same as the coordinates of the place the mob image is drawn. But this task is too difficult for their developpers.
In the Argonaut Cave a problem can occure that the position of the mob and where you have to shoot to hit him are not the same.
This bug happens not every time you go into the cave.
The bug is like this:
First you shoot at the bugged mob, as normal the mob takes damage and he runs to you and start to hit you. When you now shoot at that mob he takes no damage but still hits you and you take damage. The only way to shoot at the image of the mob and deliver damage is when you get killed and go back.
But instead of that you can kill the mob by shooting at the place the mob was standing when you made the first shot. So shooting at the position the mob was delivers damage and kills him. After that to loot the mob you can klick at the image again. So it seams that very rarely the hitbox is not updated when the mob moves.
1 Like
Many thanks for the workaround, mate. 
And indeed, there is maybe 100 “minor bugs” here and there, that MA prefers to ignore, and which slowly but surely decreasing the confidence in this game of the players…
One year ago was the “New UI”, and several forum threads open by MA to collect bugs and reactions.
They are still “compiling” them…
1 Like
It has cost and that will always have trippling effect.
Not enabling smooth cycling is just fucking stupid business plan.
I am still on EU detox and having visited the forums check up watch up, i am not impressed, same old loopie loop.
Hope the info you shared helps out someone, (y)
Altho it would be about time MA starting to pull their fucking weight.
1 Like
This argo lock issue happened to me on LA42 several times - it was notably weird that it was a single argonaut that i found several times. It happened once on HM too just before the last patch. Fragile code surprises me it hasn’t had a catastrophic crash every login!
I found it easier to hunt them near outpost and just turret the bugged ones :), can be really anoying
It seams to me they are two different bugs. When it happens in Argo Cave the Weapon can still be used and the Mob can be hit, not where you see it but where it was standing when you first shot at it. In the first picture you see that the crosshair indicates, red color, that I’m aiming at the target. In the text window you see the messages that he still tries to hit me:
[IMG width=“1738px” height=“1080px”]https://www.planetcalypsoforum.com/forum/index.php?media/argo-cave-bug-pic-1.344507/full
Then in the second Image you see that I have hit the “thin air” at the place the Argo was when I first shot at it and that he took damage and died:
[IMG width=“1734px” height=“1080px”]https://www.planetcalypsoforum.com/forum/index.php?media/argo-cave-bug-pic2.344506/full
@Ludvig|MindArk Are you still following this thread?
It just happened twice in the fields.
I found that entering my Sleip then exiting it fixed the issue of the “lost” hitbox.
Of course, can’t work in the cave.
Nice glad to hear its better for some people, were you still able to kill the mob after exit sleip?
I wasn’t at the time.
Sometimes other people were able to kill them sometimes not, never tried to turret them.
Confirmed Daily Argo cave, Fort Troy Elite spot, Twin Peaks young spot and (for love of god cant remember the name of outpost) Notus perhaps? longu/Argo spot near Athena Space port.
Seem to be issue on all servers anyway, so it is prolly Argonaut spesific issue more then server.
Wasn’t very enjoyable experience to get that codex done lol.
Yes, I was able to finish it.
It was on the Elite spot of Troy.
Indeed only Argos seem to let their hitbox behing them. 
Still an issue, sent support case. Generic response recieved. Like a big ole F off and take it.