github djules75/OFXR-Bridge 0.2.13.1
OFXR Bridge v0.2.13.1 (V438)

latest releases: 0.2.14.3, 0.2.14.2, 0.2.14.1...
one month ago

A performance and stability release on top of v0.2.12.2. On Virtual
Desktop, games that had higher latency and frame drops since v0.2.12.1 are
back to the way v0.2.11.2 ran them; hangars, menus and loading screens no
longer drop to 60 fps after a hiccup; on SteamVR the short frame-rate dips
that followed a hiccup are now a single repeated frame; MSFS 2024 no longer
stays "loaded but not generating" for a whole session after one rejected
frame; and the VRAM saving introduced in v0.2.10.1 can now be switched off
from the tray, for the cards on which it costs smoothness. Everything else
is v0.2.12.2.

Built on
tig3rmast3r's v0.2.1.

Warning

Pimax headsets: use SteamVR, not Pimax OpenXR. Pimax Play's OpenXR
runtime keeps an extra copy in VRAM of every image it is handed, so OFXR
costs about 1.5 times more on it than on SteamVR, and the copies stay
until the game closes. We have reported it to Pimax so they can fix their
runtime; there is nothing OFXR can do about it in the meantime. Until it is
fixed, run your Pimax through SteamVR with
sboys3's native SteamVR driver
and make SteamVR the active OpenXR runtime (SteamVR → Settings → OpenXR).
This matters most in MSFS 2024, which is already close to the VRAM limit
at Pimax resolutions. Details in the
troubleshooting guide.

🛠️ Not working, or not feeling smoother?

➡️ Read the troubleshooting guide first

It checks in one step whether OFXR is running in your game, then lists the
usual causes and fixes: OpenVR games, running as administrator, the game's
frame rate, frame smoothing in your VR software, and running out of VRAM.

New in v0.2.13.1

Virtual Desktop: the latency and frame drops since v0.2.12.1 are gone

Reported with IL-2 Great Battles on a Quest 3: total latency went from a
steady 47 ms on v0.2.11.2 to 58 to 70 ms on v0.2.12.1 and v0.2.12.2, with
visible frame drops.

OFXR sends Virtual Desktop two frames for every frame the game renders,
the generated one and then the real one, and they have to arrive one
refresh apart. v0.2.12.1 changed how games like IL-2 are run on Virtual
Desktop, and on that path the real frame followed the generated one by
only 3 ms, on every frame. Virtual Desktop then had two frames for one
refresh, which is where the latency and the drops came from.

Games whose frame loop runs on a single thread, which is most of them, now
get the v0.2.11.2 mode back on Virtual Desktop, chosen once when the game
starts and kept for the whole session. The reporter's log on this build
shows the same game running with nine times fewer repeated frames than
on v0.2.11.2, and he reports it "just like 416, even better". Games that
run their frame loop on two threads, such as No Man's Sky, keep the
v0.2.12.1 behaviour, which is the right one for them. Nothing changes on
SteamVR or Pimax OpenXR.

Hangars, menus and loading screens: no more drop to 60 fps

Reported with IL-2 on a Quest 3 through Virtual Desktop at 90 Hz: 60 fps
on OFXR's overlay in the hangar before a flight, 80 on Virtual Desktop's,
and a steady 90 once the flight had loaded. v0.2.11.2 showed 90 in both.

While it generates, OFXR paces the game to half the headset's refresh
rate. Whenever generation had to start over, for example after a hiccup,
the first two frames after the restart were let through unpaced. In a
scene the game renders in a few milliseconds, such as a hangar or a menu,
those two frames and the one after them reached the graphics card almost
together, the card fell behind, the fourth frame could not be captured,
and generation started over again. That is a loop of exactly a tenth of a
second: three frames, a restart, and 60 distinct images a second instead
of 90, for as long as the scene stays light. v0.2.11.2 had the same loop,
for under a second while a flight loaded; its hangar just never fell
into it.

The first frame after a restart is now paced too, so the loop cannot
start. Scenes that take the game longer to render were never affected and
do not change. Verified in MSFS 2024 on Virtual Desktop across four
pause-and-resume cycles: every restart paced, no frame lost.

SteamVR: shorter dips after a hiccup

