Quote from: Aloriel on August 12, 2022, 07:46:25 PM

After attempting to attack a spoiler race, I lost all fighters from a carrier. From that point on, my carrier could not move.

I tried deleting all empty squadrons, multiple types of move orders, dividing the ship out of the fleet, SM teleport to Earth, and reloading the game. Nothing will get my ship moving again. It claims to have it's full movement speed, but never goes anywhere.

In the included DB file, the ship in question is the CV-01 SFS Warrior (in a fleet of the same name) now orbiting Earth. It is attempting to refuel and will never succeed.

Found it - but it was a weird one

There was nothing unusual about the class design (and there was another ship of the same design that was fine). There was nothing unusual about the ship in the database, or the fleet record. Creating a new fleet or detaching the ship didn't change anything either. The movement orders were all normal. I was starting to wonder if Aurora had somehow developed a sense of humour and was just trying to wind me up

Eventually, I realised that the combination of ship commander, flag bridge and admin command was creating a reaction bonus more than 100%, which ended up tipping the fleet into a negative reaction score (Reaction is based on 1 - Bonus). The fleet movement code ignores fleets with negative reaction scores, so the orders were never being executed. I've added a cap to reaction bonus of 99% and now the fleet moves normally.

Oh I recall reporting this bug on 1.13 a while ago as I used quite deep naval hierarchy and had a few officers with 50% reaction bonus. For those suffering from this on any version, either use the DB to nerf the reaction bonuses of officers in the hierarchy or avoid assigning too many commanders with high reaction bonuses.

I got errors #1957, #1948, #1953, #460 on start, then #2147 every turn in this save.
In foreign relation window, "UK" does not show up in either "China" or "Japan" races.
I suspect it is because I named one of the factions as "UK" that is too short 

SJW: What are the error messages (the text) ?

Errors are (translated)
#1957 Index and length must be referencing position of String, parameter: length
#1953 Dereferencing null
#1948 Dereferencing null
looped 3 times, and then
#460 Index not in dictionary
twice,
and then #2147 Index not in dictionary shows up every time I click on any time progress buttons

Should be easily reproducible from the save I attached in the original post.

SJW: Your theory around the length of the alien race name was correct. Fixed for v2.1

I've encountered a minor bug that is easily reproducible.

If you delete an order template, you will no longer be able to issue any orders for any fleet due to all commands going missing.

The only way to fix this is to close the Naval Org screen and open it again.

Perhaps you still have the "Order Templates" radio button selected, rather than "System Locations" or "Auto-Route by System"?

Getting the error #2524: The given key was not present in the dictionary with "use alien tech" enabled in the class design screen.

SJW: Already reported and fixed for v2.1
http://aurora2.pentarch.org/index.php?topic=13023.msg160934#msg160934

Quote from: Steve Walmsley on August 13, 2022, 08:27:36 AM

Quote from: Coleslaw on August 11, 2022, 10:39:21 AM

Beam fire controls that are set to open fire and are then destroyed in combat do not cease their firing, resulting in forced 5-second intervals until damage controls repairs the fire control or you scuttle the damaged ship. The button on the miscellaneous tab of the tactical menu to cease fire all ships does not cease fire of destroyed fire controls.

I would assume this applies to missile fire controls also, though I haven't tested them explicitly.

There is something else going on here, as there is code to prevent the above. Its very common for fire controls to be destroyed while they are set to open fire, so if this was a general error it would be reported a lot. Can you provide more detail about the incident when this happened and how the fire control was destroyed?

The situation surrounding the destruction wasn't entirely unique unfortunately. Just a battle between a wing of FACs and a few Aether Raiders. I looked back through the event logs for that in-game date and noticed that the 5-seconds didn't immediately begin after the destruction of the fire-control, just very shortly after it so that might be my mistake. However, regardless, the game stopped being interrupted as soon as I scuttled the ship, which makes me think maybe an enemy ship had targeted my FAC that couldn't shoot at it, whether due to the enemy's weapons being destroyed or them being out of range, but not clearing the target for some reason. My FAC design mounts particle beams and just uses its speed to stay out of range of the enemy (usually) so maybe it kept coming in and out of the enemy fire control ranges during the one second sub pulses and the AI couldn't properly target/detarget?

That's all I can really add unfortunately. I'll try to test further and see if there's a way to recreate it but I'm not a bug sleuth like some of the people on this forum. 

Thanks for the update. I think your theory about the enemy ship somehow not clearing its targeting sounds like a potential cause.

Quote from: Coleslaw on August 11, 2022, 10:39:21 AM

Beam fire controls that are set to open fire and are then destroyed in combat do not cease their firing, resulting in forced 5-second intervals until damage controls repairs the fire control or you scuttle the damaged ship. The button on the miscellaneous tab of the tactical menu to cease fire all ships does not cease fire of destroyed fire controls.

I would assume this applies to missile fire controls also, though I haven't tested them explicitly.

There is something else going on here, as there is code to prevent the above. Its very common for fire controls to be destroyed while they are set to open fire, so if this was a general error it would be reported a lot. Can you provide more detail about the incident when this happened and how the fire control was destroyed?

The situation surrounding the destruction wasn't entirely unique unfortunately. Just a battle between a wing of FACs and a few Aether Raiders. I looked back through the event logs for that in-game date and noticed that the 5-seconds didn't immediately begin after the destruction of the fire-control, just very shortly after it so that might be my mistake. However, regardless, the game stopped being interrupted as soon as I scuttled the ship, which makes me think maybe an enemy ship had targeted my FAC that couldn't shoot at it, whether due to the enemy's weapons being destroyed or them being out of range, but not clearing the target for some reason. My FAC design mounts particle beams and just uses its speed to stay out of range of the enemy (usually) so maybe it kept coming in and out of the enemy fire control ranges during the one second sub pulses and the AI couldn't properly target/detarget?

That's all I can really add unfortunately. I'll try to test further and see if there's a way to recreate it but I'm not a bug sleuth like some of the people on this forum. 

Beam fire controls that are set to open fire and are then destroyed in combat do not cease their firing, resulting in forced 5-second intervals until damage controls repairs the fire control or you scuttle the damaged ship. The button on the miscellaneous tab of the tactical menu to cease fire all ships does not cease fire of destroyed fire controls.

I would assume this applies to missile fire controls also, though I haven't tested them explicitly.

There is something else going on here, as there is code to prevent the above. Its very common for fire controls to be destroyed while they are set to open fire, so if this was a general error it would be reported a lot. Can you provide more detail about the incident when this happened and how the fire control was destroyed?

If you have more naval ranks than ground commander ranks, you won't be able to promote a ground commander to any new ground commander ranks you add.

From what I see in the database, it seems that when you add a new ground commander rank, the game is changing the Priority value of the existing ground commander ranks based on the highest Priority of all ranks, rather than of only ground commander ranks.

I can't reproduce this. Adding a new ground rank works fine, regardless of the number of naval ranks. The priorities are set correctly and saved correctly to the database. I've gone through the code line by line and it only changes the rank priorities for the chosen rank type. Do you definitely have an existing ground rank selected when you added the new ground rank?