Author Topic: 4.26 Bugs  (Read 23138 times)

0 Members and 1 Guest are viewing this topic.

Offline Steve Walmsley

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 12186
  • Thanked: 23779 times
  • 2025 Supporter 2025 Supporter : Support the forums in 2025
    Gold Supporter Gold Supporter :
    Above & Beyond Supporter Above & Beyond Supporter :
Re: 4.26 Bugs
« Reply #150 on: October 13, 2009, 09:59:35 AM »
Quote from: "jfelten"
Well, I tried going back to the mdb file I had saved before advancing time and restarting from there, but about 13 days in I started getting this error again.  

---------------------------
Error in GetBodySuitability
---------------------------
Error 11 was generated by Aurora
Division by zero
Please report to viewforum.php?f=11
---------------------------
OK  
---------------------------
This error was originally in v4.2 i think. It was caused by NPRs being set up on non-habitable planets due to a data error in the database. The DB update patch fixed the error so that NPRs would be setup correctly in future. Unfortunately, it cannot fix any existing NPRs. If the NPR causing the problem was the one set up at the game start, the only thing you can do is delete it or start a new game. However, deleting NPRs is a pretty tricky operation as you have to know all the correct tables to modify. If you want to send me your DB, I can remove the NPR and send it back to you.

Quote
It would be a nice feature to be able to export/import ship designs. People could then swap them, although matching the technology might make that impractical.
The export and import ship designs won't work because each race has its own tech. The tech IDs in the database for the class components won't match the systems for another race or in another database

Steve
 

Offline jfelten

  • Lieutenant
  • *******
  • j
  • Posts: 187
Re: 4.26 Bugs
« Reply #151 on: October 13, 2009, 10:08:43 AM »
Thanks Steve.  I'll probably email you my .mdb when I get home in a couple hours.  It is kind of you to offer to fix it, especially since I've only invested hours and not days or weeks in this particular game as some I know have.  I might have an old copy of the full Office 2000 with Access included I could install (I only run one old windows box and that is just for games).  Would that version of Access allow me to delete or fix the NPR?  Could I just force the NPR's HW to a habitable type?  I searched for an in-game way in SM mode but couldn't find a way to delete an NPR.  And I don't have the DM password if that is the only way in-game.
 

Offline Steve Walmsley

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 12186
  • Thanked: 23779 times
  • 2025 Supporter 2025 Supporter : Support the forums in 2025
    Gold Supporter Gold Supporter :
    Above & Beyond Supporter Above & Beyond Supporter :
Re: 4.26 Bugs
« Reply #152 on: October 13, 2009, 10:29:12 AM »
Quote from: "jfelten"
Thanks Steve.  I'll probably email you my .mdb when I get home in a couple hours.  It is kind of you to offer to fix it, especially since I've only invested hours and not days or weeks in this particular game as some I know have.  I might have an old copy of the full Office 2000 with Access included I could install (I only run one old windows box and that is just for games).  Would that version of Access allow me to delete or fix the NPR?  Could I just force the NPR's HW to a habitable type?  I searched for an in-game way in SM mode but couldn't find a way to delete an NPR.  And I don't have the DM password if that is the only way in-game.
You can delete the NPR from the Race table. However, you will also have to delete any records in the AlienRace table where the deleted NPR is either the AlienRaceID or the ViewRaceID and any record in the GameLog table that reference the same RaceID. You will need to delete any records in the CurrentDesigns table where the EmpireID is set to the deleted RaceID and you will need to set the ControlRaceID and OldControlID fields in the RaceSysSurvey table to zero if any are set to the deleted RaceID. All the other tables that reference the race (Ship, Fleets, Shipyards, etc.) will be deleted with the cascade deletes set up within the database.

Steve
 

Offline James Patten

  • Lt. Commander
  • ********
  • J
  • Posts: 257
  • Thanked: 2 times
Re: 4.26 Bugs
« Reply #153 on: October 13, 2009, 11:02:25 AM »
I made the mistake of trying to communicate with the Precursors and now every five days I'm told they are refusing, but I have no way of turning it off.  When I destroyed precursor ships there were no survivors.  Should the option of opening communication attempts even be present in the Inteligence window for precursors (or, if you don't recover any survivors)?
 

Offline welchbloke

  • Vice Admiral
  • **********
  • Posts: 1058
  • Thanked: 10 times
  • Gold Supporter Gold Supporter :
    2025 Supporter 2025 Supporter : Support the forums in 2025
