Author Topic: v2.5.1 Bugs Thread  (Read 171529 times)

0 Members and 2 Guests are viewing this topic.

Offline Mark Yanning

  • Silver Supporter
  • Sub-Lieutenant
  • *****
  • M
  • Posts: 109
  • Thanked: 18 times
  • 2025 Supporter 2025 Supporter : Support the forums in 2025
    Silver Supporter Silver Supporter :
Re: v2.5.1 Bugs Thread
« Reply #480 on: August 31, 2025, 06:06:04 AM »
Thanks Steve, it may be some file corrupted indeed. I checked the DB files, and they are identical to the original version. I switched many PCs playing this scenario, it could be some save on Pc with "period" separator and not with "comma". Now I'm sure is on comma. I'll take a look at it, or just wait the new release to restart an epic game session. Thanks again for have created this gem, and for keeping it update o/
« Last Edit: August 31, 2025, 06:17:07 AM by Mark Yanning »
 
The following users thanked this post: Steve Walmsley

Offline Steve Walmsley (OP)

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 12265
  • Thanked: 24515 times
  • 2025 Supporter 2025 Supporter : Support the forums in 2025
    Gold Supporter Gold Supporter :
    Above & Beyond Supporter Above & Beyond Supporter :
Re: v2.5.1 Bugs Thread
« Reply #481 on: August 31, 2025, 06:16:02 AM »
Hello.
I have a problem: every time I click on an increment to advance time, I receive an error message, which occurs twice. Time still advances so it doesn't make the game unplayable but it's quite annoying, especially in battle. The precise message is the following: 2.5.1 Function #58: the sequence contains no elements. I specify that this message started appearing after I transferred a ship to an NPR. I tried several things, including destroying the ship I had transferred but that didn't change anything. The previous saves also contain the bug so this doesn't seem to be a solution, unless we can go back more than two saves? If anyone has a solution that would be very helpful, thank you in advance.

As a general rule, its not a good idea to transfer ships to an NPR because they sometimes can struggle to classify them and therefore don't know how to use them.

In this case, the error is in the function SensorActivationDecision, which happens many times on every increment.  The fact you only have the error twice per increment and it started when you transferred the ship, strongly suggests that was the problem.

This function is called for Fleets, not ships. When you deleted the ship, did you just delete it in the database? That won't work, as it wouldn't delete the parent fleet, or anything else connected to it.
 

Offline Louella

  • Sub-Lieutenant
  • ******
  • L
  • Posts: 120
  • Thanked: 180 times
Re: v2.5.1 Bugs Thread
« Reply #482 on: August 31, 2025, 10:13:37 AM »

Lately, I have an error for function #117, which seems to occur at the end of each construction cycle.

Hello, were you able to fix these errors? I have the same error for function #117  :(

sorry for the late reply, but no, I've not found a way to correct this error. It doesn't seem to be causing too much of an issue though, so I'm just ignoring it for now.
 

Offline nakorkren

  • Commander
  • *********
  • n
  • Posts: 349
  • Thanked: 306 times
  • Gold Supporter Gold Supporter :
    2025 Supporter 2025 Supporter : Support the forums in 2025
Re: v2.5.1 Bugs Thread
« Reply #483 on: August 31, 2025, 10:26:53 AM »
"Disassemble All" button allows you to disassemble components and recover tech points even if you don't have an active research lab on that colony. "Disassemble" button functions correctly i.e. requires you to have active lab there.