Black Screen

We have noticed that displaying certain text on the screen can lead to black screen problems. For example, running the stats FPS command to show the FPS or having messages like "Lighting needs to be rebuilt" can cause the stream to display a black screen.

To address the issue with the stats FPS command, we recommend removing the FPS counter. If you need to see your FPS, it can be manually calculated and added to a widget. If the FPS counter is necessary, adding a delay before running the command can help. A 5-second delay has been tested and found effective, whereas shorter delays may not work.

For on-screen error messages like unbuilt lighting notifications, please have the developer resolve these errors to prevent black screen issues.

For more details on the impact of the FPS counter, please refer to the "Jittery Experience" section below.

Jittery Experience

To improve your experience, ensure that nothing is printed on the VR screen. A common cause of jitterness is the default UE FPS display being turned on. Disabling this display can help resolve the issue.

Jagged Edges

If you notice that the edges of meshes appear jagged, especially when objects are far away or viewed at an angle, it might be due to Anti-Aliasing being turned off. To improve the appearance, you can enable Anti-Aliasing by going to Project Settings, Engine -> Rendering -> Default Settings -> Anti-Aliasing Method.

Important:  If you choose the Multisample Anti-Aliasing (MSAA) method, you will also need to enable  Forward Shading. This setting can be found under  Engine -> Rendering -> Forward Renderer -> Forward Shading.

For more information, please refer to the Anti-Aliasing and Upscaling in Unreal Engine section of the Unreal Engine documentation.

Low Resolution Issues

If your models appear to be in low resolution, it might be due to the Default Screen Percentage being set too low. You can find and adjust this setting by going to Project Settings, Engine -> Rendering -> Default Screen Percentage.

We recommend setting the Manual Screen Percentage to 100 and the Screen Percentage Mode for Desktop renderer to Manual. You can increase the Manual Screen Percentage  to values like 110 or 120 for better resolution, but please note that this may impact performance and streaming quality.

Note: Additionally, be mindful that adding too many post-process effects can also negatively affect the visual quality.

FPS Issues

If you are experiencing low FPS, here are some steps you can take to improve performance:

  • Reduce Post-Processing Effects: Post-processing effects can be GPU intensive, especially in VR. Removing or minimizing these effects can help improve FPS.
  • Switch to Forward Rendering: You can change the rendering system to forward rendering by going to Project Settings, Engine -> Rendering -> Forward Renderer -> Forward Shading.
  • Change Lighting Settings: Switching your lighting from from stationary to static can also help enhance performance.

These adjustments can help optimize your experience and improve FPS.

Controller Beam/Lines Not Showing

When setting up VR projects, you may encounter two types of pointer lines that are displayed though the VR controllers:

  1. Debugging Lines: These lines show where the hands/controllers are pointing and are typically in red color.
  2. Purpose-Built Pointers: These lines are designed for user control, often used for player movement or interactions.

If you see the red bug controller beam lines when launching your VR project and don't want to see them, it is likely because the project is built in debug mode. Rebuilding the project in shipping mode will remove the red bug lines and fix the issue.

If the purpose-built pointer lines are not appearing as they should, but they do show up in the editor, it could be due to improper implementation or missing files in the build process. A good way to confirm this is checking through a local workflow (e.g., Running Steam VR > from Headset, connect via a Steam Link > Starting the model on the connected machine).

Package Optimization

To reduce your package size, a simple method is to only include items necessary for the maps you are using.

You can do this by going into the Project Settings and searching for package. Under the  List of maps to include in a packaged build, select only the maps your model runs.

Model Is Not Launching As A VR Model

If your model is not configured to launch as a VR model, you may notice the following symptoms:

When the model is launched from the headset, the stream goes to the Grid (Steam waiting room) and never gets past this point. Usually you should see the stream at this point within 30 seconds, depending on model load time, if it is launched properly.

Grid Steam Waiting Room

Secondly, attempting to launch a model through a local workflow (e.g., Running Steam VR > from Headset, connect via a Steam Link > Starting the model on the connected machine) results in a desktop view instead of a VR stream.

Model Not Initialized As VR

To ensure your model launches correctly in VR, check the following Unreal Editor settings:

  • Set Game Mode to VR:

Navigate to Edit > Project Settings > Maps & Modes > Default Game Mode > select VRGameMode

  • Add and Enable the OpenXR Plugin:

Add the OpenXR plugin: Edit > Plugins > Search for OpenXR and enable the Plugin. (Restart the Editor if prompted.)

  • Set the Game to Start in VR:

Set the game to start in VR: Edit > Project Settings > Search for start in vr and enable the setting.

  • Remove On-Screen Console Messages:

Ensure there are no on-screen console messages. Refer to the "Black Screen" section above for guidance.

  • Optional: If the model was initially started as a non-VR model, add VR content to the project:

In the Content Browser, go to Add > Add Feature Or Content Pack To The Project > select Virtual Reality > Add to project