Jump to content

Alpha 25 Pre-release/Release Candidate Build Testing


Recommended Posts

None of the potential causes I can think of sounds particularly hard to fix. Then again, I have no clue as to which of them actually caused the bug, or if it is even one of them. No interest in finding out either.

A laughing reaction might fit the most since the message of doom and gloom isn't as serious when you start debugging.

However, at this point when this seems to be the norm and smooth releases doesn't seem to exist anymore, it might be worth it to consider the reasons why this is the case. Removing a singular oddly specific map script might sound like an attractive option, but people making that choice is the reason for this mess right now. Release with the bug, or fix it. Just don't bury it.

Link to comment
Share on other sites

ERROR: JavaScript error: simulation/components/UnitAI.js line 258 cmpControllerAI is null Order.FormationWalk@simulation/components/UnitAI.js:258:8 FSM.prototype.ProcessMessage@globalscripts/FSM.js:265:17 UnitAI.prototype.FinishOrder@simulation/components/UnitAI.js:3824:26 enter@simulation/components/UnitAI.js:2196:15 FSM.prototype.SwitchToNextState@globalscripts/FSM.js:366:14 FSM.prototype.ProcessMessage@globalscripts/FSM.js:274:8 UnitAI.prototype.ProcessMessage@simulation/components/UnitAI.js:4277:15 Attack.prototype.StopAttacking@simulation/components/Attack.js:526:14 Resistance.prototype.OnOwnershipChanged@simulation/components/Resistance.js:181:62

ERROR: Script message handler OnOwnershipChanged failed

ERROR: Error in timer on entity 5333, IID103, function TimerHandler: TypeError: cmpControllerAI is null Order.FormationWalk@simulation/components/UnitAI.js:258:8 FSM.prototype.ProcessMessage@globalscripts/FSM.js:265:17 UnitAI.prototype.FinishOrder@simulation/components/UnitAI.js:3824:26 Timer@simulation/components/UnitAI.js:3282:10 FSM.prototype.ProcessMessage@globalscripts/FSM.js:265:17 UnitAI.prototype.TimerHandler@simulation/components/UnitAI.js:4159:15 Timer.prototype.OnUpdate@simulation/components/Timer.js:139:44

ERROR: JavaScript error: simulation/components/UnitAI.js line 258 cmpControllerAI is null Order.FormationWalk@simulation/components/UnitAI.js:258:8 FSM.prototype.ProcessMessage@globalscripts/FSM.js:265:17 UnitAI.prototype.FinishOrder@simulation/components/UnitAI.js:3824:26 Order.Attack@simulation/components/UnitAI.js:427:16 FSM.prototype.ProcessMessage@globalscripts/FSM.js:265:17 UnitAI.prototype.PushOrderFront@simulation/components/UnitAI.js:3899:16 UnitAI.prototype.AttackVisibleEntity@simulation/components/UnitAI.js:4957:7 UnitAI.prototype.RespondToTargetedEntities@simulation/components/UnitAI.js:4994:15 UnitAI.prototype.AttackEntitiesByPreference@simulation/components/UnitAI_DE.js:89:14 LosAttackRangeUpdate@simulation/components/UnitAI.js:3278:11 FSM.prototype.ProcessMessage@globalscripts/FSM.js:265:17 UnitAI.prototype.OnRangeUpdate@simulation/components/UnitAI.js:4262:16

ERROR: Script message handler OnRangeUpdate failed

ERROR: JavaScript error: simulation/components/UnitAI.js line 258 cmpControllerAI is null Order.FormationWalk@simulation/components/UnitAI.js:258:8 FSM.prototype.ProcessMessage@globalscripts/FSM.js:265:17 UnitAI.prototype.FinishOrder@simulation/components/UnitAI.js:3824:26 Order.Attack@simulation/components/UnitAI.js:427:16 FSM.prototype.ProcessMessage@globalscripts/FSM.js:265:17 UnitAI.prototype.PushOrderFront@simulation/components/UnitAI.js:3899:16 UnitAI.prototype.AttackVisibleEntity@simulation/components/UnitAI.js:4957:7 UnitAI.prototype.RespondToTargetedEntities@simulation/components/UnitAI.js:4994:15 UnitAI.prototype.AttackEntitiesByPreference@simulation/components/UnitAI_DE.js:89:14 LosAttackRangeUpdate@simulation/components/UnitAI.js:3278:11 FSM.prototype.ProcessMessage@globalscripts/FSM.js:265:17 UnitAI.prototype.OnRangeUpdate@simulation/components/UnitAI.js:4262:16

ERROR: Script message handler OnRangeUpdate failed

