[kovarex] [2.0.16] CTRL-A (spidertron remote) gets confused and loses surface selection

[doktorstick]

I'm attaching two saves. The first, jump to Gleba remote view, hit CTRL-A and you can control the spidertron. The second, jump to Gleba remote view, hit CTRL-A and you cannot control the spidertron.

I observed this by CTRL-A sending the spider out to bring democracy to the pentapods with a series of waypoint moves. I jumped around a few other planets and came back to Gleba and attempted to CTRL-A to continue its path, but it wasn't selecting the spidertron anymore. I did not use the remote nor Nauvis's spidertrons between these two controller attempts. Temporally, the operations were pretty close together as the save infos will show.

Edit: It's possible this was an errant left-click on the terrain and it deselected the spidertron from the remote. I did this accidentally just now when controlling the Nauvis spidertrons.

[doktorstick]

I didn't misclick, as I had thought. In this case, I had done the same thing: sent the spidertron on a path and then went to Fulgora and was doing some building. I came back to Gleba to see where the spidertron was, hit CTRL-A and it didn't select it. In fact, it's giving the cursor of two spidertrons when there's only one on Gleba.

11-09-2024, 17-24-14.png (25.32 KiB) Viewed 118 times

[FactorioPony]

Posted my report separately since I went more in-depth on other spidertron remote problems, but here's a link to my report which includes reproduction for the 'fake' spidertrons selected aspect:
viewtopic.php?f=7&t=121288