Author Topic: Official v5.50 Bugs Thread  (Read 84630 times)

0 Members and 1 Guest are viewing this topic.

Offline SpecialK

  • Petty Officer
  • **
  • S
  • Posts: 16
Re: Official v5.50 Bugs Thread
« Reply #525 on: December 19, 2011, 08:54:29 PM »
Quote from: Theeht link=topic=3895.  msg43445#msg43445 date=1321721337
2) My planet also says that every 5 day increment, it has loses 5  Duranium under the SP +/- column.     Looking at the stockpiled number, it increases by 12 each 5 days.     The -5 changes depending on what I am building, but does not reflect the actual income.     I think it is not counting the input from mass drivers, because the Mass Driver +/- column is showing zero on all minerals on all colonies, including those firing mass drivers to earth, and I can see the packets on the System View.   

I can confirm this error in 5. 5. 5.   It makes it really tough to estimate mineral needs when you're drilling the heck out of a bunch of surrounding planets and mass-driving it all towards your settled planet. 
 

Offline Sotak246

  • Sub-Lieutenant
  • ******
  • Posts: 129
Re: Official v5.50 Bugs Thread
« Reply #526 on: December 20, 2011, 01:13:52 AM »
The Precursor surrender bug is still up and about.  I captured a small listening post and was immediately informed that 1 DDG and a Missile Defense Base surrendered due to no missiles, as well as 17 Combat Transports with boarded troops.  None of which were in the original system but spread between 15 different systems.  I also suddenly found myself with info on 13 new systems but no idea where they are in relation to my systems.

Mark
 

Offline SpecialK

  • Petty Officer
  • **
  • S
  • Posts: 16
Re: Official v5.50 Bugs Thread
« Reply #527 on: December 20, 2011, 08:21:22 PM »
Quote from: georgiaboy1966 link=topic=3895. msg43806#msg43806 date=1322453068
Error
"error in updateallsensors"
"
"error 6 was generated by Aurora"
"Overflow"


I think I have asked this one before, but never got an answer.

I know the the cause for the error is the activation of a new sensor on an enemy ship. 
This error causes the above error message to appear and force a physical action from myself.

Is there a work around for it, since in large battles, you have to sit at the computer and acknoledge each error for the turn to continue.
I am having a battle right now where a 5 second turn is taking 30-45 minutes.
would be nice to leave the battle on auto over several nights to advance the battle.

Additional data point: This is happening every 6 seconds for me when I'm up against a ship that has a ECM strength of 30, which is keeping me from targeting the ship.  I get one error per fire control that has a zero chance of hit. 
 

Offline TheDeadlyShoe

  • Vice Admiral
  • **********
  • Posts: 1264
  • Thanked: 58 times
  • Dance Commander
Re: Official v5.50 Bugs Thread
« Reply #528 on: December 21, 2011, 04:23:42 AM »
the problem is whichever ship has the bugged sensors.  The only workaround i know is to blow that ship up. 
 

Offline Scout1

  • Leading Rate
  • *
  • S
  • Posts: 9
  • Thanked: 1 times
Re: Official v5.50 Bugs Thread
« Reply #529 on: December 23, 2011, 03:27:09 AM »
Hi, running 5.  55. 


Quote
Error 3201 was generated by DAO.  Recordset
You cannot add or change a record because a related record is required in table 'TechSystem'. 
Please report to hxxp: aurora2.  pentarch.  org/viewforum.  php?f=11

This error appeared following an error with freighters.   I had them picking up mines at earth and transporting them to a nearby mining colony.   I got a little overzealous and possibly lazy, and instead of entering  a number in the repeat section I simply mashed repeat about 20 times.   This froze the entire window followed by Aurora and I was forced to close it.   It started back up fine and let me progress approximately 15 in-game days, but when the freighters arrived at the planet it would give me an error 6 overflow.   I tried a few things but got fed up and spacemaster'd into deleting the ships, completely erasing them.   Now when I try to do turns, it does this.  .  . 


EDIT: Running in administrator does NOT solve this issue.
« Last Edit: December 23, 2011, 03:33:26 AM by Scout1 »
 

