Bigscreen Beyond#

Kernel Patches#

While the Bigscreen Beyond is well-supported on Linux, you may need to patch the kernel depending on your GPU vendor, and whether you need the BSB2e’s eye-tracking cameras.

  • For Nvidia:
  • For AMD:
  • For eye-tracking cameras:
    • 0001-Change-device-uvc_version-check-on-dwMaxVideoFrameSi.patch - Allows the cameras to work out-of-the-box, without any modifications to Baballonia
    • Note that an update to the eye-tracking firmware is being released (still waiting of 2026-03-03) to address this camera bug. We don’t have steps to update the firmware from within Linux yet, but soon, this patch may no longer be necessary.
💡 Tip

If you have the ability to use Arch Linux’s AUR, you can install linux-bsb, which includes all the necessary patches for any BSB device. See the linux-bsb section on the hardware page for instructions and other details.

💡 Tip

The CachyOS kernel currently includes:

  • bigscreen-beyond-kernel.patch
  • amd-bsb-dsc-fix.patch

Which means it’s sufficient for AMD users who do not use BSB2e eye-tracking cameras. If you fall outside this description, you’ll have to add more patches on top.

Collect your patch file(s) and follow the general guide to kernel patching at the bottom of the hardware page.

Bigscreen Beyond Utility#

You can get the “Bigscreen Beyond Utility” app from Steam working via Proton by following these instructions:

  1. Use a Proton version >=10 that has access to PROTON_ENABLE_HIDRAW env var; Proton Experimental works well.
  2. Set PROTON_ENABLE_HIDRAW=0x35BD/0x0101 %command% as your launch arguments for the Bigscreen Beyond Utility under Properties.
  3. Install the udev rules from the section below.
  4. Download/Copy a Windows install of SteamVR somewhere, then set the “SteamVR path” in the Utility to the location of the Windows install of SteamVR. We won’t actually run this - the Utility requires the path to be set to modify some settings. If you don’t have a Windows version of SteamVR downloaded, you can download it through SteamCMD through the steps below.
⚠️ Warning

Currently, eye camera firmware loading & updates don’t work (see below for info on getting eyetracking working), but HMD firmware updates do work.

Download Windows SteamVR via SteamCMD#

You can easily download the Windows version of SteamVR via SteamCMD:

  1. Download SteamCMD

  2. Run this command somewhere you can create directories (i.e., your home directory):

    mkdir steamvr_win && steamcmd +@ShutdownOnFailedCommand 1 \
  +@sSteamCmdForcePlatformType windows \
  +force_install_dir $(realpath steamvr_win) \
  +login anonymous \
  +app_update 250820 validate \
  +quit

    This will:

    • Create a directory in the current directory named steamvr_win.
    • Download and validate Windows SteamVR into it.
ℹ️ Note

Your home directory is accessible under Z:\home by default in Proton.

Device Mode Swapping#

The Bigscreen Beyond does not support switching modes in the “Bigscreen Beyond Utility” in Linux. Also, in the headset’s default 90 Hz mode, it does not expose other display modes to Monado through Vulkan.

This means that, unfortunately, you will need to use the Bigscreen Beyond Utility in Windows to change the headset to 75 Hz mode before you can use that mode or toggle between the two modes in Linux.

By default, the headset will start up in Monado in the mode you set it to in the utility in Windows, whether 75 Hz or 90 Hz. If you’d like to use one mode all the time, the easiest solution is to set the mode in Windows and leave it there.

Determining Current and Supported Display Modes#

Run this command:

STEAMVR_LH_ENABLE=true XRT_COMPOSITOR_LOG=debug XRT_COMPOSITOR_PRINT_MODES=true monado-service 2>&1 >/dev/null | grep -E '(choose_best_vk_mode_auto|get_primary_display_mode)'

If you see output that includes this, your headset is configured to select modes in Linux:

DEBUG [choose_best_vk_mode_auto] Available Vk direct mode 0: 5088x2544@75.00
DEBUG [choose_best_vk_mode_auto] Available Vk direct mode 1: 3840x1920@90.00

Also, you will always see a line like this, indicating which mode was chosen and information about it:

DEBUG [get_primary_display_mode] found display mode 3840x1920@90.00

Changing Modes#

If your supported display modes list both modes, you can set the environment variable XRT_COMPOSITOR_DESIRED_MODE to the index of the one you want use, either in Envision settings or in the environment before starting Monado. For example, if mode 1 is 90 Hz based on the output from the supported modes command, XRT_COMPOSITOR_DESIRED_MODE=1 will cause Monado to select 90 Hz when starting up.

If your supported display modes doesn’t list both modes, unfortunately you will have to run the Bigscreen Beyond Utility in Windows and select the 75 Hz mode, then boot into Linux to be able to use other modes.

Adjusting Software IPD#

The Bigscreen Beyond Utility’s IPD adjustment does not work under wine/Proton.

