wasm4 VS PixelVision8

Related:

A fast Pascal (Delphi) WebAssembly interpreter:

https://github.com/marat1961/wasm

WASM-4:

https://github.com/aduros/wasm4

Curated list of awesome things regarding WebAssembly (wasm) ecosystem:

https://github.com/mbasso/awesome-wasm

Also, it would be nice if there was a WASM (soft) CPU for QEMU, which (if it existed!) would go here:

https://github.com/qemu/qemu/tree/master/target

WASM4 seems to be a fantasy console with good docs that can run zig code in the browser, using the wasm target: https://github.com/aduros/wasm4/blob/main/cli/assets/templates/zig/build.zig

About assembly language, pure WAT (WebAssembly's text format) is an option if you're into that. Check out this example source (play)

Hi, could you please file a bug report? https://github.com/aduros/wasm4/issues

Posting here because there's a Rust template but no actual Rust games yet. Could be fun to see one.

By the way, the memory corruption issue was also recently reported in Go (which uses similar linker flags to Rust) https://github.com/aduros/wasm4/issues/33

Sprites in Power Vision 8 are all 8x8 pixels in size, when your game starts up the file "sprites.png" is loaded and chopped up in to 8x8 images. Each of these images is then loaded into the memory of the sprite chip until it runs out of space. Each sprite is given an index number at load time (starting from 0) and you can use that index to fetch a particular sprite.

We don't talk enough about how much it "costs" to work on large open-source projects by yourself. I summed up my experiences building Pixel Vision 8 for the past 6 years in "The Dark Side of Supporting an Open-Source Project" on u/hashnode - https://jessefreeman.hashnode.dev/the-dark-side-of-supporting-an-open-source-project

Space Station 8 is a Micro Platformer created in 72 hours for Ludum Dare 49 based on a game I used to play on my original Macintosh called Spacestation Pheta. Space Station 8 is also heavily inspired by Bitsy and my Fantasy Console, Pixel Vision 8, which I used to create the game.

I have been working on my game engine, Pixel Vision 8, for the better part of 6 years now. One of the challenges of working on any sizeable open source project is writing all the documentation and tutorials. I've always been fascinated with designing automated build systems, and it occurred to me that I could create a tool to help me streamline this entire process. The idea was straightforward, could I analyze a code file and break it down into individual steps?