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
However, some things jumped out at me -- you mentioned running the game at 120 in the headset. I would wholly recommend you lower that to 90, as the game really can't handle 120 too well. You should see a massive improvement if you drop it to 90.
And then something else to just be vigilant of; running OBS itself will impact your performance as both things are hogging your CPU. All the physics mean the game is CPU centric, and OBS is CPU hog too. I used to stream and this was a pain for me.
And last, Airlink can be hit or miss (the Quest is currently not officially supported). Some folks are playing Airlink and having no issues. Personally I cannot get Airlink to run any VR game smoothly! It tends to be the case that people who can't use Airlink have better luck with a tethered Link cable, though funny enough I have heard the reverse too!
So you kind of have the unholy trinity of performance red flags going at the same time right now haha, 120, OBS and Airlink. Have a look into those first.
Then, if you are still struggling, here are some options to change in the settings that will greatly help:
Set "Physics Quality" to low
Persistent Bodies and Items to 1 or 2
MSAA to off
Render Scale to 0.75 (only do this if you are still struggling with performance)
Have fun!
What I think I might do (re: OBS), is record gameplay to a separate system. Apparently running DisplayPort to HDMI... then to an HDMI-to-USB capture card.... that takes the load off the gaming system. Could you verify? I've seen a lot of people do this. I have a 32GB ram laptop, quad-core i7 (2nd gen), with a 2GB Nvidia Quadro 1000m in it... 2.7ghz. For just capturing HDMI at 60 shouldn't be too much for it. I've done this before I got a gaming system, capturing Quest gameplay directly... worked pretty well.
As for Airlink-- ODD! Yeah, usually it works awesome for me. In the case of B&S, considerably better. VD hates my Blade & Sorcery, but.... then again... I was trying both at 120hz.
And lastly-- yes, those tweaks. I found those first, as soon as I started playing Blade & Sorcery and running into issues! :)
-Some of my insights:
*Accessing the Tool: The Oculus Debug Tool is part of the Oculus PC software. It's found in the "C:\Program Files\Oculus\Support\oculus-diagnostics" directory by default.
-Important Settings:
*Link Sharpening: Enhances image clarity without performance penalties.
*Distortion Curvature: Adjusts pixel density between the center and periphery of your view.
*Encode Resolution Width: Alters pixel count in the output image.
*Encode Bitrate (Mbps): Influences video stream quality.
*Encode Dynamic Bitrate: Dynamically adjusts bitrate based on network quality.
*Pixels Per Display Pixel Override: For supersampling or downscaling the image.
*FOV-Tangent Multiplier: Modifies the field of view to potentially improve performance.
*Asynchronous Spacewarp: A frame-rate smoothing technique.
*Mobile ASW: Optimizes frame rates for Air Link sessions.
*Adaptive GPU Performance Scale: Controls dynamic resolution scaling.
*Use FOV Stencil: Related to GPU pixel processing.
*Frame Drop Indicator: Displays on-screen frame drop alerts.
*Bypass Proximity Sensor Check: Previously allowed display to remain on when the headset was removed, but may not work with Quest 2.
*Force Mipmap Generation on All Layers / Offset Bias: Deals with texture resolution at varying distances.
-Troubleshooting Tips: Restarting the Oculus service can resolve issues with settings not applying.
-Performance Overlay: A useful feature for measuring and optimizing in-game performance.
-Resetting Default Values: Manually reset numerical values and dropdown options to default to undo changes.
-Useful Menu Items: Includes Performance Profiler and Mirror View for gameplay monitoring and sharing.
I tried to summarize it, but I encourage you to dive into the full article for more info:
A big thank you to all who contributed to this knowledge. If you have any questions or feedback, feel free to reach out!
Read here: https://smartglasseshub(.)com/oculus-debug-tool/