ERROR: Error in timer on entity 5345, IID7, function Attack: TypeError: cmpControllerAI is null Order.FormationWalk@simulation/components/UnitAI.js:258:8 FSM.prototype.ProcessMessage@globalscripts/FSM.js:265:17 UnitAI.prototype.FinishOrder@simulation/components/UnitAI.js:3824:26 Order.Cheer@simulation/components/UnitAI.js:620:15 FSM.prototype.ProcessMessage@globalscripts/FSM.js:265:17 UnitAI.prototype.PushOrderFront@simulation/components/UnitAI.js:3899:16 UnitAI.prototype.Cheer@simulation/components/UnitAI.js:5810:7 UnitAI.prototype.CallPlayerOwnedEntitiesFunctionInRange@simulation/components/UnitAI.js:6433:23 enter@simulation/components/UnitAI.js:2216:12 FSM.prototype.SwitchToNextState@globalscripts/FSM.js:366:14 FSM.prototype.ProcessMessage@globalscripts/FSM.js:274:8 UnitAI.prototype.ProcessMessage@simulation/components/UnitAI.js:4277:15 Attack.prototype.StopAttacking@simulation/components/Attack.js:526:14 Attack.prototype.Attack@simulation/components/Attack.js:559:8 Timer.prototype.OnUpdate@simulation/components/Timer.js:139:44

Link to comment
Share on other sites

  On 29/07/2021 at 7:00 AM, wowgetoffyourcellphone said:

Another actor bug: Actors change seed when running (and possibly in other states).

To test this, go to Atlas, choose an Elite Athenian Sword Cav (or any other unit, really). Go to Actor Viewer. Set him to WALK, then set him to RUN. You will see his actor variations change. This also happens in-game, it's just easy to see in Actor Viewer for demonstration purposes. Whether this is a "release blocker" or not is up to you guys. :) 

Expand  

Fixed by https://code.wildfiregames.com/D4205

  • Thanks 2
Link to comment
Share on other sites

  On 10/07/2021 at 3:24 AM, azayrahmad said:

I still get crash upon opening Atlas with Unhandled unknown exception error. Like this:

gambar.png.d373e2a6424268a1ca3322897b7fd36e.png

I have attached the crashlog.txt below. Entire logs folder has also been attached, although not sure if it helps since mainlog and interestinglog don't show anything suspicious. This still happens even after I deleted cache folders. Is it just me?

crashlog.txt 18 kB · 3 downloads logs.zip 16 kB · 3 downloads

Expand  

I still get this even after installing RC 4, so I guess it's not build issue. A24 has no issue like this.

Link to comment
Share on other sites

  On 31/07/2021 at 6:14 AM, wowgetoffyourcellphone said:

ERROR: JavaScript error: simulation/components/UnitAI.js line 258 cmpControllerAI is null Order.FormationWalk@simulation/components/UnitAI.js:258:8 FSM.prototype.ProcessMessage@globalscripts/FSM.js:265:17 UnitAI.prototype.FinishOrder@simulation/components/UnitAI.js:3824:26 enter@simulation/components/UnitAI.js:2196:15 FSM.prototype.SwitchToNextState@globalscripts/FSM.js:366:14 FSM.prototype.ProcessMessage@globalscripts/FSM.js:274:8 UnitAI.prototype.ProcessMessage@simulation/components/UnitAI.js:4277:15 Attack.prototype.StopAttacking@simulation/components/Attack.js:526:14 Resistance.prototype.OnOwnershipChanged@simulation/components/Resistance.js:181:62

ERROR: Script message handler OnOwnershipChanged failed

ERROR: Error in timer on entity 5333, IID103, function TimerHandler: TypeError: cmpControllerAI is null Order.FormationWalk@simulation/components/UnitAI.js:258:8 FSM.prototype.ProcessMessage@globalscripts/FSM.js:265:17 UnitAI.prototype.FinishOrder@simulation/components/UnitAI.js:3824:26 Timer@simulation/components/UnitAI.js:3282:10 FSM.prototype.ProcessMessage@globalscripts/FSM.js:265:17 UnitAI.prototype.TimerHandler@simulation/components/UnitAI.js:4159:15 Timer.prototype.OnUpdate@simulation/components/Timer.js:139:44

ERROR: JavaScript error: simulation/components/UnitAI.js line 258 cmpControllerAI is null Order.FormationWalk@simulation/components/UnitAI.js:258:8 FSM.prototype.ProcessMessage@globalscripts/FSM.js:265:17 UnitAI.prototype.FinishOrder@simulation/components/UnitAI.js:3824:26 Order.Attack@simulation/components/UnitAI.js:427:16 FSM.prototype.ProcessMessage@globalscripts/FSM.js:265:17 UnitAI.prototype.PushOrderFront@simulation/components/UnitAI.js:3899:16 UnitAI.prototype.AttackVisibleEntity@simulation/components/UnitAI.js:4957:7 UnitAI.prototype.RespondToTargetedEntities@simulation/components/UnitAI.js:4994:15 UnitAI.prototype.AttackEntitiesByPreference@simulation/components/UnitAI_DE.js:89:14 LosAttackRangeUpdate@simulation/components/UnitAI.js:3278:11 FSM.prototype.ProcessMessage@globalscripts/FSM.js:265:17 UnitAI.prototype.OnRangeUpdate@simulation/components/UnitAI.js:4262:16

