Lemmings Forums
Lix => Lix Main => Topic started by: Simon on August 10, 2020, 07:53:35 PM
-
In 2018, I wrote:
Skill blueprints: Demo video of skill blueprints (http://www.lixgame.com/etc/skill-blueprints-2018-10-31.mp4). It looks sophisticated, but it's not in releasable quality yet:
- This is comparatively expensive to compute. I allocate an extra level-sized VRAM bitmap for the blueprints. Even though that's permanent, I have to target/untarget that at least once per drawing. It dents the performance.
- It doesn't cover all skills yet: It doesn't draw any terrain changes for cubers or ploders.
- It draws the removers' blueprints even where there is already air. I'd prefer to only draw it on terrain. That requires changes to some low-level algorithms.
- I like the previewed pose of the lix after the skill has run out. But stopped terrain removers get hidden behind the blueprint.
I'd like to improve it it before I release. I could hide it behind a disabled-by-default option, but hmmm, it feels very very beta even for that. Still, I'm happy to have made some progress here.
August 2020 discussion about this old D Lix branch in NL Customisable Fast-Forward Speed (https://www.lemmingsforums.net/index.php?topic=5009.msg84360#msg84360):
Lix doesn't have skill shadows yet, they're elaborate to implement both nicely and fast. I have a crude version in a 2018 branch. It's possible to release that, but I feel like I should polish it more. I haven't done it in two years.
These look pretty good to be honest, but I can see that more refined versions are possible. For example, making it so the destructive blueprint only appears on the terrain that it will affect rather than the entire mask being shown.
Whatever you do, be sure to make these optional! I don't play Lix much at the mo but I keep meaning to - I'll likely make my next LP series Lix-based. It would be great to play through a few more levels and finally get around to reviewing the editor!
Yes, the main disadvantage is that the remover blueprints paint their entire mask, even over air. It's possible to improve that. I already have intricate/expensive per-pixel VRAM drawing for the real terrain removing; ideally, the blueprints work the same, even if expensive.
The blueprints allocated an extra level-sized VRAM bitmap. I'd like to omit that, too. Haven't thought about it in over a year. But maybe it's not that bad after all.
Undo in the editor is still in the works, but not releasable yet. Nonetheless, looking forward to your feedback!
-- Simon
-
I could hide it behind a disabled-by-default option, but hmmm, it feels very very beta even for that.
You could write at the option that it's beta, e.g. 'enable skill shadows (beta)' or similiar.