Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Allies 8a crashing on playtest build #16031
Just tried Allies 8a, it seems to have the same issue as Allies 7.
The Perf log returns a couple hundred lines of " 1 ms  Activity: CallLuaFunc", while all the other logs are empty.
I couldn't find any error in the actual LUA script, but that might just be me having no clue how to code.
Playtest 20190106 freezes 34 seconds after launching Allied mission 08a or 08b (Protect the Chronosphere). [Linux]
Fresh install of AppImage of Playtest 20190106. Default settings. Game launches fine, no problems in any mission or any match, until Allied mission 08a or 08b (Protect the Chronosphere).
I've had exactly the same experience, and looking at the Lua code (not my strongest language and I'm a beginner with the Lua API, so be gentle) it seems there is a recursive call at the end of the TargetAndAttack function, no matter what happens in the function.
Target selection in mission 7 is only slightly different from mission 8, but when the plane is selects a target (randomly from every enemy in the map) to attack in 7 it is visible, so the plane does an Attack successfully. (Which I guess means it will take a while to return?) In mission 8 I think it selects an enemy it can't see (many more targets in the big base than in the players force), so Attack returns at once and TargetAndAttack gets called again, etc. All starting at 34 seconds (on easy) because that is when the first mig is ready.
To check out my theory I changed
I imagine the recursive call is there to make sure migs continually look for targets, and it will work fine when the mapwide random targeting selects a visible enemy. I can't find anything in the Lua API that will tell you if an actor is visible to a player or to only select visible units, so I'm not sure how best to fix it.