Offline Scout1

  • Leading Rate
  • *
  • S
  • Posts: 9
  • Thanked: 1 times
Re: Official v5.50 Bugs Thread
« Reply #530 on: December 24, 2011, 03:27:48 AM »
Quote from: Scout1 link=topic=3895. msg44834#msg44834 date=1324632429
Hi, running 5.   55.  


This error appeared following an error with freighters.    I had them picking up mines at earth and transporting them to a nearby mining colony.    I got a little overzealous and possibly lazy, and instead of entering  a number in the repeat section I simply mashed repeat about 20 times.    This froze the entire window followed by Aurora and I was forced to close it.    It started back up fine and let me progress approximately 15 in-game days, but when the freighters arrived at the planet it would give me an error 6 overflow.    I tried a few things but got fed up and spacemaster'd into deleting the ships, completely erasing them.    Now when I try to do turns, it does this.   .   .  


EDIT: Running in administrator does NOT solve this issue. 



Fixed by deleting the (now empty) task group.  Somewhere between deleting the ships themselves and tearing my hair out it cleared the fleet's orders, allowing me access back to their fleet page and said solution.
 

Offline Steve Walmsley (OP)

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 11667
  • Thanked: 20428 times
Re: Official v5.50 Bugs Thread
« Reply #531 on: December 26, 2011, 06:28:23 AM »
The Precursor surrender bug is still up and about.  I captured a small listening post and was immediately informed that 1 DDG and a Missile Defense Base surrendered due to no missiles, as well as 17 Combat Transports with boarded troops.  None of which were in the original system but spread between 15 different systems.  I also suddenly found myself with info on 13 new systems but no idea where they are in relation to my systems.

Mark

I have had yet another attempt to fix this problem :). I haven't been able to reproduce it but I think I have changed something that may cause it. Time will tell :)

Steve
 

Offline Shemar

  • Petty Officer
  • **
  • S
  • Posts: 17
Re: Official v5.50 Bugs Thread
« Reply #532 on: December 26, 2011, 07:34:20 AM »
I have tracked down the "Error in qrtSorted_SelChange: Error 30009 was generated by MSFlexgrid.  Invalid Row Value" in the Leaders screen.

It happens when the leader selected on the right (using the search section) is the top one displayed on the left (rank seniority), but only if the particular rank was not the one displayed before.

Steps to reproduce, assuming you have at least one Vice Admiral otherwise use lower ranks:
- Select Vice Admiral in the Ranks and Seniority section and if you have more than one make a mental note of the top ranking one's name.
- Search by Rear Admirals or higher.
- Select any Rear Admiral.  If by any chance you selected the most senior you will get th error, otherwise you will not.
- Select the most senior Vice Admiral.  You will get the error for sure.

The error may not occur is the officers are not assigned to commands.  I have not checked.
 

Offline Steve Walmsley (OP)

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 11667
  • Thanked: 20428 times
Re: Official v5.50 Bugs Thread
« Reply #533 on: December 26, 2011, 10:43:11 AM »
Even with jump efficiency 4, a 6000 ton commercial drive only costs 4 wealth. They've always been absurdly cheap. ^^

I have set the minimum cost for a jump drive at 10 BP

Steve
 

Offline sloanjh

  • Global Moderator
  • Admiral of the Fleet
  • *****
  • Posts: 2805
  • Thanked: 112 times
  • 2020 Supporter 2020 Supporter : Donate for 2020
    2021 Supporter 2021 Supporter : Donate for 2021
Re: Official v5.50 Bugs Thread
« Reply #534 on: December 26, 2011, 07:09:31 PM »
I have tracked down the "Error in qrtSorted_SelChange: Error 30009 was generated by MSFlexgrid.  Invalid Row Value" in the Leaders screen.

It happens when the leader selected on the right (using the search section) is the top one displayed on the left (rank seniority), but only if the particular rank was not the one displayed before.

Steps to reproduce, assuming you have at least one Vice Admiral otherwise use lower ranks:
- Select Vice Admiral in the Ranks and Seniority section and if you have more than one make a mental note of the top ranking one's name.
- Search by Rear Admirals or higher.
- Select any Rear Admiral.  If by any chance you selected the most senior you will get th error, otherwise you will not.
- Select the most senior Vice Admiral.  You will get the error for sure.