Reported in MSFS 2024 with 3X Frame Gen at 72 Hz, on a Pimax through
SteamVR: short frame-rate dips of one to three seconds.

After a small hiccup, SteamVR starts showing every frame one refresh late,
and OFXR took about twenty frames to move its timing back into step. Those
twenty frames were the dip. OFXR now makes the move in one go, which costs
a single repeated frame, and if the next hiccup arrives before the
correction has settled it is handled the same way instead of being walked
off again. SteamVR only.

MSFS 2024: no more "loaded but not generating" for the whole session

Reported with MSFS 2024 on a Pimax Crystal Light through SteamVR: OFXR was
running, the FPS number was on screen, but it stayed red and no frames
were generated, from the start of the session to the end.

MSFS 2024 is one of the few games that stamps every frame with a time of
its own, so OFXR can only pair a frame with the game's request for it when
exactly one request is waiting. When SteamVR rejected a single frame, for
example during loading, that frame's request was left waiting for ever,
two requests were pending from then on, and no later frame could be
paired: every one of them was passed through unchanged.

OFXR now drops a request that no frame can match any more, and a rejected
frame now clears its request as an accepted one does, so the next frame
pairs again. A new test covers the shape. Games that stamp their frames
the usual way were never affected.

A tray switch for the VRAM saving: "Lower VRAM (may cause stuttering)"

v0.2.10.1 made OFXR keep one working image per output instead of two,
which saves about half a gigabyte of VRAM at high resolutions. On most
cards it costs nothing. On an AMD RX 9070 XT running AMS2 at the edge of
its GPU budget it showed as stutter that was gone on v0.2.9.1, and that
no timing in the flight log explained; switching the saving off brought
v0.2.9.1's smoothness back on the current version.

The tray menu now has Lower VRAM (may cause stuttering), just after
3X Frame Gen. It is on by default, as before. Untick it if you see
stutter that an older version did not have and you have VRAM to spare.
Unlike the two entries marked "[live change]", it is not applied to a
running game: it takes effect the next time the game starts.

Smaller changes

  • The FPS number no longer alternates between 89 and 90 on a session that
    is delivering every frame. Both ways of counting read one frame short now
    and then; the overlay now shows the refresh rate when the count is within
    2% of it. A real loss of 3% or more still shows.

Known issues

  • Your game has to reach half your headset's refresh rate, with some
    headroom
    (45 fps at 90 Hz, 50 at 100 Hz), for every frame to come out
    evenly. Generating frames costs GPU time too: No Man's Sky ran at 94 fps
    without OFXR on our test machine and reached an even 100 at 100 Hz, but
    113 to 115 at 120 Hz. If your number stops short of the refresh rate,
    choose a lower refresh rate, or lower the per-eye resolution or the
    optical-flow resolution. The
    troubleshooting guide
    has the details.
  • Pausing is not the same as disarming. A paused game still runs through
    OFXR. To rule OFXR out of a problem, disarm it and restart the game.
  • Check your real per-eye resolution. SteamVR's global resolution and a
    per-game resolution multiply: 200% global with 200% for the game gives
    four times the pixels, and OFXR's memory grows with them. The
    troubleshooting guide explains how to read the real value from a flight
    log.
  • SteamVR: turn off Motion Smoothing and "fixed frame rate at half" for
    the game
    in SteamVR's per-application video settings. They fight with
    OFXR's own pacing.
  • No FPS overlay in Vulkan games, so no pause symbol there either. The
    tray entry still shows whether generation is paused.

Installing

Unzip anywhere and run OFXRBridgeTray.exe. It arms the bridge by itself.
Keep OFXRBridgeTray.exe and the ofxr folder together; it holds the OpenXR
layer, its settings and the Vulkan layer. If an earlier version is armed,
disarm it and close its tray first.

Please report results, working or not, on this fork's
GitHub Issues, with an OFXR flight log where you can. To
record one, enable Bridge flight recorder in the tray, reproduce the
problem, then use Open bridge logs. Logs are written under
%LOCALAPPDATA%\OFXR Bridge\RuntimeLayer\v438\. Read the
troubleshooting guide first: most problems are
solved there in a few minutes.

Don't miss a new OFXR-Bridge release

NewReleases is sending notifications on new releases.