Jump to content

"Planetoid detected" when it should not be


qenadvnapdi
  • Branch: Live Branch Version: Windows Pending

I got a notification of a "planetoid detected".  A new planetoid now appears in the list of discovered planetoids.  However, the starmap does not show the planetoid and there is no reason it should have been detected yet.  When I click to view that planetoid I see only a small section of that planetoid deep underground.  This occurred while launching a rover for the first time to another planetoid that I did legitimately discover.  I suspect that somehow revealing the surface of that new planetoid for the first time resulted in spillover, erroneously revealing part of another planetoid at the same time.


Steps to Reproduce

Launch a rocket to the orbit of a recently discovered planetoid and deploy a rover.  Doing so revealed the surface of the planetoid as expected, but also revealed a portion of another planetoid unexpectedly.




User Feedback


I have the similar error few days ago when I arrived the orbit of a asteroid (Vegetista is that target) and black hole ate my game. I didn't catch the log because it was just before I want to go to bed. (Sleep time schedule). The next day I loaded the game and a new asteroid found on my starmap which I didn't reveal any hex around it. (See below Dampolin on the left). Mine is an old map generated before Bug and Shine. Not sure what it is related so I didn't report it.

image.thumb.png.7f4d67f0686490ca1391888972e5b1b3.png

I still not visit Dampolin and now I can see it glowing on my starmap. (like a star blinking). When overseeing the asteroid, I can see the surface of it. Not sure if this helps but sav attached.

拯救海文星.sav

Share this comment


Link to comment
Share on other sites

Attaching a save file where this occurs.  Upon loading the file there is a notification that "Moistora" has been discovered.  The starmap does not show Moistora.  Going to that planetoid by clicking it in the planetoid list reveals only a small section of the planetoid deep underground.

The Darkest Hovel.sav

Share this comment


Link to comment
Share on other sites

Something similar just happened to me.

I'm on cycle 1132, and I've been flying around a 20-range rocket for a while, equipped with a cartographic module, and I had discovered practically everything on the star map within a 10 tile range, in every direction.  I had not discovered the water world yet.

Today I load my game, and upon loading I receive a "new planetoid" notification.

It is the water world, which appeared in a tile I had already discovered.  All the tiles directly around it are showing as discovered.

At the same time, however, a bunch of tile I already had discovered have become "???", in the direction of the new planetoid.

f0947b13902f7d9ca2980b94dc14e003.png

When clicking to oversee the planetoid, I also get only a tiny portion on the bottom-left of its map:

d12d44e4eba0e71fe4615400bda4852e.png

 

I tried re-loading the game, and it still happens everyt time I load it.

I also tried reloading the last 3 auto-saves (every 10 cycles), and it now does the same every time.

I can't attach my save game as it's larger than the allowed attachment size limit.

Share this comment


Link to comment
Share on other sites

From my limited testing in colonies with less than 5 discovered planetoids, it seems:

  • The bug manifests when a rocket launches and enters orbit. It must also be the first rocket built.
  • It will only persist when a save is made while the ship is in space.  Therefore loading a save after the moment a ship enters orbit will have the bug.
  • The release of a rover has no bearing on the bug's manifestation. 
  • The lower left corner of the rogue discovery will not be revealed until a save is made, auto or user initiated, and then loaded.  This is confirmed by debugging to reveal all planetoids before the rocket enters orbit after launch.
  • If a ship completes its journey by landing on a platform, subsequent saves will not have the rogue planetoid bug.  This would indicate the bug is most likely caused by the map location allocated for the rocket interior of the first rocket built.

I have had this bug on three consecutive cluster colonies.  Please fix.

 

Share this comment


Link to comment
Share on other sites

On 9/3/2022 at 3:03 AM, ravalox said:
  • The bug manifests when a rocket launches and enters orbit. It must also be the first rocket built.
  • If a ship completes its journey by landing on a platform, subsequent saves will not have the rogue planetoid bug.  This would indicate the bug is most likely caused by the map location allocated for the rocket interior of the first rocket built.

The lone rocket I have in flight is my 2nd rocket built, not my 1st, and I encountered this bug.

Both of my first two rockets use solo spacefarer nosecones on CO2 engines.

Also, the lower left corner of the new planetoid (the water planet Aquila, btw) is visible as soon as it's "detected."

Edited by zivvel

Share this comment


Link to comment
Share on other sites

I've reproduced this again after the Hot Shots release. If you load up the attached save file, the water planetoid should get detected immediately after load, despite no one being nearby.

 

Lunar Space Hut.sav

Share this comment


Link to comment
Share on other sites

This issue causes the discovery of the water planet (bottom-left) and the disorder of planet list (also, shortcuts).

The issue is not immediately visible to the live play. The discovery of water planet is only notified after loading saves consisting of problematic rocket launches.

The issue seem occurring randomly. I usually fixed the issue by loading previous saves and launching rockets again.

This time this trick did not work. I tried different steam rocket configuration, eg. adding/removing/replacing/rebuilding modules, change height, ... etc.

It seems that the issue is related to rovers because removal of rover modules did not cause the reveal of water planet.

However, I had launched rockets with rovers on other planet before and no issue occurred.

I also experimented launching CO2 rocket with/without rovers but the issue did not occur.

Above is my experience.

Edited by aaron2022

Share this comment


Link to comment
Share on other sites



Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
  • Create New...