Quest 3 Noob with Performance problems and lots of questions

Hey guys,

I am enjoying ED in VR very much, but the performance seems sometimes a bit lacking. I have an RT3070 TI with 32 GB Ram and an AMD Ryzen 7 5800X 8 Core but I have some serious Framedrops in Station, Planets, Rings, a lot of bugs f.e. I suddenly have serious screen tearing (sometimes I can resolve this with putting the Quest off and on again, which makes the headset "reload" something) or even extreme lag spikes that make me need to restart the game.

On top planet surfaces look like s***, Stations have glitchy shadows/lights (sometimes I have them even in my cockpit) and jumping out/into a system always has some lags.

I am running the Quest via Link Cable and the Meta Quest Link.

I tried my way around with Steam VR, but that tanked the performance massively, so I am running Elite via the Frontier Launcher and Meta Link. That helped with frames in Space, but not with the problems mentioned before.

The Quest settings are 72hz set to native resolution (found some reddit entry that discussed that this was the best setting).

These are the settings I ended up with in the Oculus Debug Tool:

oculus debug tool settings.png



My ingame settings are mostly medium, with some areas boosted as they really annoyed me or gave me a headache when lower (like 1.25x Resolution because anything lower had very ugly edges)
Elite Profiler Settings.png



So I was looking a bit around and saw that there is this VRPerfKit available and I wanted to ask if it would help me with performance and if so, what settings would you guys recommend. Did I make a serious mistake with the settings in the other tools or do I miss something that could greatly enhance performance?

You probably realised by now that I am pretty new to VR. Quest 3 is my first VR headset and I exclusively got it for Elite. So any help, any advice or hint if I am maybe making a newbie mistake would be very appreciated.

Thanks, Jan
 
Last edited:
Hey guys,

I am enjoying ED in VR very much, but the performance seems sometimes a bit lacking. I have an RT3060 with 32 GB Ram and an AMD Ryzen 7 5800X 8 Core but I have some serious Framedrops in Station, Planets, Rings, a lot of bugs f.e. I suddenly have serious screen tearing (sometimes I can resolve this with putting the Quest off and on again, which makes the headset "reload" something) or even extreme lag spikes that make me need to restart the game.

On top planet surfaces look like s***, Stations have glitchy shadows/lights (sometimes I have them even in my cockpit) and jumping out/into a system always has some lags.

I tried my way around with Steam VR, but that tanked the performance massively, so I am running Elite via the Frontier Launcher and Meta Link. That helped with frames in Space, but not with the problems mentioned before.

The Quest settings are 72hz set to native resolution (found some reddit entry that discussed that this was the best setting).

These are the settings I ended up with in the Oculus Debug Tool:

View attachment 403984


My ingame settings are mostly medium, with some areas boosted as they really annoyed me or gave me a headache when lower (like 1.25x Resolution because anything lower had very ugly edges)
View attachment 403982


So I was looking a bit around and saw that there is this VRPerfKit available and I wanted to ask if it would help me with performance and if so, what settings would you guys recommend. Did I make a serious mistake with the settings in the other tools or do I miss something that could greatly enhance performance?

You probably realised by now that I am pretty new to VR. Quest 3 is my first VR headset and I exclusively got it for Elite. So any help, any advice or hint if I am maybe making a newbie mistake would be very appreciated.

Thanks, Jan
Hi Jan, the first things that leap out at me are that you’re running 600 Mbps with HMDQ 1.25 on a RTX 3060 - when I had a RTX 3070ti and a Quest 2 I was running something like 100 Mbps with HMDQ 1.0 (although I had most other settings turned up as high as I could get them).

Today with my Quest 3 & RTX 4070ti I’m going at default encoded bitrate for Link in the Tray Tool or 150 Mbps variable for AirLink when I use that, with HMDQ 1.25 and most other in-game settings as high as they go.

First thing I’d do is set the bitrate back to default. If you want HMDQ 1.25 then I’d put all other settings down to their lowest, check to see if performance is good (I usually choose a station interior or planet port for testing) then gradually increase settings from there. I always have Ambient Occlusion off as that’s a performance hog for not much visual gain.

Glitchy shadows and a few other visual problems are unfortunately part of the game - please see the VR bug thread (linked in my signature) for current issues.
 
Hi Jan, the first things that leap out at me are that you’re running 600 Mbps with HMDQ 1.25 on a RTX 3060 - when I had a RTX 3070ti and a Quest 2 I was running something like 100 Mbps with HMDQ 1.0 (although I had most other settings turned up as high as I could get them).

