A level playthrough

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Andrew Davie

Slowly removing glitches. Here's a full level gameplay.

The on-the-run pickup as you go past the electric fence is pretty cool. Some sections have this at the only way to get past the fence (e.g., at 0:28). Gotta be careful there's not anything above the pickup object, though, or you get crushed.


Andrew Davie

Another playthrough, with the swipes operational. Tightening up the timing.
Up till now I've had a weird crash (overtime). Fingers crossed... haven't seen it for a few runs.


Andrew Davie

Yet another playthrough - planet intermission screens now stable, too!
There was an incredibly obscure bug found in this round -- I would modify the planet height starting point, and the *copyright* kernel would crash.  Only the planet code had not been called at that point. In other words, "spooky action at a distance".  If I disabled the '-flto' flag in the link/build (which is an optimisation flag) then all worked OK.  In fact if I modified anything inside the planet code, then the copyright (or the skull, or the detectkernel) would crash. Bizarre!

Eventually tracked down to a warning in the compile -- the drawGridPreview (on the menu screen) iterated 11 lines instead of 10. I'd ignored this warning as a "fix later", but in fact - even though the code was never called - it was enough to allow the optimiser to effectively break things with its code reordering.  Lesson learned - one I already knew - treat warnings as errors. But this was the absolute weirdest one I've ever seen.

Fixed the code in question - even though it *never ran* -- and everything is now working properly.


Video shows a long playthrough with many systems functional.


Andrew Davie

#3
Another playthrough. Lots of updates to the timing. Noticeable slowdown in some (very complex) areas where a lot is happening. But not too bad - and in any case I won't have screens that complex anyway.  One crash observed. It's a time overflow issue - will hunt it down eventually.  The new auto-timing code is working very effectively - not many time overflows in this one. Very few, actually. Well, maybe none?  In any case, it will only get better.