Skip to content

Antichamber VR 1.2.0

Choose a tag to compare

@hernanrodeblas-tech hernanrodeblas-tech released this 13 Nov 10:48
· 2 commits to main since this release

Antichamber VR 1.2 – up to 90 fps standalone on the Steam Frame.

Steam Frame performance (full write-up in the README):

  • Render thread on the fast core (RenderThreadCore=7, CpuCores=2-7). On the Frame the game is limited by one thread, the engine's render thread, running under x86 emulation. The Snapdragon's core 7 is much faster than the others; pinning the render thread to it takes light rooms from 45 to 80–90 fps at 90 Hz (average ~51 fps over a long session). The idea comes from DDD's Deadlock Steam Frame patch. The headset runs a bit warmer.
  • Per-eye frustum (AsymmetricFrustum). Each eye renders only its own field of view instead of a symmetric square that SteamVR cropped by ~28%: fewer pixels and fewer objects to draw (render thread 14–18 → 9–16 ms). Mirrors, portals, the aim dot, the block outline and the linework use the same per-eye projection. Off by default on PC (launcher: Advanced → Performance → Per-eye frustum).
  • Both are on in the new Steam Frame preset (SteamFrame/antichamber_vr.ini).

Fixes

  • Choosing a resolution on the in-game options wall no longer leaves a small image in a corner with a frozen frame around it (#3): the mod restores the headset resolution as soon as the game changes it.

Diagnostics: per-thread CPU time in the log, DebugEvents (window focus, SteamVR dashboard events, audio output changes) for #1 and #2, DebugProjection, OcclusionQueries.

Steam Frame users: copy the new SteamFrame/antichamber_vr.ini over Binaries/Win32/antichamber_vr.ini. Setup steps are unchanged: see Steam Frame (standalone).


Español: en las Steam Frame sin PC, el hilo de render del motor (el que limita) se fija ahora al núcleo rápido del procesador y cada ojo dibuja solo su propio campo de visión: las salas ligeras llegan a 80–90 fps a 90 Hz. Copia el nuevo SteamFrame/antichamber_vr.ini. También se arregla el cambio de resolución desde la pared de opciones (#3). Todos los detalles, en el README.