Re: 4.26 Bugs
« Reply #154 on: October 13, 2009, 04:50:17 PM »
Quote from: "James Patten"
I made the mistake of trying to communicate with the Precursors and now every five days I'm told they are refusing, but I have no way of turning it off.  When I destroyed precursor ships there were no survivors.  Should the option of opening communication attempts even be present in the Inteligence window for precursors (or, if you don't recover any survivors)?
I've done the same thing (didn't know they were presursors when I tried to communicate). I don't know of any method to stop the 5 day message, I just lived with it until I screwed the game up without backing up my DB  :cry:
Welchbloke
 

Offline Beersatron

  • Rear Admiral
  • **********
  • Posts: 997
  • Thanked: 7 times
Re: 4.26 Bugs
« Reply #155 on: October 13, 2009, 05:09:48 PM »
Quote from: "welchbloke"
Quote from: "James Patten"
I made the mistake of trying to communicate with the Precursors and now every five days I'm told they are refusing, but I have no way of turning it off.  When I destroyed precursor ships there were no survivors.  Should the option of opening communication attempts even be present in the Inteligence window for precursors (or, if you don't recover any survivors)?
I've done the same thing (didn't know they were presursors when I tried to communicate). I don't know of any method to stop the 5 day message, I just lived with it until I screwed the game up without backing up my DB  :cry:

If you can get into the DB there is a flag in one of the tables that you can remove which stops the communication attempts. Unfortunately I can not remember the name of the table, but it is in there ... somewhere ...
 

Offline ZimRathbone

  • Captain
  • **********
  • Posts: 411
  • Thanked: 34 times
  • 2023 Supporter 2023 Supporter : Supporter of the forum in 2023
Fleet Training Bug (minor)
« Reply #156 on: October 14, 2009, 07:08:50 AM »
On each increment I get the following message:

Error in Fleet Training
Error 6 was generated by Aurora
Overflow

This appears once per fleet on a training excercise.  

Also (perhaps related) the fleets in training just seem to go to one location and never move therafter - it used to be that they would dot hither & yon around the system
Slàinte,

Mike
 

Offline Beersatron

  • Rear Admiral
  • **********
  • Posts: 997
  • Thanked: 7 times
Re: Fleet Training Bug (minor)
« Reply #157 on: October 14, 2009, 07:29:28 AM »
Quote from: "ZimRathbone"
On each increment I get the following message:

Error in Fleet Training
Error 6 was generated by Aurora
Overflow

This appears once per fleet on a training excercise.  

Also (perhaps related) the fleets in training just seem to go to one location and never move therafter - it used to be that they would dot hither & yon around the system

I have seen the issue with the fleet not moving even though it has the task force training mission, but didn't have the error message though.
 

Offline ZimRathbone

  • Captain
  • **********
  • Posts: 411
  • Thanked: 34 times
  • 2023 Supporter 2023 Supporter : Supporter of the forum in 2023
Secondary orders events
« Reply #158 on: October 14, 2009, 07:31:53 AM »
The secondary orders reporting in the event log seems in error.

For example - I usually set survey fleets with Default Orders  
Primary: Survey Nearest Planet or Moon
Secondary: Survey Nearest Body

Whenever a fleet cannot set its primary order (due to lack of suitable destinations) I get a message like
Survey 3 is unable to carry out its special survey order as there is no suitable destination within 10 billion kilometers
(so far so good)

The problem is that the follow up message usually refernces something that has no relevance eg
As per secondary orders Survey 3 has been assigned the following order: Activate Transponder Tiejus
 
and this message is the same for ALL fleets that have a secondary order triggered in that increment (other than the fleet name).  In this case it refrences another order for a different fleet, but in some cases it seems to refernce orders given to an entirely different race - I saw one referncing an order to survey a planet in a system I havent discovered yet.

The orders that are actually assigned to the fleets appear correct , it looks as if the event log is being written from a buffer that is not being flushed or updated.
Slàinte,

Mike
 

Offline Father Tim

  • Vice Admiral
  • **********
  • Posts: 2162
  • Thanked: 532 times
Re: 4.26 Bugs
« Reply #159 on: October 14, 2009, 11:50:15 PM »
When a ground unit is disbanded (using the Disband button on the Ground Units tab of the F2 'Population & Production' window) or a Replacement Division is entirely used up, its commander is not released from her assignment.  She continues to count as 'assigned' to her previous post until given a new assignment, or manually set as unassigned.
 

Offline Steve Walmsley

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 12186
  • Thanked: 23779 times
  • 2025 Supporter 2025 Supporter : Support the forums in 2025
    Gold Supporter Gold Supporter :
    Above & Beyond Supporter Above & Beyond Supporter :
