Files
OpenAssetTools/src/ModMan
moandJan Laupetin 9f49e0e31c feat: QOS (007: Quantum of Solace) support (#894)
* feat: QOS (007: Quantum of Solace) support

* feat: add qos localize loader

* feat: add qos stringtable loader

* chore: comment about official zones

* fix: add qos gfximage runtime fields

* chore: remove useless dev time comments

* fix: remove all `static_asserts`s from asset headers causing build fail on x64

* chore: change union ordering of qos `entryInternalData`

* chore: move qos asset type enum to qos.h

* fix: qos and t4 xsurface index buffer

* chore: implement qos MaterialInfo struct

* chore: adjust some gfxworld struct members

* chore: implement qos PhysPreset and PhysConstraints

* chore: fix and adjust slight inconsistencies with qos zone code

* chore: reorder qos ZoneCode.lua entries in order of asset type enum

* chore: remove asset types that are not actual asset types in zones

* chore: check common asset arrays with static_assert

* chore: rename qos assets

* chore: reorder qos in templates to be in alphabetical order

* chore: use function for CopyMipLevel in Dx9TextureLoader

* chore: use templates for qos MapEntsDumper

* chore: add missing braces in XModelToCommonConverter

* chore: add generic way to peek at zone data

* Qos does not use a classic ZoneHeader so code needs to be more generic

* fix: do not use raw_byte and raw_uint typedefs for qos

* fix: not being able to write clipmapmp

* chore: additional research on qos vertex property and stuff

---------

Co-authored-by: Jan Laupetin <[email protected]>
2026-08-05 00:32:23 +02:00
..
2026-06-20 20:35:47 +02:00
2026-01-27 23:49:37 +01:00
2026-06-18 18:52:52 +02:00
2025-10-17 19:20:25 +01:00
2025-10-11 19:04:47 +01:00

ModMan

ModMan is the experimental GUI for OpenAssetTools.

How do I test it

Currently ModMan is not compiled by default. To enable it, you have to generate with the appropriate premake5 flag:

# On Windows
./generate.bat --modman

# On Linux
./generate.sh --modman

Before building the C++ solution, the ui has to be built. This will require NodeJS to be installed on your machine.

# Download dependencies
npm install

# Build frontend
npm run build

# Optional: Dev Server for UI development
npm run dev

How does it work

ModMan uses webwindowed for providing a web frontend as a native application. Unlike frameworks like Electron this does not ship a browser engine alongside it, but instead relies on browser APIs of your OS. On Windows, this makes use of WebView2, on Linux it uses WebKitGTK.

This adds the following dependencies:

  • Windows: An up-to-date OS with at the very least Windows10. The WebView2 library for development is downloaded by premake.
  • Linux: Developing and using ModMan requires the following dependencies to be installed: gtk4 webkitgtk-6.0