quakespasm VS box64

Quakespasm https://github.com/sezero/quakespasm

Forget the GOG version and grab a modern source port like Quakespasm: https://sourceforge.net/projects/quakespasm/

I wouldn't say you absolutely need to get a new PC. You could probably try using the QuakeSpasm engine. Pretty much any modern PC can run Quake, the "remaster" just has much higher system requirements than usual.

Can you elaborate on what you understand the correct location to be? Does this mean you have placed your music folder inside of your id1 directory? Are your music files named correctly, e.g. track02.[ogg,mp3,wav, or flac]~track11.[ogg,mp3,wav, or flac]? Have you looked at the documentation on music support in Quakespasm?

Get Quakespasm and drop the files in your Steam/steamapps/common/quake/rerelease folder, and use that executable to play the game. It'll work on older computers.

Yesterday a new update to Quakespasm came out. You can get it here.

Grab at sourceforge.

( I have sucessfully integrated a .net rewrite (https://github.com/Memorix101/SharpQuake) of the quake engine into unity and I've seen someone else do it for UE4. I'm working on PLUQ, which is a nanomsg nng interface integrated into an modern Quake engine (https://github.com/sezero/quakespasm, https://github.com/mdeguzis/ftequake, ...) that on game/level load provides geometry, textures, entities, ... and at runtime a bidirectional channel for the data (enity positions and inputs) needed to render and steer the game from a connected client. The connected client can e.g. be the rendering and input part of the original engine or something Unity3D, Unreal, Godot, ... based. I hope to open up Quake for experimentation using non GPL engines with this...)

I used QuakeSpasm.

In the video, they mentioned they can't run steam on RISC-V because box64 doesn't support 32bit apps. In the README of box64, it is mentioned:

I see it can do more now, already tried some stuff. But see it is now more mature than months ago. Will try factorio again https://github.com/ptitSeb/box64/issues/665

Also, in the discussions of box64 is this thread: https://github.com/ptitSeb/box64/discussions/524 My guess is that you have to install both box64 and box86, the latest mesa drivers with vulkan support. And then try to launch the game with proton. There is also this issue that shows factorio running on a Rock 5B: https://github.com/ptitSeb/box86-compatibility-list/issues/284

In Box64, which is an emulator+JIT recompiler, and thus likely pretty slow?

macOS runs x64 executables just fine through Rosetta so I don't see why Wine couldn't make use of that hardware acceleration.

It's also possible to only simulate the entrypoints through Rosetta and then execute native aarch64 code from there. On Linux https://github.com/ptitSeb/box64 does exactly that, for example. However, with the performance Apple has been able to squeeze out of Rosetta, I'm not sure of that workaround is even necessary.

Recently, I got a server from Oracle Cloud, having 4 cores and 24GB of RAM. Then, using a software called Box86 and its 64 bit version called Box64, I succeeded in running Factorio! Unfortunately, 1.1.80 ran at 3 UPS! I went through each major version, testing each individual one down to 0.12. Here are my results!

You could try https://github.com/ptitSeb/box86 and https://github.com/ptitSeb/box64/ , I believe they allow you to emulate x86_64 on aarch64, though I have no experience with them, so cannot say for sure.

git clone https://github.com/ptitSeb/box64.git

If you have time and patience take a look at box86 and box64. These are basically like translation layers that allow x86/x86_64 applications to run on ARM. I personally haven't use them yet, so I can't provide a guide or vouch for game compatibilities. But by the look of the progress made by them so far it looks promising.

You can follow progress of this on https://github.com/ptitSeb/box64/issues/635