Page 1 of 1

[1.2.0.0] beta - problem when zooming in, only one ship is selectable

Posted: Sun Jan 14, 2024 2:35 pm
by InfoBit
After updating to version 1.2.0.0, I have a bug when zooming in to the system level. At this point, there seems to be a bugged ship that is automatically selected when I click on any ship or base station in the same system. The ship information appears in the corner of the screen (see screenshot at the top left), and when I try to click any other entity on that system, that ship is automatically selected. At the bottom, you can see a screenshot of the problem

This savefile has the issue. https://www.dropbox.com/scl/fo/q1mpmw1j ... up2w2&dl=0

You can see the problem when you zoom into the system "Ruunadan system" (the capital system of the Ikkuros from the Ruunadan Collective). You can see that the ship named "Formidable Skirmish" is the only selected entity, no matter where you click. If you zoom in enough into my home system, you can see that the same problem occurs.

This happened before with another ship, but when I destroyed it, the problem shifted to this ship, the "Formidable Skirmish."

I just remembered that I am playing with a few mods on this playthrough. There might be a chance they are the culprit. However, the problem started after I updated it to 1.2.0.0. Before that, version 1.1.8.1 was ok.

My mods are:
XL https://steamcommunity.com/sharedfiles/ ... 2916197192
Distant Worlds Universe Music https://steamcommunity.com/sharedfiles/ ... 2933129408
Anex Realistic System Names https://steamcommunity.com/sharedfiles/ ... 2941773051
Realistic Empire Names https://steamcommunity.com/sharedfiles/ ... 2941511272
Screenshot 2024-01-13 202646.png
Screenshot 2024-01-13 202646.png (3.09 MiB) Viewed 391 times

Re: [1.2.0.0] beta - problem when zooming in, only one ship is selectable

Posted: Tue Jan 16, 2024 8:13 pm
by MaximKI
Thanks for the report! We'll investigate.

Re: [1.2.0.0] beta - problem when zooming in, only one ship is selectable

Posted: Sat Jan 20, 2024 11:42 am
by InfoBit
Thanks! This got fixed for 1.2.0.2