spoopyghosty0--frameport

0 Fork 0

mirror of https://github.com/spoopyghosty0/frameport.git synced 2026-10-16 20:01:52 +02:00

Files

T

spoopyghosty0 d2885ea26a PC builds (AXRB): runtime-independent APK fixes, FrameBridge and the telemetry patch

pc_selection keeps the APK fixes marked on_pc (Meta library stubs, Unreal/Unity
gates, manifest fixes; vk_sanitize, vrapi_bridge, unity_tls_key_pool and
eos_keychain_loop as experimental), FrameBridge with its settings except the
Frame-only ones (sync_guard, focus_hold, controller_models, GL shim/Zink keys;
focus_hold=0 written), and, given the analysis, OVRPort's Meta XR Audio
telemetry patch for x86_64 translation (Patch.pc_detect). PC builds with
FrameBridge turn extractNativeLibs on so libframe_settings.so is readable.
Steam Frame builds are unchanged.

2026-10-15 19:28:38 -04:00

showcase

Showcase: the fake Monitor history gets exact 1 s steps (smoothed numbers differed between renders on slow runners)

2026-10-14 20:47:31 -04:00

catalog_from_issue.py

BlazeRush works (GitHub #57 , from Klownicle's guide; headset check pending): frame.blazerush (1.0.349 only, fingerprint + words checked: avatar wait NOP, avatar renderer RET, shader cache cache/br_shader_v1), device.config_sync (agent v78: saved resolution in user_config.xml from the runtime eye size x scale at finalize, settings changes and before each start), catalog recipe with the GL shim fixes and scale 1.7, triage vrapi-fov-before-tracking / gl-integer-attribs

2026-10-10 23:18:42 -04:00

compat_list.py

Docs: shorter, consistent copy

2026-10-10 16:34:19 -04:00

dev_version.py

Dev builds on demand: CI "Run workflow" (dev ticked, optional notes for testers) publishes the rolling dev pre-release with version <next patch>.dev<run>; Settings → Updates → "Install the latest dev build…" installs it like an update (automatic checks still ignore it; the next release is offered normally)