Post reply

Warning: this topic has not been posted in for at least 120 days.
Unless you're sure you want to reply, please consider starting a new topic.

Note: this post will not display until it's been approved by a moderator.

Name:
Email:
Subject:
Message icon:

shortcuts: hit alt+s to submit/post or alt+p to preview

Please read the rules before you post!


Topic Summary

Posted by: Zook
« on: December 23, 2021, 12:13:27 PM »

For others with the same problem: I got rid of these issue several times now.

- Download DB Browser for SQLite
- Save Aurora game, exit Aurora
- Make a backup of your Aurora DB!
- Start DB Browser, load DB
- Find table FCT_Increment. If you're stuck with 2-hour turns, you'll see a lot of 7200 second increments at the end of the table. Choose one that is several increments before the last and copy the timestamp (e.g. "2135824235.0").
- In the SQL command tab enter (with the timestamp from the step above):

SELECT * FROM FCT_FleetHistory
WHERE GameTime > 2135824235.0;

- Run it (click the Play button). You'll get the last couple of actions of all fleets. That should tell you which ones are misbehaving by jumping back and forth.
- Find these fleets in FCT_Fleet. There's a field called Xcor, the x-coordinate of the fleet. Change it by adding a large number. For example, if it reads "-1628493155.80953", change it to "-991628493155.80953". That should teleport the fleet many billions of km away from the jump point.
- Save changes. Done.

That fleet will spend several weeks or months moving back to the jump point. By that time, the reason for going back and forth (most likely an enemy fleet) might have disappeared. If not, rinse and repeat.

Disclaimer: Resist the urge to muck around with too many things in the DB. If you screw up your database, it's your problem. But then you made a backup, didn't you?
Posted by: Zook
« on: December 19, 2021, 03:01:22 PM »

I'm slowly getting the hang of it, but I'm not making this a hobby any time soon...

My biggest problem is a fleet of five jump point defenders who have been doing the old back-and-forth for a looong time now. They have no orders, no fuel, there seem to be no standing orders for the NPRs I could edit and I don't want to delete them. I teleported them to a faraway place in-system, but like a zombie they always come back. I just switched off their sensors, hoping they'd get blown to bits. No such luck. I'll teleport them to an even further-away place now.

How can teleport them to another system?
Posted by: nuclearslurpee
« on: December 19, 2021, 09:53:36 AM »

Ideally you want to try and dig into the fleet in other tables to try and figure out what it is trying to do, and then tune your "fix" to help them accomplish that. A common one is a fleet trying to head home to refuel, but the route home runs through an enemy-infested system and the AI is too stupid to not jump in anyways, and too stupid to once in make a run for it instead of jumping back out. In that case you may be able to help by shifting that fleet towards the jump point they actually need to go through.

Hopefully the rework to jump shock in v2 will help correct this behavior.
Posted by: Zook
« on: December 19, 2021, 01:41:05 AM »

Have to bother you one more time....

I'm definitely getting somewhere. After adding "1" to the first digit of the four suspects' x-coordinates, I got 30 hours of gameplay in three increments (what unit is this, anyway? Kilometers?). Then I was back to 2 hours, because presumably, they were back at the JP.