Today with my Quest 3 & RTX 4070ti I’m going at default encoded bitrate for Link in the Tray Tool or 150 Mbps variable for AirLink when I use that, with HMDQ 1.25 and most other in-game settings as high as they go.

First thing I’d do is set the bitrate back to default. If you want HMDQ 1.25 then I’d put all other settings down to their lowest, check to see if performance is good (I usually choose a station interior or planet port for testing) then gradually increase settings from there. I always have Ambient Occlusion off as that’s a performance hog for not much visual gain.

Glitchy shadows and a few other visual problems are unfortunately part of the game - please see the VR bug thread (linked in my signature) for current issues.
Hey man, thank you for your answer and taking the time. I will adjust my "expectations" regarding performance to what you suggested.

Sadly, there were two misinformations (or lack of informations) in my opening post.
First, I have a RTX 3070 TI (seems like my brain glitched when I wrote 3060).
Second, I am running the Quest via Link Cable and Meta Quest Link.

Don't wonder, I added that to the original post.

I tested the cable connection in the Meta Quest Link App and it said that I have a bandwith of 2.4 Gbps (sometimes going low to 2.3 Gbps). With the default Mbps (that was 150) I had some serious compression in the image. So I watched some YouTube videos about that and found tons of recommendations of putting the Encoded-Bitrate to something higher than 500 and lower than 920 (because there was some cap).

As I understood it, this Encoded Bitrate should have nothing to do with the performance of the system, but with only with performance and bandwith of the USB Port the cable is attached to, or did I get something seriously wrong about that?
 
Hey man, thank you for your answer and taking the time. I will adjust my "expectations" regarding performance to what you suggested.

Sadly, there were two misinformations (or lack of informations) in my opening post.
First, I have a RTX 3070 TI (seems like my brain glitched when I wrote 3060).
Second, I am running the Quest via Link Cable and Meta Quest Link.

Don't wonder, I added that to the original post.

I tested the cable connection in the Meta Quest Link App and it said that I have a bandwith of 2.4 Gbps (sometimes going low to 2.3 Gbps). With the default Mbps (that was 150) I had some serious compression in the image. So I watched some YouTube videos about that and found tons of recommendations of putting the Encoded-Bitrate to something higher than 500 and lower than 920 (because there was some cap).

As I understood it, this Encoded Bitrate should have nothing to do with the performance of the system, but with only with performance and bandwith of the USB Port the cable is attached to, or did I get something seriously wrong about that?
I can only go by my own experience - when going to high Mbps using the Tray Tool I have performance problems in games. I get a lovely clean image but there will be stutters when my system cannot keep up. Whether that’s due to my USB3 port or the cable I’m using, I don’t know.

I’m sure others will be able to give you better info because I stopped fiddling with external settings and software quite a while ago; it was a lot of faff for not much visual/performance gain (to my eyes at least) and often gave me issues I’d be scratching my head at. These days I leave the headset settings at default and just adjust game settings to get the performance I’m happy with.
 
Ah, I understand. Well, I have no experience at all, so I will try this again and see if I can get a more stable experience.

I just tested the low settings now (granted, I put textures to high and everything else to low). Even though inside stations edges are flickering a lot, it was a smoother experience. So thank you for all the Input.

Do you, or maybe someone else also have experience with VRPrefKit? I can't seem to get it running with Meta Quest Link without steam.
 
Hi, I'm still on the same search for good settings.

With the Encoded Rate you are right, but I can set 500 mbps only in the OculusDebugTool.

Graphics Quality:
I can confirm, sometimes ground textures look like from an old game from the past. And my eyes are abused by a 4K widescreen with ultra settings and 2x Supersampling due to a rtx4090.
I tried a bit with different settings. Yesterday e.g. I found out, that the ground textures become way better, when the primary monitor stays on 4K instead of most peoples recommendation of "low resolution". I also do not touch any other setting on ultra/high except the SuperSampling, which I lower to 1.0 and Normal instead FSR.

I still have to say, that it is a shame of Frontier not to care for or even push on VR as it was one of the best games for it.
 
Anything else you would change considering the strong GPU/CPU and the Quest 3 connected via USB3 Link?
1729072934085.png
 

Attachments

  • 1729072690269.png
    1729072690269.png
    38.9 KB · Views: 37
Last edited:
You could try disabling Adaptive GPU Performance Scale. As the name suggests, it adapts the resolution depending on performance available. At least for testing you might want to disable it, since you could be increasing the resolution (and image quality) beyond what your system is capable and not see any benefit since the system will just drop the resolution to compensate.
 
Back
Top Bottom