Hi all , after borrowing one of these for a week I had to get one, great value for money.

However I am still getting quite bad jerkiness / stuttering when I look out the side windows. 

I can be going 150 - 500 IAS , out the front is fine, but low down looking out the side windows is very very jerky.  I switched developer mode on and I am getting a steady 59 Frames per second.  I have tried all sorts of settings recommended on Utube,  even set the SIm at default.

At Altitude its fine. Low down  Fly around Bowerman Airport in the USA , not good out the side

Quest 2  settings  120Htz (tried 80/90 )  1.5x  4224 x 2128

Tray Tool  ASW Mode off ( tried 18Htz, 30 Htz, 45Htz)  Bitrate tried 400-500, encode resolution 3648. 

I know the solution is don't  look out the side window when low,  but I am a bit OCD and want to improve it.

Is there some magic setting I need to investigate  for this particular problem?

Please can anyone help?  Appreciate any suggestions 

 

(he only thing I have not done is changed any settings in The Nvidia Control Panel. Driver  is 511.65 - If I change anything here will that effect when I play in 2D as that runs  great?)

 

System Specs

 

Intel(R) Core(TM) i7-12700KF

32.0 MB DDR5

MSI 3080RTX

win 11  

 

Edited February 22, 20224 yr by Bozdog

Have you tried switching between the various oculus reprojection modes? (ASW)

CTRL+KP1 - Disable ASW and USE ATW
CTRL+KP2 - Force apps to 45hz, DISABLE ASW
CTRL+KP3 - Force apps to 45hz, ENABLE ASW
CTRL+KP4 - Enable ASW to operate automatically

KP = Numeric Keypad

Open the 'Oculus Debug Tool'.
Enter 'Service'
Click 'Toggle console windiw visibelity'
The console will open. Don't close it!
Check if the landscape outside the window becomes smooth.
To close the console, repeat the above steps.

Another option is to lower the FOV in the oculus tray.  (must save before each session).  I have it set at 80 horizontal and 60 vertical which is pretty low, but I'm used to it now.  If nothing else works give it a shot.  Also, try a lower bit rate, I'm using 300.

3 hours ago, dogmanbird said:

Have you tried switching between the various oculus reprojection modes? (ASW)

CTRL+KP1 - Disable ASW and USE ATW
CTRL+KP2 - Force apps to 45hz, DISABLE ASW
CTRL+KP3 - Force apps to 45hz, ENABLE ASW
CTRL+KP4 - Enable ASW to operate automatically

KP = Numeric Keypad

Sorry I am a little new to all this VR, what does this mean CTRL+KP1?  Is this while running it in VR in the cockpit  ,    I press Ctrl  and   (What is KP1....   2 etc?)  is that number key 1, 2 etc?

Cheers

22 minutes ago, kugut said:

Open the 'Oculus Debug Tool'.
Enter 'Service'
Click 'Toggle console windiw visibelity'
The console will open. Don't close it!
Check if the landscape outside the window becomes smooth.
To close the console, repeat the above steps.

Hi Do I do this while Its running in VR  or  before I launch into VR?

Many thanks (I I will have a go tonight)

I ran both options (before starting any game and during the game) - the result was the same.

The twitching of objects during movement completely disappears.

 

You have to go to Oculus Debug Tool -> Service -> Toggle console window visibility, let it restart the Oculus service, and then Link will be fine for that and future sessions.

I have no idea why that works, but I toggled that setting 5 times in a row and it had consistent results (if console window wasn't visible, Link would be laggy; if the console window was visible, Link was fine). The console window needs to remain visible on the desktop and cannot be minimized. I'm unsure if this affects Rift or SteamVR. This was still needed for a Quest 2.

 

 

If I had to guess the issue, it has to do with 11 throttling applications that are in the background. There was an article somewhere else that had an unrelated application running into a Vsync issue and Windows automatically assuming that it could be throttled unless some power API was implemented.

Edited February 22, 20224 yr by kugut

Also, read this

It works the same way. And the inclusion of the console will not be necessary. It's actually surprising that Oculus engineers still haven't patched the software to be compatible with Windows 11.

Edited February 22, 20224 yr by kugut

4 hours ago, Bozdog said:

Sorry I am a little new to all this VR, what does this mean CTRL+KP1?  Is this while running it in VR in the cockpit  ,    I press Ctrl  and   (What is KP1....   2 etc?)  is that number key 1, 2 etc?

Cheers

Ah thank you, seems CTRL+KP1  give best result

2 hours ago, kugut said:

I ran both options (before starting any game and during the game) - the result was the same.

The twitching of objects during movement completely disappears.

 

You have to go to Oculus Debug Tool -> Service -> Toggle console window visibility, let it restart the Oculus service, and then Link will be fine for that and future sessions.

I have no idea why that works, but I toggled that setting 5 times in a row and it had consistent results (if console window wasn't visible, Link would be laggy; if the console window was visible, Link was fine). The console window needs to remain visible on the desktop and cannot be minimized. I'm unsure if this affects Rift or SteamVR. This was still needed for a Quest 2.

 

 

If I had to guess the issue, it has to do with 11 throttling applications that are in the background. There was an article somewhere else that had an unrelated application running into a Vsync issue and Windows automatically assuming that it could be throttled unless some power API was implemented.

Thank you so much for this, first time tried it headset crashed,  but it seems I also need to leave my monitor switched on.

It has really improved it. Still some instances , mainly in densely Tree packed areas - Bowerman is my test  airport,  or places like London or New York , but it is SOOOOO much better  really appreciate your time offering help .  Perhaps if Windows 11 is supported in future it will get even better.

 

I just need to stop tweaking and actually enjoy it

Thanks again