DOOMFIRE#

Test your TTY's might!#

The doom-fire algo can push upwards of 180k a frame - results may vary! It is, to my surprise, a nice TTY stress test.

As a comparison, this is the younger sibling of a node variant ( https://github.com/const-void/DOOM-fire-node ).

INSTALL#

Tested on OX Monterey / M1 w/zig 0.9...

EDIT: Now tested on Artix Linux - links against libc to get the size of the TTY.

EDIT: 2024 - Now tested with Windows - Win32 Compatible, thank you @marler8997!

This means that the program does rely on libc, this shouldn't be a problem.

$ git clone https://github.com/const-void/DOOM-fire-zig/
$ cd DOOM-fire-zig
$ zig build run
...

Results#

• iTerm.app - ok
• kitty.app - great
• Terminal.app - poor -- seems to drop framerates
• VS Code - great
• Warp - great
• Alacritty (artix linux) - great
• Powershell/CMD

Inspiration / Credits#

• Thanks to contributors for your support!

• doom fire - https://github.com/filipedeschamps/doom-fire-algorithm, https://github.com/fabiensanglard/DoomFirePSX/blob/master/flames.html

• color layout - https://en.wikipedia.org/wiki/ANSI_escape_code

• ansi codes - http://xfree86.org/current/ctlseqs.html

• str, zig - https://www.huy.rocks/everyday/01-04-2022-zig-strings-in-5-minutes

• emit - https://zig.news/kristoff/where-is-print-in-zig-57e9

• term sz, zig - https://github.com/jessrud/zbox/blob/master/src/prim.zig

• osx term sz - https://github.com/sindresorhus/macos-term-size/blob/main/term-size.c

• px char - https://github.com/cronvel/terminal-kit