Re: 4.26 Bugs
« Reply #160 on: October 16, 2009, 04:13:39 AM »
Quote from: "Father Tim"
When a ground unit is disbanded (using the Disband button on the Ground Units tab of the F2 'Population & Production' window) or a Replacement Division is entirely used up, its commander is not released from her assignment.  She continues to count as 'assigned' to her previous post until given a new assignment, or manually set as unassigned.
Fixed for v4.3

Steve
 

Offline Steve Walmsley

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 12186
  • Thanked: 23779 times
  • 2025 Supporter 2025 Supporter : Support the forums in 2025
    Gold Supporter Gold Supporter :
    Above & Beyond Supporter Above & Beyond Supporter :
Re: Secondary orders events
« Reply #161 on: October 16, 2009, 04:28:59 AM »
Quote from: "ZimRathbone"
The secondary orders reporting in the event log seems in error.

For example - I usually set survey fleets with Default Orders  
Primary: Survey Nearest Planet or Moon
Secondary: Survey Nearest Body

Whenever a fleet cannot set its primary order (due to lack of suitable destinations) I get a message like
Survey 3 is unable to carry out its special survey order as there is no suitable destination within 10 billion kilometers
(so far so good)

The problem is that the follow up message usually refernces something that has no relevance eg
As per secondary orders Survey 3 has been assigned the following order: Activate Transponder Tiejus
 
and this message is the same for ALL fleets that have a secondary order triggered in that increment (other than the fleet name).  In this case it refrences another order for a different fleet, but in some cases it seems to refernce orders given to an entirely different race - I saw one referncing an order to survey a planet in a system I havent discovered yet.

The orders that are actually assigned to the fleets appear correct , it looks as if the event log is being written from a buffer that is not being flushed or updated.
Thanks for the details - that helped me track it down.

During the recent rewrite, I moved the code that sets up default geological survey orders into a separate section of code. However, I didn't move the line of code that records the order to the game log, which meant that the order description referenced by the seconday orders log entry was being picked up from the base table and will be probably be the oldest current order in the DB in all cases. This only affects geological survey-related secondary orders though. All other secondary orders should be fine. It's fixed for v4.3

Steve
 

Offline Steve Walmsley

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 12186
  • Thanked: 23779 times
  • 2025 Supporter 2025 Supporter : Support the forums in 2025
    Gold Supporter Gold Supporter :
    Above & Beyond Supporter Above & Beyond Supporter :
Re: 4.26 Bugs
« Reply #162 on: October 16, 2009, 04:43:19 AM »
Quote from: "James Patten"
I made the mistake of trying to communicate with the Precursors and now every five days I'm told they are refusing, but I have no way of turning it off.  When I destroyed precursor ships there were no survivors.  Should the option of opening communication attempts even be present in the Inteligence window for precursors (or, if you don't recover any survivors)?
I had already 'fixed' the precursor comm bug for v4.3 by having them refuse to communicate. After further thought though, I think I am just going to make them extremely difficult to communicate with so it's not immediately obvious if they are precursors.

With regard to your immediate problem, the only way to fix this is to change the CommStatus field in the AlienRace table to zero. And to find out which RaceID is the precursors, you will have to look at the Race table to see which RaceID is flagged as the Precursors.

Steve
 

Offline Steve Walmsley

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 12186
  • Thanked: 23779 times
  • 2025 Supporter 2025 Supporter : Support the forums in 2025
    Gold Supporter Gold Supporter :
    Above & Beyond Supporter Above & Beyond Supporter :
Re: Fleet Training Bug (minor)
« Reply #163 on: October 16, 2009, 04:44:47 AM »
Quote from: "ZimRathbone"
On each increment I get the following message:

Error in Fleet Training
Error 6 was generated by Aurora
Overflow

This appears once per fleet on a training excercise.  

Also (perhaps related) the fleets in training just seem to go to one location and never move therafter - it used to be that they would dot hither & yon around the system
Is this affecting every fleet that is in training? Also, has this bug always been there or did you train fleets in the past with no problems and the bug has appeared only recently?

Steev
 

Offline Steve Walmsley

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 12186
  • Thanked: 23779 times
  • 2025 Supporter 2025 Supporter : Support the forums in 2025
    Gold Supporter Gold Supporter :
    Above & Beyond Supporter Above & Beyond Supporter :
Re: 4.26 Bugs
« Reply #164 on: October 16, 2009, 04:46:44 AM »
Quote from: "IanD"
While in the second month of the above game I noticed my Survey ships had the following event against them "11th February 2065 08:00:01,Sol,As per secondary orders, Geo-Survey Group 1 has been assigned the following order.  Geological Survey Galloway's Star-A II". This is pretty good as I have yet to find any jump points :D . I have seen this type of error regularly and assume it’s something to do with the default secondary orders problem already described.
It would appear so - should be fixed now for v4.3

Steve