ERROR: Script message handler OnRangeUpdate failed

ERROR: JavaScript error: simulation/components/UnitAI.js line 258 cmpControllerAI is null Order.FormationWalk@simulation/components/UnitAI.js:258:8 FSM.prototype.ProcessMessage@globalscripts/FSM.js:265:17 UnitAI.prototype.FinishOrder@simulation/components/UnitAI.js:3824:26 Order.Attack@simulation/components/UnitAI.js:427:16 FSM.prototype.ProcessMessage@globalscripts/FSM.js:265:17 UnitAI.prototype.PushOrderFront@simulation/components/UnitAI.js:3899:16 UnitAI.prototype.AttackVisibleEntity@simulation/components/UnitAI.js:4957:7 UnitAI.prototype.RespondToTargetedEntities@simulation/components/UnitAI.js:4994:15 UnitAI.prototype.AttackEntitiesByPreference@simulation/components/UnitAI_DE.js:89:14 LosAttackRangeUpdate@simulation/components/UnitAI.js:3278:11 FSM.prototype.ProcessMessage@globalscripts/FSM.js:265:17 UnitAI.prototype.OnRangeUpdate@simulation/components/UnitAI.js:4262:16

ERROR: Script message handler OnRangeUpdate failed

ERROR: Error in timer on entity 5345, IID7, function Attack: TypeError: cmpControllerAI is null Order.FormationWalk@simulation/components/UnitAI.js:258:8 FSM.prototype.ProcessMessage@globalscripts/FSM.js:265:17 UnitAI.prototype.FinishOrder@simulation/components/UnitAI.js:3824:26 Order.Cheer@simulation/components/UnitAI.js:620:15 FSM.prototype.ProcessMessage@globalscripts/FSM.js:265:17 UnitAI.prototype.PushOrderFront@simulation/components/UnitAI.js:3899:16 UnitAI.prototype.Cheer@simulation/components/UnitAI.js:5810:7 UnitAI.prototype.CallPlayerOwnedEntitiesFunctionInRange@simulation/components/UnitAI.js:6433:23 enter@simulation/components/UnitAI.js:2216:12 FSM.prototype.SwitchToNextState@globalscripts/FSM.js:366:14 FSM.prototype.ProcessMessage@globalscripts/FSM.js:274:8 UnitAI.prototype.ProcessMessage@simulation/components/UnitAI.js:4277:15 Attack.prototype.StopAttacking@simulation/components/Attack.js:526:14 Attack.prototype.Attack@simulation/components/Attack.js:559:8 Timer.prototype.OnUpdate@simulation/components/Timer.js:139:44

Expand  

Fixed by https://code.wildfiregames.com/rP25845

  • Like 1
  • Thanks 1
Link to comment
Share on other sites

  On 03/08/2021 at 9:47 AM, Stan` said:

I've tried to barter in A24 & A25 and I don't see any messages, only when observer; Tribute messages still show.

Expand  

Confirmed! Looks like I did testing with a match which was already won, then one seems to be also an observer and thats why I saw my own bartering   : D

  • Like 1
Link to comment
Share on other sites

Here is the fifth 'Release Candidate' of Alpha 25 - Yaunā

We've entered Commit Freeze, which means we only now fix Release Blocker issues that we might yet find.

Downloads - Current bundles are for SVN revision 25848

Things to note:

  • Mind your mods -> they might introduce issues or Out Of Sync.
  • Save your A24 config file somewhere, ideally.

Notable changes since the last bundle:

  • Broken run variant fixed.
  • Some formation could trigger errors fixed.
  • Patrolling and attack walk unit when in formation fixed.
  • Formation gathering treasures fixed.
  • Map generation of ngorongoro fixed

What to do if I have an error or notice something weird?

Post your commands.txt (replay) and the interestinglog.html file from your folder. You can also reply to this thread.

What to do if the game crashes?

Update your crashlog.dmp and crashlog.txt  see https://trac.wildfiregames.com/wiki/GameDataPaths

What to do if I have an Out Of Sync?

You should go in your logs folder, find the replay (commands.txt at least), the mainlog/interestinglog and find the OOS dump folder. Zip all these files and upload them here.
We need the reports from two players to compare them: One OOS and one non-OOS players at least should upload their oos_dump files.

Things you may want to test (non-exhaustive)

  1. Launch a random game
  2. Launch a skirmish.
  3. Connect to the lobby
  4. Play on the lobby with someone
  5. Launch Atlas and try things out there
  6. Open Unit tests demo (To see if there any breakage in displaying entity's) (It's in scenarios)
  7. Enable feedback and see if it works (Main menu) See this  video
  8. Connect to and use mod.io
  9. Test replaying new games
  10. Test Screenshots (F2)
  11. Test Big Screenshots (Maj+F2)
  12. Test hotkeys
  13. Test Saving and loading a game.
  14. Test Quickload/Quicksave

And of course playing games.

  • Like 3
  • Thanks 4
Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...