[2.0.15] Map shows red dots where nothing exists

[Linsanga]

The map has a red dot on Nauvis and a red dot on Gleba, as though a turret or enemy is there, but when zooming in and visiting the location, nothing is there. I don't know where or when they appeared, but I added a map tag arrow to the left of each red dot to help spot them if you load the save file.

Nauvis.png (20.14 KiB) Viewed 944 times

Gleba.png (22.19 KiB) Viewed 944 times

[LCStark]

From the map view screenshots it looks to me like deconstruction orders on rocks or other neutral entities, are you sure it's not what that is?

[The_Sane]

I've also experienced this and started ignoring it after repeatedly noticing them. I think they usually appear when fighting enemies, most commonly on Gleba. Gleba has a lot of extra enemies spawning during fights, and there is often an orphaned red dot left on the map. Unsure if its left behind from a killed enemy, or perhaps when a new enemy tried to spawn it failed in some way(?) but still added a marker on the map.


edit: one of several I can see when looking around Gleba.

20241110171123_1.jpg (368.1 KiB) Viewed 887 times

20241110171125_1.jpg (830.01 KiB) Viewed 887 times

[thuejk]

Yeah, I have seen this too. There is no enemy or deconstruction request at the eternal red dot.

[BlueTemplar]

I've also experienced this and started ignoring it after repeatedly noticing them. I think they usually appear when fighting enemies, most commonly on Gleba. Gleba has a lot of extra enemies spawning during fights, and there is often an orphaned red dot left on the map. Unsure if its left behind from a killed enemy, or perhaps when a new enemy tried to spawn it failed in some way(?) but still added a marker on the map.

Same thing. (2.0.16 and once before that, both on Gleba.)

Save where I'm standing a few m to the north of the dot, just after a recent combat nearby :

[Loewchen]

117582

[LCStark]

I've just had first occurrence of this in 2.0.20.

11-20-2024, 19-28-50.png (6.04 KiB) Viewed 669 times

11-20-2024, 19-12-13.png (718.73 KiB) Viewed 669 times

There was a single red dot on the radar a bit above the spot where there are a few small craters right on the edge of my Spidertron's light. This was the direction from where moment's ago I was attacked by a Big Stomper. Apparently, my radar scanned this chunk at some point and picked it up:

11-20-2024, 19-13-16.png (3.69 KiB) Viewed 669 times

To me it looked like the blip was one of Stomper's legs and for some reason it wasn't cleared from the map.


I loaded an autosave and went there before the attack, killed the Stomper, but I didn't manage to get the red dot stuck again. Letting the stomper attack on its own and going there after the attack once again didn't reproduce the bug. Whatever it is, reloading the game prevented it from happening again.


I loaded again a save after the attack first happened and the dot is still there. But, weirdly, it disappears when my Spidertron gets really close to it:





I've attached this save, which loads you at the start of this video. Just switch to remote-view on Gleba.

[LCStark]

And another interesting thing happened. I've attacked the stomper from a different direction to see if maybe it was depending on being far away from the player-controller vehicle, when this happened:





As the stomper was chasing me, its legs were leaving a trail of red dots on the map. They persisted until I approached them.

[BlueTemplar]

So, it's some kind of leggy nonsense ?

[Brambor]

Segmenty nonsense. Happens on Vulcanus too.

[Sworn]

One more for the list: viewtopic.php?p=646637#p646637

[Rseding91]

As far as I can tell, everything here is working correctly. Simply put: the map stops being updated when you the player or a radar is not nearby to update it. When you engage with these enemies you typically run away quickly while fighting them to keep out of reach. But by doing that, you stop being near them enough to update the map and so it leaves the red enemy indicator from the last time you were close enough.

The same thing can be seen with biters on Nauvis when fighting large groups of them and moving away from their nests at speed.