Problem is, two of the four fleets are troop transports with proper orders to go to some planet (that I've never heard of). The two others are Jump Point defence fleets. The buggers don't even have orders, they just jump for the fun of it.

edit: it appears the transports are causing the problem.

Given that deleting a fleet seems fraught with peril (operational groups, what have you), what's my best course of action? How can I move them e.g. to their home planet?
Posted by: nuclearslurpee
« on: December 18, 2021, 06:32:28 PM »

Quote from: Zook on December 18, 2021, 04:33:37 PM
43   23333   JP3: Tomten (JG): Standard Transit   2121525110.0
43   23333   JP2: System #53 (JG): Standard Transit   2121532310.0
43   23333   JP3: Tomten (JG): Standard Transit   2121539510.0
43   23333   JP2: System #53 (JG): Standard Transit   2121546710.0
43   23333   JP3: Tomten (JG): Standard Transit   2121553910.0
43   23333   JP2: System #53 (JG): Standard Transit   2121561110.0
43   23333   JP3: Tomten (JG): Standard Transit   2121568310.0
43   23333   JP2: System #53 (JG): Standard Transit   2121575510.0
[repeated many more times]

43   24435   JP4: Allentown (JG): Standard Transit   2122129910.0
43   24435   JP1: Albuquerque (JG): Standard Transit   2122137110.0
43   24435   JP4: Allentown (JG): Standard Transit   2122151510.0
43   24435   JP1: Albuquerque (JG): Standard Transit   2122165910.0
43   24435   JP4: Allentown (JG): Standard Transit   2122180310.0
43   24435   JP1: Albuquerque (JG): Standard Transit   2122194710.0
43   24435   JP4: Allentown (JG): Standard Transit   2122209110.0
[This one is pretty bad and #1 on my to-hit list]

43   25359   JP1: Albuquerque (JG): Standard Transit   2121525110.0
43   25359   JP3: Annapolis (JG): Standard Transit   2121532310.0
43   25359   JP1: Albuquerque (JG): Standard Transit   2121539510.0
43   25359   JP3: Annapolis (JG): Standard Transit   2121546710.0
43   25359   JP1: Albuquerque (JG): Standard Transit   2121553910.0
43   25359   JP3: Annapolis (JG): Standard Transit   2121561110.0
[very, very often]

Any one of these is the most probable candidate, possibly even all three which would be quite a cluster... probably the next thing is to try and pull apart the fleet orders in the relevant table and figure out where each one is going, then try to move it away from the JP so it cannot just insta-transit and might complete its orders.

Quote
While we're at it: is it enough to change the current x-coordinate to move a fleet?

Yes.
Posted by: Zook
« on: December 18, 2021, 04:33:37 PM »

Sigh... it unfixed itself. Back to 2-hour turns.

Now, not being one to give up easily and following Migi's advice, I found the following fleet history entries from recent turns that look decidedly fishy:

43   23300   Asteroid #70: Move to Location   2121525110.0
43   23300   Asteroid #70: Move to Location   2121532310.0
43   23300   Asteroid #70: Move to Location   2121539510.0
[repeated many more times]

43   23333   JP3: Tomten (JG): Standard Transit   2121525110.0
43   23333   JP2: System #53 (JG): Standard Transit   2121532310.0
43   23333   JP3: Tomten (JG): Standard Transit   2121539510.0
43   23333   JP2: System #53 (JG): Standard Transit   2121546710.0
43   23333   JP3: Tomten (JG): Standard Transit   2121553910.0
43   23333   JP2: System #53 (JG): Standard Transit   2121561110.0
43   23333   JP3: Tomten (JG): Standard Transit   2121568310.0
43   23333   JP2: System #53 (JG): Standard Transit   2121575510.0
[repeated many more times]

43   26979   Amity-A I: Move to Location   2122237910.0
43   26979   Amity-A I: Move to Location   2122245110.0
43   26979   Amity-A I: Move to Location   2122252310.0

43   26996   Acute-A VI: Move to Location   2122396310.0
43   26999   Acute-A VI: Move to Location   2122396310.0
43   27002   Acute-A VI: Move to Location   2122396310.0
[repeated many more times]

43   23883   Armendáriz Resources Limited: Refuel from Colony   2122072310.0
43   23883   Armendáriz Resources Limited: Refuel from Colony   2122086710.0
43   23883   Armendáriz Resources Limited: Refuel from Colony   2122101110.0
[repeated many more times]

43   24176   Asteroid #284: Refuel from Colony   2121532310.0
43   24176   Asteroid #284: Refuel from Colony   2121546710.0
43   24176   Asteroid #284: Refuel from Colony   2121561110.0
43   24176   Asteroid #284: Refuel from Colony   2121575510.0
43   24176   Asteroid #284: Refuel from Colony   2121589910.0
[repeated many more times]

43   24222   Fantomen-A II - Moon 1: Refuel from Colony   2122201910.0
43   24222   Fantomen-A II - Moon 1: Refuel from Colony   2122216310.0
43   24222   Fantomen-A II - Moon 1: Refuel from Colony   2122230710.0
43   24222   Fantomen-A II - Moon 1: Refuel from Colony   2122245110.0
[repeated many more times]

43   24435   JP4: Allentown (JG): Standard Transit   2122129910.0
43   24435   JP1: Albuquerque (JG): Standard Transit   2122137110.0
43   24435   JP4: Allentown (JG): Standard Transit   2122151510.0
43   24435   JP1: Albuquerque (JG): Standard Transit   2122165910.0
43   24435   JP4: Allentown (JG): Standard Transit   2122180310.0
43   24435   JP1: Albuquerque (JG): Standard Transit   2122194710.0
43   24435   JP4: Allentown (JG): Standard Transit   2122209110.0
[This one is pretty bad and #1 on my to-hit list]

43   25107   Semarang Prime: Refuel and Resupply from Colony   2121964310.0
43   25107   Semarang Prime: Refuel and Resupply from Colony   2122396310.0
[repeated many more times]

43   25359   JP1: Albuquerque (JG): Standard Transit   2121525110.0
43   25359   JP3: Annapolis (JG): Standard Transit   2121532310.0
43   25359   JP1: Albuquerque (JG): Standard Transit   2121539510.0
43   25359   JP3: Annapolis (JG): Standard Transit   2121546710.0
43   25359   JP1: Albuquerque (JG): Standard Transit   2121553910.0
43   25359   JP3: Annapolis (JG): Standard Transit   2121561110.0
[very, very often]

43   26298   Ag Mines Corporation: Refuel from Colony   2121820310.0
43   26298   Ag Mines Corporation: Refuel from Colony   2121834710.0
43   26298   Ag Mines Corporation: Refuel from Colony   2121849110.0
[repeated many more times]

43   27662   Annaj Prime: Refuel and Resupply from Colony   2121532310.0
43   27662   Annaj Prime: Refuel and Resupply from Colony   2121546710.0
43   27662   Annaj Prime: Refuel and Resupply from Colony   2121561110.0

These are SQL-pulled from the last 383 increments, all 2-hour (7200 sec) turns. Now, which fleet is the culprit? I notice that e.g. the last bunch (Annaj Prime: Refuel and Resupply from Colony) does not have 7200 sec between entries, but why is the fleet repeating this order? Does any of this look legitimate?

I could delete or move all fleets that seem suspicious but I'd prefer minimally invasive surgery on the DB. Some advice would be welcome!

While we're at it: is it enough to change the current x-coordinate to move a fleet?
Posted by: Migi
« on: December 17, 2021, 09:28:31 PM »

Quote
But I'm still wondering: how can you tell from a look at the log or ship or move order table if a fleet is jumping back and forth?
You could look in the fleet history?
Posted by: Zook
« on: December 17, 2021, 05:51:57 PM »

Praise the Lord! It fixed itself - somebody must have blown the bugger to bits.

Thanks, anyway.

Oh, and here's something from another thread that might help in this kind of situation (I haven't checked this out):

"I think i have found the problem - at least the cause of it: after my last battle quite a few unlucky crewmembers where left behind in their lifepods.  those must have triggered an interupt - because as soon as the lifepods expired, time increments went back up."

But I'm still wondering: how can you tell from a look at the log or ship or move order table if a fleet is jumping back and forth?
Posted by: dsedrez
« on: December 17, 2021, 10:24:38 AM »

Quote from: Zook on December 17, 2021, 09:09:49 AM
Further research indicates that the move orders are not incomprehensible, but there's 3000 of them. And a fleet jumping back and forth would not leave an entry in the log.

I have a suggestion, take another copy of the DB, and in the FCT_Races table switch the NPR race to user-controlled (from 1 to 0 I think). That will allow you to examine what's happening first-hand, and try some solutions.
I never tried giving orders to the NPR as user-controlled, then switching it back to NPR, so I don't know if that would work, but at least you might be able to figure out what the exact problem is.


Posted by: Zook
« on: December 17, 2021, 09:09:49 AM »

Further research indicates that the move orders are not incomprehensible, but there's 3000 of them. And a fleet jumping back and forth would not leave an entry in the log.
Posted by: Zook
« on: December 17, 2021, 08:14:37 AM »

Thanks, but no
- I tested my tinkering on a copy of the game DB. The 2-hour breaks happen in an unmodified game.
- Many construction cycles have passed now.
- Some of these same ships tried to join OpGroups when Neil Armstrong was still wearing diapers.
Posted by: Blogaugis
« on: December 17, 2021, 05:35:30 AM »

Quote from: Zook on December 16, 2021, 11:27:56 PM
I'm in the precisely same situation, i.e. stuck in 2-hour increments. I've used DB Browser (for the first time) on a copy of the DB and found a suspicious entry at about the time the trouble began: "Destination of FAC Hunter Squadron - Jump 011 cannot be found. Please issue new orders". I deleted that fleet and its ships and the result was that I'm now stuck on 6-minute increments.

I'm not about to give up, but I have no idea how to identify a fleet trying to jump or anything like that. The move orders are incomprehensible. Could anybody walk me through this, or give me a hint how to proceed?

These are the last log entries. Some of these messages already appeared before the 2-hour problem began.
-----------------------------------------
GE Gwanggaeto the Great 002 is unable to carry out its primary standing order: Refuel from Colony or Hub (All)
GE Gwanggaeto the Great 003 is unable to carry out its primary standing order: Refuel from Colony or Hub (All)
GE Gwanggaeto the Great 004 is unable to carry out its primary standing order: Refuel from Colony or Hub (All)
Stabilisation Squadron 003 is unable to carry out its primary standing order: Build Jump Gate at Nearest Jump Point
Stabilisation Squadron 004 is unable to carry out its primary standing order: Build Jump Gate at Nearest Jump Point
Stabilisation Squadron 003 is unable to carry out its primary standing order: Build Jump Gate at Nearest Jump Point
Stabilisation Squadron 004 is unable to carry out its primary standing order: Build Jump Gate at Nearest Jump Point
JD Saint Augusta 001 is unable to carry out its primary standing order: Join Operational Group
JD Saint Augusta 002 is unable to carry out its primary standing order: Join Operational Group
GE Thufir Hawat 002 is unable to carry out its primary standing order: Refuel from Colony or Hub (All)
DDG Iri IV 039 is unable to carry out its primary standing order: Join Operational Group
DDG Iri IV 040 is unable to carry out its primary standing order: Join Operational Group
FT Viroconium 013 is unable to carry out its primary standing order: Join Operational Group
DDG Iri IV 041 is unable to carry out its primary standing order: Join Operational Group
DDG Iri IV 042 is unable to carry out its primary standing order: Join Operational Group
DDG Iri IV 043 is unable to carry out its primary standing order: Join Operational Group
DDG Iri IV 044 is unable to carry out its primary standing order: Join Operational Group
DDG Iri IV 045 is unable to carry out its primary standing order: Join Operational Group
DDG Iri IV 046 is unable to carry out its primary standing order: Join Operational Group
DDG Iri IV 047 is unable to carry out its primary standing order: Join Operational Group
DDG Iri IV 048 is unable to carry out its primary standing order: Join Operational Group
DDG Iri IV 049 is unable to carry out its primary standing order: Join Operational Group
DDG Iri IV 050 is unable to carry out its primary standing order: Join Operational Group
SS Modena 001 is unable to carry out its primary standing order: Refuel from Colony or Hub (All)
SS Modena 002 is unable to carry out its primary standing order: Refuel from Colony or Hub (All)
Stabilisation Squadron 001 is unable to carry out its primary standing order: Build Jump Gate at Nearest Jump Point
SS Modena 003 is unable to carry out its primary standing order: Refuel from Colony or Hub (All)
Stabilisation Squadron 002 is unable to carry out its primary standing order: Build Jump Gate at Nearest Jump Point
DDG Exodus II 003 is unable to carry out its primary standing order: Join Operational Group
DDG Exodus II 004 is unable to carry out its primary standing order: Join Operational Group
Stabilisation Squadron 003 is unable to carry out its primary standing order: Build Jump Gate at Nearest Jump Point
Stabilisation Squadron 004 is unable to carry out its primary standing order: Build Jump Gate at Nearest Jump Point
GE Patecatl 001 is unable to carry out its primary standing order: Refuel from Colony or Hub (All)
GE Patecatl 002 is unable to carry out its primary standing order: Refuel from Colony or Hub (All)
SS Chalchiutotolin 003 is unable to carry out its primary standing order: Refuel from Colony or Hub (All)
SS Chalchiutotolin 004 is unable to carry out its primary standing order: Refuel from Colony or Hub (All)
BDB Judas Priest III 001 is unable to carry out its primary standing order: Join Operational Group
BDB Judas Priest III 002 is unable to carry out its primary standing order: Join Operational Group
BDB Judas Priest III 003 is unable to carry out its primary standing order: Join Operational Group
SV Grizzly Bear 001 is unable to carry out its primary standing order: Join Operational Group
As per standing orders TT Brundisium 003 is moving to join Troop Transport Group - Jump 006
My rough guess is that you deleted the operational group, which most newly produced things try to join...
I guess a new OG should be automatically created when a new construction cycle starts - at least, if you have the patience to make it to that...
Posted by: Zook
« on: December 16, 2021, 11:27:56 PM »

I'm in the precisely same situation, i.e. stuck in 2-hour increments. I've used DB Browser (for the first time) on a copy of the DB and found a suspicious entry at about the time the trouble began: "Destination of FAC Hunter Squadron - Jump 011 cannot be found. Please issue new orders". I deleted that fleet and its ships and the result was that I'm now stuck on 6-minute increments.

I'm not about to give up, but I have no idea how to identify a fleet trying to jump or anything like that. The move orders are incomprehensible. Could anybody walk me through this, or give me a hint how to proceed?

These are the last log entries. Some of these messages already appeared before the 2-hour problem began.
-----------------------------------------
GE Gwanggaeto the Great 002 is unable to carry out its primary standing order: Refuel from Colony or Hub (All)
GE Gwanggaeto the Great 003 is unable to carry out its primary standing order: Refuel from Colony or Hub (All)
GE Gwanggaeto the Great 004 is unable to carry out its primary standing order: Refuel from Colony or Hub (All)
Stabilisation Squadron 003 is unable to carry out its primary standing order: Build Jump Gate at Nearest Jump Point
Stabilisation Squadron 004 is unable to carry out its primary standing order: Build Jump Gate at Nearest Jump Point
Stabilisation Squadron 003 is unable to carry out its primary standing order: Build Jump Gate at Nearest Jump Point
Stabilisation Squadron 004 is unable to carry out its primary standing order: Build Jump Gate at Nearest Jump Point
JD Saint Augusta 001 is unable to carry out its primary standing order: Join Operational Group
JD Saint Augusta 002 is unable to carry out its primary standing order: Join Operational Group
GE Thufir Hawat 002 is unable to carry out its primary standing order: Refuel from Colony or Hub (All)
DDG Iri IV 039 is unable to carry out its primary standing order: Join Operational Group
DDG Iri IV 040 is unable to carry out its primary standing order: Join Operational Group
FT Viroconium 013 is unable to carry out its primary standing order: Join Operational Group
DDG Iri IV 041 is unable to carry out its primary standing order: Join Operational Group
DDG Iri IV 042 is unable to carry out its primary standing order: Join Operational Group
DDG Iri IV 043 is unable to carry out its primary standing order: Join Operational Group
DDG Iri IV 044 is unable to carry out its primary standing order: Join Operational Group
DDG Iri IV 045 is unable to carry out its primary standing order: Join Operational Group
DDG Iri IV 046 is unable to carry out its primary standing order: Join Operational Group
DDG Iri IV 047 is unable to carry out its primary standing order: Join Operational Group
DDG Iri IV 048 is unable to carry out its primary standing order: Join Operational Group
DDG Iri IV 049 is unable to carry out its primary standing order: Join Operational Group
DDG Iri IV 050 is unable to carry out its primary standing order: Join Operational Group
SS Modena 001 is unable to carry out its primary standing order: Refuel from Colony or Hub (All)
SS Modena 002 is unable to carry out its primary standing order: Refuel from Colony or Hub (All)
Stabilisation Squadron 001 is unable to carry out its primary standing order: Build Jump Gate at Nearest Jump Point
SS Modena 003 is unable to carry out its primary standing order: Refuel from Colony or Hub (All)
Stabilisation Squadron 002 is unable to carry out its primary standing order: Build Jump Gate at Nearest Jump Point
DDG Exodus II 003 is unable to carry out its primary standing order: Join Operational Group
DDG Exodus II 004 is unable to carry out its primary standing order: Join Operational Group
Stabilisation Squadron 003 is unable to carry out its primary standing order: Build Jump Gate at Nearest Jump Point
Stabilisation Squadron 004 is unable to carry out its primary standing order: Build Jump Gate at Nearest Jump Point
GE Patecatl 001 is unable to carry out its primary standing order: Refuel from Colony or Hub (All)
GE Patecatl 002 is unable to carry out its primary standing order: Refuel from Colony or Hub (All)
SS Chalchiutotolin 003 is unable to carry out its primary standing order: Refuel from Colony or Hub (All)
SS Chalchiutotolin 004 is unable to carry out its primary standing order: Refuel from Colony or Hub (All)
BDB Judas Priest III 001 is unable to carry out its primary standing order: Join Operational Group
BDB Judas Priest III 002 is unable to carry out its primary standing order: Join Operational Group
BDB Judas Priest III 003 is unable to carry out its primary standing order: Join Operational Group
SV Grizzly Bear 001 is unable to carry out its primary standing order: Join Operational Group
As per standing orders TT Brundisium 003 is moving to join Troop Transport Group - Jump 006
Posted by: nuclearslurpee
« on: April 23, 2021, 11:00:38 AM »

Quote from: idefelipe on April 23, 2021, 09:43:12 AM
And.. how can we do that?  ??? ???

Any SQL browser/editor can let you work with the database and make small changes if needed. For example, DB Browser for SQLite.

The table "FCT_GameLog" is your starting point and you can see if for example a particular NPR fleet is jumping back and forth at every sub-increment. You'll have to get comfortable with exploring different tables to find the spot you need to make a change. For example, changing the NPR fleet's position to be away from any jump point may solve the problem.
Posted by: idefelipe
« on: April 23, 2021, 09:43:12 AM »

And.. how can we do that?  ??? ???