Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
There's a plugin for OBS Studio to capture VR Sources and that lets you select which eye and can record sound. This is my preferred way of doing it. Doing it through OBS Studio also allows you to set it up as a Virtual camera to share to Discord or whatever.
Using the built-in desktop mirror from the game increases system resource usage, hurting both VR and desktop performance.
It's often the best method because if the developers do it correctly, they can provide a wider screen and static info for the spectators. HL:Alyx is a great example of this being done correctly, and afaik, the only one that has done it correctly.
iRacing is a close second in that it offers at least a correct FOV, as if you do it via OpenVR/OpenXR capture in OBS, the available window is too small if you do one eye, and if you have a canted display, it has an odd split in the middle with 2 eyes.
on top of that, using the direct OpenXR/VR capture can increase instability as well. While there is a small performance hit from window capture, it has the most benefit overall when a game is handling it correctly that is far more beneficial for the viewer.
And I tested all sorts of methods over the course of 5 years. Game mirror is 100% preferred when it's actually handeled by the dev correctly.
Unfortunately not, it's been a long time since I played ets 2 on VR anyway and gave up on it.