I imagined a space game based on a bit similar approach but the caveat is "technology to make stuff deep space radiation resistant also limited the available compute", and the player has capability to

So your airlocks, space station and ship subsystems and similar devices would run just on small microcontroller sized chips (8-64kB sized ones, with slow clocks) and player that invested in that given skillset could essentially hack them and modify or replace the programming, and have access to a bunch of languages, from assembler, thru rust to something more high level/easier to use like BASIC/MicroPython.

They could also acquire disassemblers, the basic ones would just give them assembly code (which might be enough if they want to just re-program a lock), the advanced ones would also get actual high level source code (just a bit of smoke and mirrors so player doesn't have to stare at assembler or build code from scratch every time). And basically play hacker but on actually running systems, OR re-tune their ship's engines (it could even go to fun stuff like "there are 5 models of this engine, all just software locked into given power level", akin to real life car ECU tuning).

There would be bigger systems, but they would be bulky from shielding so it would be often mainframe-like system of station having one big core computer with a bunch of dumb terminals, that player could also fuck around with, like installing a password sniffer. Or having it trigger something when certain character accessess it.

A few things about our RISC-V 64-bit emulator. Please forgive me, if I make some mistakes, but I'm not the expert on this.

First, PasRISCV not only emulates userspace (RV64GC usermode), but a complete, modern machine (SMP/MultiHART, RV64, full RVA23.1 including Hypervisor, Crypto, Vector stuff, etc.), which is capable of booting a normal Linux kernel (either using direct OpenSBI -> kernel boot, but currently everything has to be in the initrd then), or using U-Boot (OpenSBI -> U-Boot -> kernel).

The emulator uses a hybrid of interpreter with a tracing JIT. Currently, the JIT is limited to host x86-64. About 99% of all instructions and are supported by the JIT. For example, the host FPU is passed through to the guest. But PasRISCV also supports an optional stricter FPU mode, where with soft floats and interpreter only, because IEEE754-2008 has specific rules, that don't exist on the x86 architecture.

Disk images are provided either using VirtIO-Block or NVMe via PCIe. We can either use disks in normal read-write mode, or also in read-only mode. This allows us to have a root partition, that we can overwrite with game updates, and have a user partition, where custom player stuff is stored. We also can mount host dirs as external paths/mounts over VirtIO-9P or VirtIO-FS, which is especially useful for development because this allows us to compile guest tools directly on the host system.

To display graphics on our virtual game screen(s), we currently use a framebuffer device (via SimpleFB with a custom MMIO framebuffer). But PasRISCV also supports other graphics "adapters", such as VirtIO GPU (with EDID, 2D, and experimental 3D/virgl support), or using PCI emulation (bochs-drm and Cirrus-DRM). We have some custom shaders modifying the framebuffer output, so that we can add some retro FX like scanlines, phosphor glow, etc.

The emulator also has audio using emulated CMI8738 and FM801 cards (both with OPL2/3 support), as well as Intel HDA and VirtIO-Sound. Our little space game (Space Prowler) inside SEEDS has a title tune which is made using PCM+OPL3. I coded a small tracker, which runs in a plain Linux console, so I can even compose inside our game on its 80×50 (640×400px) framebuffer console, albeit it's a bit cumbersome. I'll release the tracker as FOSS when we have a bit more spare time, as I need to make it a bit more user-friendly.

We use vsock (Linux virtual sockets) to interface with the game outside of the emulated machine. We use a small serialization format (basically something similar to binary JSON) to communicate bi-directionally, like you'd expect over normal network. We have a small priority queue and message referencing for urgent and request-response communication. For example, the client to display a planet sphere on the in-game computer can ask for updated positions of e.g. terrain or all animals.

The emulator embeds its own disassembler and debugger, and also can act as gdb server, which means you can use your favourite debugging tools, as long as it speaks gdb's server protocol.

It has real network support through a Slirp-like usermode NAT (without using external libs) which supports IPv4 and IPv6. We can run APK's update and install directly on the emulated machine.

Our game uses a slightly modified Alpine Linux 3.23 and custom kernel build, but a recent stock Alpine image also runs without problems.

PasRISCV is licensed under the permissive zlib license.

If you have any questions, I'm sure BeRo is happy to answer questions with far more detail than I could. :)

https://en.wikipedia.org/wiki/0x10c

Cool, and quite reminiscent of 0x10c: https://en.wikipedia.org/wiki/0x10c

> Object Pascal

Free Pascal or Delphi? I tried FP a while back and felt that the language had really stagnated (e.g., variables can only be declared at the top of scope like C89).

This is absolutely wonderful and I can't wait to play it!

Selfish question -- will you be releasing on GOG or Itch?

Do you have a blog post about this? The link is to the home page and doesn't mention anything! Sounds super interesting but the landing page reads like survivalcraft in space #1001

[flagged]

> to change and automate your world.

In what ways?

I saw this on the steam page:

> our entirely in-house game engine PasVulkan, which powers SEEDS, as well as our RISC-V emulator PasRISCV, are both Free and Open Source Software (FOSS)

Can you link to PasVulkan and PasRISCV please?