Skip to main content

PrismaUI F4 2.1.0

PrismaUI_F4 2.1.0 is the current public framework release line. The public developer SDK for this line is current through IVPrismaUI12.

Runtime architecture​

  • In-process Ultralight 1.4.0
  • Rewritten D3D11 GPU-accelerated presentation path
  • Controlled CPU BitmapSurface fallback when the accelerated path is unavailable or deliberately disabled
  • Retired external browser host/subprocess architecture removed from production
  • PrismaUI_F4.dll owns view lifecycle, JavaScript bridging, input, focus, and frame composition
  • bMeshBinding=0 remains the shipping default

Fallout 4 support​

Desktop 2.1.0 supports:

  • OG 1.10.163
  • AE 1.11.137+ when matching Address Library data is available

The intermediate 1.10.980-1.10.984 Next-Gen runtime line is deliberately rejected.

Fallout 4 VR has a separate provider and validation/release path. Its API contract remains separate from the flat provider's V11/V12 extensions.

API​

The desktop public SDK is one header:

#include "PrismaUI_F4_API.h"

PrismaUI_F4_API.h contains IVPrismaUI1 through IVPrismaUI12. The V1-V10 ABI prefix remains frozen. V11 derives from V10 and adds verified Fallout window-thread dispatch. V12 derives from V11 and adds focused controller-action routing.

Consumers should request and null-check the lowest interface version containing the methods they need.

The current canonical public desktop SDK mirror is pinned to Git blob:

5c03467ce567921e1de86ef89157cd246e07c977

The original 2.1.0 release source and the current API source are tracked separately by prisma-mcp so release provenance is not confused with later SDK/API evolution on the same release line.

The VR header mirror is separately pinned to:

8221eb7bd81694f604b6f188fc8b2c475200dbf0

Header comment errata​

The canonical header preserves a few historical CEF-era terms in comments inside older ABI sections. Those comments are retained because the public mirror is byte-identical to the canonical SDK header. The current backend and method behavior are documented here and in the method reference.

For current behavior:

  • inspector methods are retained for ABI compatibility but are not the normal Ultralight debugging path;
  • GetScrollingPixelSize / SetScrollingPixelSize are compatibility methods rather than a primary Ultralight integration surface;
  • the runtime uses Ultralight, not the retired CEF/subprocess architecture;
  • current rendering uses the accelerated D3D11 path with controlled CPU fallback;
  • V11 engine-affecting callbacks use verified Fallout window-thread dispatch semantics;
  • V12 controller actions are delivered only to the exact focused live view and use the documented prisma-controller-action event.

Web content​

Ultralight is not Chromium. Consumer documentation should not promise the complete Chromium/Electron web platform.

For production 2.1.0 views:

  • ship required JS/CSS/fonts/images locally with the mod;
  • avoid required CDN or remote-font dependencies;
  • keep real network activity in native C++ and relay data to the view through PrismaUI;
  • do not rely on the old browser DevTools workflow;
  • test the exact front-end features your UI uses against Ultralight 1.4.0.

Public developer source of truth​

This Fallout-4-Prisma-UI-Framework repository is the public consumer/developer source of truth for:

  • the canonical desktop V1-V12 SDK mirror;
  • the separate VR SDK mirror;
  • method reference;
  • guides;
  • examples;
  • MCP tooling;
  • website documentation.

The framework implementation and release pipeline are maintained privately. Public users do not need implementation-repository access to compile a consumer plugin or use the MCP server.

Public framework download:

https://www.nexusmods.com/fallout4/mods/105454

The release process retains the desktop ZIP, matching symbols, SHA-256 sums, and release-candidate provenance.