If you have a windows installation, the easiest way to adjust the value is to boot into that & set it from the Utility.

If you use Monado, you can override the headset’s default IPD of 64mm by setting the environment variable LH_OVERRIDE_IPD_MM to some value (e.g. 64). This should be set such that the monado-service process can see it — if you use Envision, edit your profile and add it under Environment Variables.

Via lighthouse_console#

Very advanced users may use the lighthouse_console CLI program in ~/.local/share/Steam/steamapps/common/SteamVR/tools/lighthouse/bin/linux64/ to directly update the headset config with their desired IPD. Exact instructions are not included here on purpose.

Make sure to keep a local & offsite backup of your config before editing it if you try this.

🛑 Caution

Do not attempt this unless you understand the process & risks, which may include sending your headset back to Bigscreen for repairs.

udev Rules#

In most use-cases, you will need udev rules for full functionality.

The following script will:

  • Create a udev rules file, setting their GROUP fields to one your user is in so you have access to the devices
  • Tell the udev daemon to apply the rules

Other notes about this script:

  • This purposefully avoids using TAG+="uaccess", since it is undocumented and unexpectedly picky about the exact number in the filename. It is easier to just pick a group.
  • On regular distros, run this script as your regular user, not root.
export udev_group=$(groups | tr ' ' '\n' | grep -E "$(whoami)"'|wheel|sudo|adm|admin|video|plugdev' | head -n 1)
bash -c 'sudo tee "/etc/udev/rules.d/99-bigscreen-beyond.rules" > /dev/null <<EOF
# Bigscreen Beyond
KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="35bd", ATTRS{idProduct}=="0101", MODE="0660", GROUP="${udev_group}"
# Bigscreen Bigeye
KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="35bd", ATTRS{idProduct}=="0202", MODE="0660", GROUP="${udev_group}"
# Bigscreen Beyond Audio Strap
KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="35bd", ATTRS{idProduct}=="0105", MODE="0660", GROUP="${udev_group}"
# Bigscreen Beyond Firmware Mode?
KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="35bd", ATTRS{idProduct}=="4004", MODE="0660", GROUP="${udev_group}"
EOF'

sudo udevadm control --reload && sudo udevadm trigger

If your headset is already plugged in, disconnect & reconnect it to force the rules to fire.

On NixOS, use the following option, where you replace the PLACEHOLDER with the first group your user has from this list (You can list your groups with the groups command in the terminal): wheel, sudo, adm, admin, video, plugdev

services.udev.extraRules = ''
  # Bigscreen Beyond
  KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="35bd", ATTRS{idProduct}=="0101", MODE="0660", GROUP="PLACEHOLDER"
  # Bigscreen Bigeye
  KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="35bd", ATTRS{idProduct}=="0202", MODE="0660", GROUP="PLACEHOLDER"
  # Bigscreen Beyond Audio Strap
  KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="35bd", ATTRS{idProduct}=="0105", MODE="0660", GROUP="PLACEHOLDER"
  # Bigscreen Beyond Firmware Mode?
  KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="35bd", ATTRS{idProduct}=="4004", MODE="0660", GROUP="PLACEHOLDER"
'';

For some even more special use cases (such as using with libsurvive), you may need a more permissive udev rule. If you do, use the following udev rule. You will also need to be part of the wheel group.

KERNEL=="hidraw*", SUBSYSTEM=="hidraw", ATTRS{idVendor}=="35bd", MODE="0660", GROUP="wheel"
SUBSYSTEM=="usb", ATTRS{idVendor}=="35bd", MODE="0660", GROUP="wheel"

Bigscreen Beyond 2e Eyetracking#

For details on setting up eye tracking, please see the Baballonia Eye/Face Tracking guide, but you will need to use BSB2e-specific forks, see below.

The full stack can be pictured as such:

graph TB
   E[Bigscreen Beyond 2e]-->F
   F[Bigscreen Bigeye]-->B
   E-->M[Monado]
   M-->X[xrizer]
   X-->D
   B[Baballonia.Desktop/bsb2e_linux] --> C[VRCFT.Avalonia] --> D[VRChat/etc.]
   subgraph Linux Native
   B
   C
   E
   F
   M
   X
   end
   subgraph Proton/Wine
   D
   end

You’ll have better luck currently with the bsb2e_linux fork of Baballonia and its README. It uses libuvc to get around the v4l issues we have with the Bigeye cameras.

NixOS has not yet packaged Baballonia (see nixpkgs-xr PR #532), but you can still run it with nix run 'git+https://github.com/leon-costa/Baballonia?submodules=1#default'.

Baballonia.Desktop can be given the Bigscreen Bigeye (video0) endpoints for each camera if you’re using the bsb2e_linux fork. You’ll need to adjust cropping and brightness for the cameras as necessary, but it should allow you to easily select the whole left/right areas automatically for the Bigeye in particular.