TASEmulators / TASEmulators/BizHawk

[Core Port Req.] WinQuake or Chocolate Quake

Open
#4,345 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Request: New core/port/re-port
Dominant language
C#
Stars
2.8k
Forks
468
PR merge metrics
No merged PRs in 30d

Description

Upstream info (WinQuake)
Technical details

Why point out WinQuake and not GLQuake as well, it's the same codebase after all?
Well to make the long point short. GLQuake has drastically incorrect colours/lighting compared to DOS whereas it's correct in WinQuake.

Upstream info (Chocolate Quake)
  • Target platforms: Win/Mac/Tux
  • Source repo
  • Language(s): C
  • Licence: GPL 3.0
Comments

Obviously Chocolate Quake just came out (and still in beta at the time of this request), so this is gun jumping quite a bit, but due to this being the first original experience of Quake since WinQuake without any enhancements I think it's good timing to at least put it in the mind to make the request.

Technical details

Probably the best modern iteration whilst trying to keep that "stock" experience of Quake in a similar vain of goals to that of Chocolate DOOM but with better stability to modern systems.

Merits

We have DSDA-DOOM, which is a nicer port of Chocolate/Crispy DOOM whilst keeping it more of a "stock" experience compared to something else, why not get the next system down the line? Quake.

Quake is a large enough series, where there are Tool-Assisted works that exist, and well if the same applications that are being done to DOOM can be done here, then why not go for it?


Alternative Quake:
vkQuake is a modern Vulkan implementation of Quake. Written in C/C++.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the linked WinQuake, Chocolate Quake, and vkQuake repositories and comparing their platform targets, languages, and rendering approaches. The issue does not name BizHawk entry points or tests; completion would require selecting a target and integrating a working Quake core, with acceptance criteria established first.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, cpp
Domain
game-dev
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.