4.26 Bugs

[schroeam (OP)]

I had a team that was on a ship that got blew up by an enemy, in which the captain of the ship got killed.  The team members did not get killed, and the team still existed, albeit in limbo and the members had no location on the Officer window.

This also happens when an espionage team is captured or killed.  They don't die or go to the no longer active category, but rather, are assigned to the "0" club.  

Adam.

[Paul M]

A minor bug.  I had some ships low on fuel and had the conditional order "if <30% go to nearest colony" active and they went to a colony without fuel.  Maybe it would be a good idea to add a check to see if the colony has fuel on hand.

Also ships on a training mission don't follow that conditional order which could be WAD but is a bit odd.

[waresky]

A very boring bug.
in F4,Search by Ability or location windows,Ability A: trade bonus,come this bug:
Error 91...Object variable or With block variable not set

if u "flag" unassigned Officers only come an bug windos for EVERY Unassigned officers...)...

2000 unassigned..u imagine.

[Thorgarth]

Receiving an "Error in CheckForMaintenanceFacilities" Error 91 was generated by Aurora, Object variable or With block variable not set.

Message continues to repeat until I kill the program.  
I have maintenance turned off for this galaxy.

[Beersatron]

One of my ships appears to have been leaking fuel!

I had a GE with a large fuel tank set to return and refuel at 30%, the size of the tank meant that 30% was going to be something like 20billion km - more than sufficient in my current game.

What seems to be happening is that on each time increment the fuel usage is being calculated at the start of the tick, but then there is an interrupt with the increment being shortened but the fuel for the full increment being subtracted.

This means that all of a sudden my GE is stuck in the middle of nowhere because his tank is dry  

[IanD]

Just started a 4.26 game, explored a couple of jump points. I have civilian shipping showing up in the newly explored system when I know they are in home system. Also saw this in 4.1. You can deselect and reselect the system to clear the problem, just a little irritating

Regards

[James Patten]

Had a ship that was finishing up it's given orders in another system (move to home system JG, transit, move to home world, refuel) when I added on to the orders to grab a cargo, move to another system's JG, transit, move to that world, drop the cargo.  I clicked the checkbox that causes the orders to repeatedly cycle.

Later I noticed in the F12 orders window that the ship was headed for the JG, but on F3 map of the second system was headed on a different vector.  I figured out that was using the vector of the JG for the first system, the system it was in when I composed the orders.  It did successfully transit back to home system.

Looks like there's a bug somewhere.  I couldn't tell if the F12 window was wrong in the time it took to get to the JG, as compared to the F3's view of it's location.

[alanwebber]

I've started occasionally getting the following error during regular (not economic) updates:

Error in AddToShippingLineWealth

Error 3201 was generated by DAO.Recordset
You cannot add or change a record because a related record is required in table 'ShippingLines'

When it pops up, I usually get the same error a few (~3-4) times at once.

I am pretty sure this is caused by an NPR not having a shipping line. I thought I had prevented this situation from occuring but it would seem not . I have another look through the code to see if I can find a hole in my logic.

Steve

Steve

This only happens when the "Shipping Lines" window is open. if you close it, the errors disappear but reappear if you have it open during an update.

Alan

[Brian Neumann]

I've started occasionally getting the following error during regular (not economic) updates:

Error in AddToShippingLineWealth

Error 3201 was generated by DAO.Recordset
You cannot add or change a record because a related record is required in table 'ShippingLines'

When it pops up, I usually get the same error a few (~3-4) times at once.

I am pretty sure this is caused by an NPR not having a shipping line. I thought I had prevented this situation from occuring but it would seem not . I have another look through the code to see if I can find a hole in my logic.

Steve

Steve

This only happens when the "Shipping Lines" window is open. if you close it, the errors disappear but reappear if you have it open during an update.

Alan

I have been getting the same error.  It always seems to be around the 5th of a month, every two to three months and I am getting about 20 such errors when it happens.  I am playing a game with a large non-tl starting race, and there is one npr created at the start of the game.  (my population to start was 5000m.)

Brian

[Kurt]

Just started a 4.26 game, explored a couple of jump points. I have civilian shipping showing up in the newly explored system when I know they are in home system. Also saw this in 4.1. You can deselect and reselect the system to clear the problem, just a little irritating

Regards

I've seen this as well.  

Kurt

[Father Tim]

"Error 3197 was generated by DAO.Recordset
The Microsoft Jet database engine stopped the process because you and another user are attempting to change the same data at the same time."

My conventional start player race is in the midst of a large ground battle with a neighbouring pre-TN empire on their planet - about 50 low-tech divisions each.  I have converted two LTI to Replacement divisons, and one of them was entirely 'used up' in the same increment as the error occurred.

[Thorgarth]

Receiving an "Error in CheckForMaintenanceFacilities" Error 91 was generated by Aurora, Object variable or With block variable not set.

Message continues to repeat until I kill the program.  
I have maintenance turned off for this galaxy.

Update:  First receive this error message:

Error 3075 was generated by DAO.Datebase
Syntax error (missing operator) in query express 'f.RaceID = 827 and f.SystemID = f.Xcor = -76964650 and f.Ycor = -128283291 and s.FleetID = f.FleetID and s.CurrentMaint > 0'.

[Beersatron]

Just entered a new system and it seems that a Race is being created:

Error in AddNextTech
Error 3021 was generated by DAO.Recordset
No current record.

Error in AddNextTech
Error 3020 was generated by DAO.Field
Update of CancelUpdate without AddNew or Edit

Error in AddNextTech
Error 3020 was generated by DAO.Recordset
Update of CancelUpdate without AddNew or Edit

[Paul M]

I've been seeing some very odd messages coming up from my survey forces plus some strange behavior.  They are set for primary default "Survey next three system locations" and secondary "survey nearest planet or moon."

1.  I've seen messages showing up that say they can't complete an order they were never given.  In this case load PDC components.  What is odd is that this is an order that was given to another task force.  I've seen this before in other versions so it seems a long standing issue but quite often I get these gibberish messages even though the ships themselves execute their orders eventually.
2.  They say they can't fulfil their secondary default order but then when I look they are executing their primary default order.
3.  They have often been trying to execute their secondary order before the primary order (I've seen them break off a JP survey to scan a moon).

Given 2 and 3 I think the routine is checking the default orders secondary before primary.

[Beersatron]

I have my Battle Fleet heading 3 systems away to put some hurt on a hostile race. As an escort, I gave two other fleets the command to stay 50k km ahead and offset 20 degrees clockwise and anticlockwise. I had Battle Fleet setup to move to the entry JG of the hostile race and the 2 escort fleets moved into position correctly. But, on the first exit JG from Sol, the two escort fleets didn't jump after the Battle Fleet. Instead, they appeared to move in a random direction within the Sol system for the rest of the timespan. It took 4 days to get everything back in shape.

Thinking about it some more, the escort fleets may have been trying to move to the X/Y coords of the Battle Fleet, only in the Sol system.