In part one I went over how the effects in Ack Ack Attack! got made, first built in code and then rebuilt out of three free Unity packs. This part is the bugs that came along with them, and what's next.
Getting that many new effects in threw up a couple of other things. Each new effect compiles its shaders the first time it's drawn, which shows up as a hitch in the middle of a fight, so from July 12th one of each combat effect gets played behind the black loading curtain (the same fix as the first door hitch back in From Unreal to the App Store, Part Two). The turret explosion got missed off that list until September, when I noticed "a distinct pause while it loads the explosion", and once the bolts, an enemy and the muzzle flash joined it as well, the deck 1 load went from 146 to 220 milliseconds, once a session, where nobody can see it. The sneakier one was that a one-shot effect that ends up off screen pauses itself and never says it's finished, so it would just hang around, and now every one of them frees itself on a timer.
The fire jets had one more bug in them that took a while to find. In September I was still seeing white at the top of the flames ("flames still have whites at the top", as I put it at the time), and two rounds of colour tweaks didn't touch it. There were red herrings too, turning off mipmaps or reimporting the texture lossless both looked like they'd fixed it, and neither had. The real cause was a Godot gotcha. A new Gradient starts with two points, black at the start and opaque white at the end, and since points get sorted as you add them, setting point 1 after adding three more recoloured one of the new ones and left the white end alone, so every flame ramp since July had been quietly fading to white. Writing the ramps out in full sorted it.
The steam had exactly the same bug, and with Hovl's smoke puff it made a bright white cauliflower, which is why I'd asked for it to look "more smooth and not so curly". So the steam went back to the soft code dots from June, nice and see-through, then got twice as long that same night, and the next day the damage was cut back to the first 75% of the cloud, because the faint tail "looks great but makes navigation tough". You can still hide in the whole thing though.
For anyone wondering about the phone side of things, there are no custom shaders in any of the effects, they all use Godot's standard material, and every effect texture is VRAM compressed, with the biggest at 1024 square. Lights were the other budget. The mobile renderer only allows 8 omni lights per mesh, so out of up to about 58 wall and portal lights on a late map only the nearest 16 stay on, and the muzzle flash has a comment in its code that just says "Deliberately NO light (8-omni budget / horror mood)".
All told the effects are 20 scripts and 2,779 lines of code, touched by 46 check-ins (the original spawn field got 18 of those on its own, and it isn't even used anymore). As for Houdini, it's still on the list, the portals, the fire vent on the floor and the steam vents on the walls, same as I said back in August. The good news is the game can already play a flipbook, the cartoon battery explosion runs its fire through Godot's standard particle material, so a new sheet would slot straight in the same way. The thing I'll need to keep in mind is the camera, the top-down view looks down at 72 degrees rather than straight down, and first person sees everything from the side, so anything I make has to hold up from both. Who knows, maybe the next effects post will actually have some Houdini in it!