v5.56/v5.60 Official Bugs Thread

[Sarganto]

"It seems like using a geological team on a body which has a civilian mine on them has no effect. They are just sitting there for years and years and nothing happens."
Did it say no survey in the mineral section? if not then it was already surveyed, and there was no need to resurvey it. Does the ship sit there with SP needed constantly?

I am talking about geological survey teams, not ships.

[TheDeadlyShoe]

most Sol-system civilian mines are on asteroids and comets.   Asteroids take forever to team-survey, presumably to stop them from being used as infinite training grounds and sources of infinite minerals. There are after all hundreds of asteroids in Sol alone so the training/mineral potential is extreme.

[Sarganto]

most Sol-system civilian mines are on asteroids and comets.   Asteroids take forever to team-survey, presumably to stop them from being used as infinite training grounds and sources of infinite minerals. There are after all hundreds of asteroids in Sol alone so the training/mineral potential is extreme.

Nope, right now the team is on a moon with civilian mines and I didn't have a single tick for umh maybe 2 or 3 years?

[Thiosk]

I no longer survey asteroids because of this.  Its not a bug, per se, but i don't think its working as intended, exactly.

With the recent capping of geo surveyer training at 60% (might be my fault) I'm not so concerned about the training up of people these days.  Let the chunks survey a bit faster for gods sake.

[Nathan_]

Nope, right now the team is on a moon with civilian mines and I didn't have a single tick for umh maybe 2 or 3 years?

It goes by mass, more massive asteroids can be surveyed fairly quickly, and, say, phobos and deimos will take forever.

[ExChairman]

In Population Menu, the button for refresh All, doesn't refresh colonies, but by transferring the capital to a new planet does update the colony list...

[North Pole]

In Population Menu, the button for refresh All, doesn't refresh colonies, but by transferring the capital to a new planet does update the colony list. . .

You can reselect civ name in top-left corner to update population menu

[Sarganto]

I no longer survey asteroids because of this.  Its not a bug, per se, but i don't think its working as intended, exactly.

With the recent capping of geo surveyer training at 60% (might be my fault) I'm not so concerned about the training up of people these days.  Let the chunks survey a bit faster for gods sake.

As I said, the problem does not only exist with asteroids. Every other body has been surveyed by the team at least within a year.
But on asteroids and moons with civilian mines, nothing is happening.

[Marthnn]

As I said, the problem does not only exist with asteroids. Every other body has been surveyed by the team at least within a year.
But on asteroids and moons with civilian mines, nothing is happening.

Check the mass of successfully surveyed bodies, and the mass of attempted surveyed bodies. How do they compare? Does the team you're using have a good rating (150+) with 5 members total?

Moons can be very small, even smaller than asteroids. If they already have civ mines, that is probably not the case, so maybe you're just unlucky. Still, you give us not much info to work with.

[Thiosk]

Error in UpdateGameEvents
Error 3167 was generated by DAO.Database
Record is deleted

The previous error was something of the nature of "invalid bookmark"

What happened is that I was launching a complex array of missiles at an oncoming enemy-- I targeded my last salvo, and then set fleet speed to maximum to pull away from the enemy.

It started throwing the invalid bookmark error, then record is deleted after I set the whole fleet to cease fire.

Now it appears the missiles aren't moving.

This is version 5.6 in an unmodified game.

Edit:
John's suggestion works flawlessly.  I repacked the database immediately on error occurrence and fixed it.

I had cycled back to an earlier save before beginning that encounter, and even the situation REPLICATED ITSELF.  Which I found interesting.  I have a backup of that file immediately on reccurrence, before repacking.

[Steve Walmsley (OP)]

I no longer survey asteroids because of this.  Its not a bug, per se, but i don't think its working as intended, exactly.

With the recent capping of geo surveyer training at 60% (might be my fault) I'm not so concerned about the training up of people these days.  Let the chunks survey a bit faster for gods sake.

When a survey team finishes a cycle (which is really the game checking a random number each 5-day to see if it is lower than their rating), the code carries out a mineral generation check on the body they are surveying. If it finds something better than what is currently available, the team will report it. Asteroids generally have a much lower chance than planets to have any minerals at all so often those checks result in nothing. So it isn't that asteroids take longer for each check, it is that those checks are unlikely to find anything and you only hear about a check that found something.

Mineral generation is based on system body size, with larger bodies having both a higher chance of minerals being present and larger deposits while smaller bodies have better accessibility.

Steve

[sloanjh]

Error in UpdateGameEvents
Error 3167 was generated by DAO.Database
Record is deleted

The previous error was something of the nature of "invalid bookmark"

What happened is that I was launching a complex array of missiles at an oncoming enemy-- I targeded my last salvo, and then set fleet speed to maximum to pull away from the enemy.

It started throwing the invalid bookmark error, then record is deleted after I set the whole fleet to cease fire.

Now it appears the missiles aren't moving.

This is version 5.6 in an unmodified game.

You might try compressing the database (I think there's a menu option to do so in Aurora.)  My recollection is that this can fix some invalid bookmark errors - not sure if it will work on the cascading deleted record error, but what have you got to lose?  (Assuming you back up the DB before compressing, of course )

John

[Shemar]

When a survey team finishes a cycle (which is really the game checking a random number each 5-day to see if it is lower than their rating), the code carries out a mineral generation check on the body they are surveying. If it finds something better than what is currently available, the team will report it. Asteroids generally have a much lower chance than planets to have any minerals at all so often those checks result in nothing. So it isn't that asteroids take longer for each check, it is that those checks are unlikely to find anything and you only hear about a check that found something.

Mineral generation is based on system body size, with larger bodies having both a higher chance of minerals being present and larger deposits while smaller bodies have better accessibility.

Steve

The problem with that is that a team can be stuck on an asteroid for years and years. Wouldn't it be better if they have a higher chance of finding anything but also a higher chance of completing the survey? That way they could still be finding the same total amounts (on average) but in a little less time.

[Zed 6]

I would agree with a higher chance of completing the survey. Years and years and years of waiting for a report is a little excessive. If the survey team finds something or not, I just wish they would complete the survey.

[sloanjh]

I would agree with a higher chance of completing the survey. Years and years and years of waiting for a report is a little excessive. If the survey team finds something or not, I just wish they would complete the survey.

Thirded.

John