Unless someone knows of a way to make it happen with an enemy that's within 3 chunks of the player - or a red spot that when visited doesn't then go away (this indicates an engine issue that it failed to flag the chunk as changed since you last saw it).

[aka13]

As far as I can tell, everything here is working correctly. Simply put: the map stops being updated when you the player or a radar is not nearby to update it. When you engage with these enemies you typically run away quickly while fighting them to keep out of reach. But by doing that, you stop being near them enough to update the map and so it leaves the red enemy indicator from the last time you were close enough.

The same thing can be seen with biters on Nauvis when fighting large groups of them and moving away from their nests at speed.

Unless someone knows of a way to make it happen with an enemy that's within 3 chunks of the player.

I had a couple of f10s uploaded where there were red phantom enemy dots on the map, if that helps

[Rseding91]

I had a couple of f10s uploaded where there were red phantom enemy dots on the map, if that helps

Did they go away when scanned by a radar?

[BlueTemplar]

It's different here, in the situation that you describe, this happens to enemy radar dots getting outside of radar range, and they disappear immediately once you get them into radar range again.

In this case they never started out of radar range to start with, and stayed inside all of that time (at least in my case, I'm fairly confident that spot has at least 2 overlapping radars and only one of them might have gotten destroyed, not to mention that I was probably close enough myself).

[Rseding91]

It's different here, in the situation that you describe, this happens to enemy radar dots getting outside of radar range, and they disappear immediately once you get them into radar range again.

In this case they never started out of radar range to start with, and stayed inside all of that time (at least in my case, I'm fairly confident that spot has at least 2 overlapping radars and only one of them might have gotten destroyed, not to mention that I was probably close enough myself).

So, you probably don't know how the player radar range works (I don't know why anyone except someone looking at the code would). Every 32 ticks a 2 chunk radius around the player is updated (chunk you're on + 2 in all directions). All changes done to the chunks for the next 32 ticks will not be reflected on the map if the player moves away from it before the 32 tick re-scan time is up.

So what happens is: the spider is near the chunk border and your player re-scans, then 32 ticks of movement you moved past the chunk border and the next re-scan doesn't update that chunk the spider may or may not still be in.

The time for a scanned chunk to fully fade to dark is 600 ticks, so it still "looks" like it's being scanned but it's not.

[BlueTemplar]

Maybe I'm missing something, but there should be no «fading to dark» here ??
(Red dot still right under me.)

red_dots_and_radars.png (340.73 KiB) Viewed 266 times

The «radar» I was thinking about was actually either the cargo landing pad or the roboport and they were certainly not destroyed. (Turrets removed for clarity.)

[Rseding91]

In that case, do you know how I can reproduce that happening?

[BlueTemplar]

No, sorry

[LCStark]

As far as I can tell, everything here is working correctly. Simply put: the map stops being updated when you the player or a radar is not nearby to update it. When you engage with these enemies you typically run away quickly while fighting them to keep out of reach. But by doing that, you stop being near them enough to update the map and so it leaves the red enemy indicator from the last time you were close enough.

The same thing can be seen with biters on Nauvis when fighting large groups of them and moving away from their nests at speed.

Unless someone knows of a way to make it happen with an enemy that's within 3 chunks of the player - or a red spot that when visited doesn't then go away (this indicates an engine issue that it failed to flag the chunk as changed since you last saw it).

Check the video in my post: viewtopic.php?p=642791#p642791. I don't think it's the expected situation you're talking of. The red dots show up well within the scanning range and they don't disappear until the spidertron approaches them to just a few tiles away. Like at 0:27 you can see that there's a red dot right next to the spidertron, and it doesn't disappear until it moves right past it. At 0:33 you can see me stopping with the red dot just outside of personal roboport range (30x30 for this spider) and after several seconds in radar range the dot doesn't disappear from the map.

I've done that with my save from viewtopic.php?p=642749#p642749, I'll try it again tomorrow on current experimental version to see if it's still reproducible in it.