AI War Beta 5.077-5.079 "Cap Tectonics" Released!

[Diazo]

Can someone check out a Carrier's stats for me please?

They do not have AOE immunity listed anywhere but they are immune to the AOE from my lighting warheads.

If I give the warhead right-click on a carrier, it will damage that carrier as expected but another carrier overlapping the carrier I targeted will take no damage.

Am I missing something or is the AOE immunity in fact not listed for carriers?

D.

[Faulty Logic]

No AoE or Major Electric immunity listed.
Do you have auto-target carriers on? I bet with it off, it prevents AoE effects from hurting them.

[Kahuna]

No AOE or Major Electric immunity listed.
Do you have auto-target carriers on? I bet with it off, it prevents AoE effects from hurting them.

I have it on and the same problem --> bugged

[Faulty Logic]

Really? I just tested, and scrap-detonations damage carriers if and only if they are auto-targeted.

[Diazo]

'Auto-Target Carriers'?

Err, I vaguely remember something about that.

It's at default right now, I'll play with that.

D.

[Kahuna]

Really? I just tested, and scrap-detonations damage carriers if and only if they are auto-targeted.

Looks like carrier auto targeting has magically turned itself off. f

[keith.lamothe]

mmmMMMM-BWAHAHAAAHAHAAHAHAHAA
I think I'm going to wait a bit till stuff gets fixed xD THEN I'll update my game. Also I want to finish the game I'm playing atm.

The wave thing was already fixed in 5.078, though it looks like Lancefighter found another ripe (albeit apparently rare) one with the unhandled error.

[keith.lamothe]

Code: [Select]

9/5/2012 12:36:03 AM
UnhandledErrors:    9/5/2012 12:36:03 AM (5.078)
-----------------------------------Error-----------------------------------Log String: FixedUpdate: System.NullReferenceException: Object reference not set to an instance of an object
  at ForegroundObject.MovePlayerUnit (Boolean RecalculateFull, Boolean RecalcualteMiddling) [0x00000] in <filename unknown>:0
  at Game.RunOneCycleOfSimulation () [0x00000] in <filename unknown>:0
  at Game.RunNextCycle (Boolean DoRendering) [0x00000] in <filename unknown>:0
  at Game.RunFrame () [0x00000] in <filename unknown>:0
  at MainCameraLogic.FixedUpdate () [0x00000] in <filename unknown>:0
Stack Trace:   at ForegroundObject.MovePlayerUnit (Boolean RecalculateFull, Boolean RecalcualteMiddling) [0x00000] in <filename unknown>:0
  at Game.RunOneCycleOfSimulation () [0x00000] in <filename unknown>:0
  at Game.RunNextCycle (Boolean DoRendering) [0x00000] in <filename unknown>:0
  at Game.RunFrame () [0x00000] in <filename unknown>:0
  at MainCameraLogic.FixedUpdate () [0x00000] in <filename unknown>:0


   at System.Environment.get_StackTrace()
   at ArcenDebugging.ArcenDebugLog(System.String Message, DebugLogDestination Destination, Boolean IncludeStackTrace, Verbosity Verbosity)
   at ArcenDebugging.ArcenDebugLog(System.String Message, DebugLogDestination Destination, Verbosity Verbosity)
   at ArcenDebugging.ArcenDebugLog(System.String Message, Verbosity Verbosity)
   at Configuration.WriteToErrorFile(System.String ErrorFile, System.String ErrorName, System.String ErrorText)
   at MainCameraLogic.LogWritten(System.String LogString, System.String StackTrace, LogType Type, System.Exception Cause, Boolean CameFromUnity)
   at MainCameraLogic.LogWritten(System.String LogString, System.String StackTrace, LogType Type, System.Exception Cause)
   at MainCameraLogic.FixedUpdate()

Just got that. No real clue what caused it, but I've got a save directly after it said that? Says 'at move player unit'.. which sounds to me like it could be anything.

Fixed it for 5.079.  The only thing that's changed since 5.073 that could cause that, so far as I can tell, was the remains-rebuilder logic fix to make it drop its rebuild target if it was trying to rebuild an energy producer after the command station went down.  Basically, if:

1) The energy producer died
2) The rebuilder targeted the remains for rebuilding
3) The command station died
4) The rebuilder entered a wormhole or did something else to cause its CurrentPlanet reference to be set to null for that frame
5) The rebuilder then did its check for "can I actually do the rebuild now?"
6) The logic checking for the existence of the command station would reference CurrentPlanet and blow up.

So if this error gets at all common I'll go ahead and push the release, otherwise I'll wait to see if something else pops up to keep it company in the changelog.  Anyway, thanks

[TechSY730]

Fixed it for 5.079.  The only thing that's changed since 5.073 that could cause that, so far as I can tell, was the remains-rebuilder logic fix to make it drop its rebuild target if it was trying to rebuild an energy producer after the command station went down.  Basically, if:

1) The energy producer died
2) The rebuilder targeted the remains for rebuilding
3) The command station died
4) The rebuilder entered a wormhole or did something else to cause its CurrentPlanet reference to be set to null for that frame
5) The rebuilder then did its check for "can I actually do the rebuild now?"
6) The logic checking for the existence of the command station would reference CurrentPlanet and blow up.

So if this error gets at all common I'll go ahead and push the release, otherwise I'll wait to see if something else pops up to keep it company in the changelog.  Anyway, thanks

Wow, that is one tricky, hard to spot race condition. 
Good job finding it.

[Soyweiser]

I noticed something strange. There are groups of enemy ships that move very slowly and stuttery.

Look at the attached game, the vehe system, the group of enemies boosted by the armor booster.

(At first they move rather stuttery then they somehow start moving again).

In this case it had little effect, but I have seen the ships do that while not shooting at me. because they where out of range.

[Mánagarmr]

AI indecisiveness. That's an old one right there.

[Lancefighter]

That does indeed fit what I was doing at the time (sending remains rebuilders to frd on planets I needed rebuilding on)

I actually did notice the ai suttering a bit, (both going back and forth on defense, and once just moving really slowly, like <5 speed)

[Soyweiser]

Yeah the stuttering was very long even for some ships. I was able to kill a few guard posts, fly by them kill another before the stuttering stopped. (In one case. not the save I uploaded).

[Hearteater]

Sounds like this issue Soyweiser.  Did they happen to be Hybrid escorts by chance?

[Soyweiser]

I think they where.

I'm now doing some sort of lord of the colony ships mission lets see how that goe ... ow look colony ships. Hi! ... WTF