Skip to content

OFXR Bridge v0.2.12.2 (V427)

Choose a tag to compare

@djules75 djules75 released this 05 Oct 16:19
· 130 commits to main since this release

A patch release: one fix on top of v0.2.12.1. It removes a flicker in
the left eye only, reported in MSFS 2024 with 3X Frame Gen. Everything else
is v0.2.12.1, and its notes are repeated below.

v0.2.12.1 was a feature release: you can pause and resume frame generation
while you play, from the tray or with a key you choose; the flight recorder
can be switched on in a game that is already running; and Virtual Desktop
and Pimax OpenXR sessions behave the same way every time. It also removed a
black screen some games showed while loading, and an error that could stop
OFXR from starting again after you had turned it off.

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.12.2

No more flickering in the left eye

In MSFS 2024 with 3X Frame Gen, some players saw the left eye flicker or
shimmer while the right eye was fine. OFXR was sometimes working from a
picture of the left eye that was one frame old. It now takes both eyes'
pictures when the game has finished drawing the frame. Two players who had
the flicker confirmed it is gone. D3D12 games only; nothing changes for the
others.

New features in v0.2.12.1

Pause and resume frame generation while you play

The tray menu has a new entry, Pause frame generation. It switches the
generated frames off in the game you are playing, and Resume frame
generation
switches them back on. No restart, so you can compare with and
without OFXR in the same scene.

While paused:

  • the tray entry reads Resume frame generation, with an orange pause
    symbol beside it;
  • the FPS number in the headset shows the same symbol (two vertical bars).

A paused game still runs through OFXR: it only stops making extra frames.
If you want to check whether a problem comes from OFXR, disarm it and
restart the game, as before. Every time you arm OFXR, it starts resumed.

A key to pause and resume, and you choose it

Ctrl + Alt + F7 pauses and resumes without leaving the game.

To change it, select Current key binding in the tray menu, press the key
or keys you want, and confirm:

  • any key works, with or without Ctrl, Alt and Shift;
  • Default goes back to Ctrl + Alt + F7, and No key turns it off;
  • a combination another program already uses is refused, and the window says
    so.

The game still sees the key press, so pick keys your game and its mods do
not use. A key used on its own, without Ctrl, Alt or Shift, stops working in
every other program while OFXR is armed.

The flight recorder can be switched on while you play

Bridge flight recorder used to work only if it was ticked before the
game started. You can now tick it in the middle of a session, right when a
problem shows up: recording starts within a moment, and unticking it closes
the file.

A log started this way still begins with what OFXR noted when the game
started (your runtime, the resolution, the game's graphics API), so it can
be read like any other. The game hitches once when you switch the recorder
on or off.

A long session's log also keeps that start-up information now. Before, it
was lost once the log filled up and started over.

The same result every time on Virtual Desktop and Pimax OpenXR

OFXR has two ways of sending frames to the headset. On Virtual Desktop and
Pimax OpenXR it could switch from one to the other in the middle of a
session, when the game stalled for a moment, and stay there. In some games
that made the rest of the session choppy, and whether it happened depended
on luck.

OFXR now chooses once, from how the game itself is built, and keeps that
choice for the whole session. A given game runs the same way every time.
Nothing changes on SteamVR.

Bug fixes in v0.2.12.1

No more black screen while a game loads

Some games send the headset one unusual frame while they load, for example
a loading screen that is not quite ready yet. Your VR software rejects that
one frame, and without OFXR the game simply carries on.

With OFXR, that single rejected frame made OFXR stop showing anything for
the rest of the session: the game kept running and you could hear it, but
the headset stayed black until you restarted the game. It was reported with
Alien: Rogue Incursion VR on Virtual Desktop.

OFXR now skips that one frame and keeps going, just as the game would on its
own.

OFXR starts again after you turn it off

If you turned OFXR off and back on, or closed and reopened the tray, while a
game or another VR program was still running, the tray could refuse to start
with an error like:

Installing the runtime layer failed (32)

or

Installing the Vulkan layer failed (32)

The only way out was to close every VR program, or restart the PC. This
happened in any game, not only Vulkan ones.

The tray now starts normally in that situation. No need to restart anything.

Smaller changes

  • Two flight logs started within the same second no longer overwrite each
    other.
  • The tray's About box and the README now link to this project's page,
    where updates and bug reports belong.
  • The About box now credits tig3rmast3r as the original creator of OFXR,
    and Djules as the maintainer of the 0.2.x versions, with a Ko-fi link for
    each if you'd like to support them.
  • Donate in the tray menu now offers both: tig3rmast3r, creator of OFXR,
    and Djules, maintainer of 0.2.x.

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\v427\. Read the
troubleshooting guide first: most problems are
solved there in a few minutes.