The error may not occur is the officers are not assigned to commands.  I have not checked.

I isolated a similar bug a long time ago - it sounds like it was never fixed....

John
 

Offline Steve Walmsley (OP)

  • Aurora Designer
  • Star Marshal
  • S
  • Posts: 11667
  • Thanked: 20428 times
Re: Official v5.50 Bugs Thread
« Reply #535 on: December 27, 2011, 06:26:30 AM »
I have tracked down the "Error in qrtSorted_SelChange: Error 30009 was generated by MSFlexgrid.  Invalid Row Value" in the Leaders screen.

It happens when the leader selected on the right (using the search section) is the top one displayed on the left (rank seniority), but only if the particular rank was not the one displayed before.

Steps to reproduce, assuming you have at least one Vice Admiral otherwise use lower ranks:
- Select Vice Admiral in the Ranks and Seniority section and if you have more than one make a mental note of the top ranking one's name.
- Search by Rear Admirals or higher.
- Select any Rear Admiral.  If by any chance you selected the most senior you will get th error, otherwise you will not.
- Select the most senior Vice Admiral.  You will get the error for sure.

The error may not occur is the officers are not assigned to commands.  I have not checked.

I've tried following the above exactly but I can't reproduce it. Please could you check you are definitely using v5.55 as I seem to recall fixing something like this in the past.

Steve
 

Offline Shemar

  • Petty Officer
  • **
  • S
  • Posts: 17
Re: Official v5.50 Bugs Thread
« Reply #536 on: December 27, 2011, 09:26:44 AM »
Quote from: Steve Walmsley link=topic=3895. msg44892#msg44892 date=1324988790
I've tried following the above exactly but I can't reproduce it.  Please could you check you are definitely using v5. 55 as I seem to recall fixing something like this in the past.

Steve

Make sure all the officers involved are assigned to commands.  Also I am not sure if it matters which commands (for example in teams, staff offices, different systems etc. ).  The various checkboxes (like "Assign to any Location") may also play a part.  I will try to document those too.  I can send you my database if you want, it happens with 100% consistency.  I am 99% sure I am using 5. 55 as this was the current version when I installed on my new computer and started my latest game, but I will re-verify when I get home.
« Last Edit: December 27, 2011, 09:28:30 AM by Shemar »
 

Offline Shemar

  • Petty Officer
  • **
  • S
  • Posts: 17
Re: Official v5.50 Bugs Thread
« Reply #537 on: December 27, 2011, 03:07:58 PM »
Confirmed version 5.55 on the above issue.

Tomorrow I will upgrade to 5.56 and re-test. Screen shots and/or database available for troubleshooting.
 

Offline Socialist Threat

  • Petty Officer
  • **
  • S
  • Posts: 16
Re: Official v5.50 Bugs Thread
« Reply #538 on: January 07, 2012, 02:50:21 PM »
Error 3265 was generated by DAO. Fields
Ii'm using v. 5. 52 but failed to find an appropriate thread, sorry >_>

So, there was some glitch about the same (afaik) error when i was just generating the world.  But the main problem started when I found an NPR which attacked my own system.  I believe it's a Swarm-type NPR.  At first there were 4 big ships which seemed to be something like slow giant (60 000 t) sensor-ships, and there seemed to be no problem with them, but when these ships approached my home-planet a series of 3625-errors appeared, at the same time as some smaller ad faster swarm-ships approached the Earth and seemed to attack it.  I have no idea what happen to them afterwards, they just disappeared, perhaps due to the error? This NPR doesn't seem to be that dangerous, though it's just 2033 and i haven't got any decent Navy yet, but a bit amount of 3625 error messages keep to appear around every 5 days, which slows down the game seriously.
 

Offline OAM47

  • Sub-Lieutenant
  • ******
  • Posts: 142
Re: Official v5.50 Bugs Thread
« Reply #539 on: January 07, 2012, 04:05:27 PM »
I actually just got that same error code in .54 when genning a system with a wormhole [/spoilers].

I wouldn't report it normally, as I'm not using the latest version, so I dunno if 56 or 60 fixed it, but I find that odd timing.