droogie/bbhost

Maintainer? Show your league in your README

Card: your league's emblem, from Copper to Legendary

[![bestofgithub](https://bestofgithub.dev/badge/droogie/bbhost.svg?style=card)](https://bestofgithub.dev/repo/droogie/bbhost)

Flat: fits beside your other badges

[![bestofgithub](https://bestofgithub.dev/badge/droogie/bbhost.svg)](https://bestofgithub.dev/repo/droogie/bbhost)

Loading README…

Part	State
Game logic (CPU)	the game's own code, running natively
System libraries	reimplemented by bbhost: all 660 named imports the game binds
Window, input, audio, movies, saves	native (SDL3, Vulkan, FFmpeg, LibAtrac9)
Online	native sockets and HTTP against a private server; peer-to-peer UDP with NAT traversal
Draws	native: each draw is built from the engine's graphics objects; the command buffer only marks its place in the stream
Post-processing (YEBIS)	native: every stage's resources built by bbhost
Tessellation	native: the host GPU's own tessellation stages, all three stages lifted; the game's mesh hulls draw as one native pipeline, without the PS4's on-chip ring
Shaders	decompiled ("lifted") from GCN to typed, structured SPIR-V when the game creates them, every stage: 3,206 of the 3,209 pixel shader programs, all the vertex, tessellation and compute programs in the game's bundles, and the GPU particles' geometry shaders; 100% of the draws and dispatches at the 12 measured places (see docs/rendering.md). The lifts are printed as HLSL and compiled with DXC on the player's PC, behind the game; the few programs the lifter refuses are translated by bbhost's GCN compiler
Frame pacing	native: the game's frame-time manager runs as bbhost source; 30, 60, 90, 120 or uncapped, with the game's per-frame steps following real time
Compute dispatches, clears, copies	native: built from the engine's calls, like the draws; the command processor puts them in order from host command lists recorded per command buffer
Labels and fences	still emulated: recorded by the command processor and written by the host once their submission has run (GPU fills on Windows for now); GPU particle counters are kept natively, as per-buffer counters
Textures and buffers	the game's tiled textures are detiled on the GPU; textures belong to the engine's own objects (GX's, YEBIS's, Scaleform's), and vertex and index data is told by GX's calls; only memory no call tells of is tracked by watching the game's writes

droogie/bbhost

bbhost

Why not emulation

Features

Status

Getting started

Building

Documentation

Project layout

Roadmap

License

Acknowledgements


	Any resolution, ultrawide included. 21:9 and 32:9 with a wider field of view and the HUD where it belongs, and the resolution can be changed while playing. FSR 1 upscaling for slower GPUs.
	Settings in the game's own menus. The System menu gains PC Settings, PC Graphics, PC Effects, PC Controls, PC Camera and Key Bindings, drawn in the game's style: anti-aliasing, ambient occlusion, shadow distance, fog, motion blur, field of view, frame rate and more.