Vizzy is Broken

@AndrewGarrison Unit tests really should have picked this up. Not that I have not pushed much worse on a Friday afternoon -- no judgement here, man. At a high level, can you talk about what kind of dev-ops or CI/CD regime you guys employ? I am professionally curious.

@AndrewGarrison I want you to know that I apreciate very much your swift reply.. I never posted before on any game thread but I like this game. Thanks fpr your efforts

@Ghazal Sorry, the dev notes were confusing but they are for my own reference. This bug has been fixed and the fix will be in the next update. As @SoMa has recommended, the best workaround until then is to put a Wait 1 Second immediately after an Activate Stage.

@AndrewGarrison I do not understand what exactly are you telling us.. there is a youtube tutorial by Jundroo on their youtube channel... I did what the dude did there... it didnt work.. it broke..
Instead of activating every stage on its time.. it activated all stages at once..
I tried many tweks around but didnt work. I repeat this is Android.. I dont have it on pc or ios

Same exact issue with the update -- broke every Vizzy script that uses Fuel In Stage = 0 or Performance = 0 to stage.

A quick and dirty work around (tested) is to drop in a [Wait 1 Second] statement between [Activate Stage] and [wait until Fuel in Stage = 0]

Dev Notes: The Vizzy program activates the stage and then immediately executes the Wait Until Fuel In Stage = 0 which evaluates to true. The Vizzy program needs to break execution for the frame to allow the craft to recalculate its structure and fuel levels.