Description
2 votesFound a Tech signature around a K-class planet during FTL travel. Performed an all-stop command, and then commanded helm to navagate to the system using the sensor target. (as it was just outside of the 15 LY limit for the "Scan Target System" command to work. I commanded helm to navagate directly to the outermost Dwarf planet of the system.) Once we got there, I executed an "explore current system" command. Helm navagted directly to the sun and Sensors Officer performed a short range scan, but then failed to select a new target. I then canceled all open commands, and tried again, but it's still stuck and not executing properly. I had toggled on the "System Overview" option on sensors, which appears to also replace the medium range sensor display on the Holoviewer... so this may or may not have some impact on the execution of the "explore current system" command.
Screenshot
Auto-Captured
Game Context
Auto-Captured- Galaxy Coords -24942, 663, 279
- Local Coords 16931377428, 63821783487, -5092159134
- Player Deck A
- Player Role Admiral
- Player Location X=491 Y=75 Z=165
- Player Rotation P=0 Y=165 R=0
- CPU AMD Ryzen 7 7700X 8-Core Processor
- GPU NVIDIA GeForce RTX 4070
- Operating System Windows
Details
- Reporter Don T.
- Assignee Dan Govier
- Status Confirmed
- Severity Gameplay Impacting
- Close Reason None
- Game Mode Single Player
- Vessel Type Magellan Class
- Build Version 0.227.0.21
- Raised 2026-05-17 18:49 UTC
- Updated 2026-05-18 18:42 UTC
Comments
4 total-
AyJayAreDii 2026-05-17 19:45 UTCStatus: New → Confirmed
Assignee: QA Team → Dan Govier -
2026-05-17 19:46 UTCRan though the exact same events given and crew scanned the outer most planet, then the star and then got stuck trying to select a new target.
-
2026-05-17 19:54 UTCAt a closer look at the Current Sensor order that flickers on and off. It looks like it is targeting the local 0,0,0 which is the current location that is already scanned.
-
2026-05-17 22:47 UTCYaY!! We found it!!
Sign in to post a comment.