VR Discussions, Questions & Feedback

Reverb G2 so yeah it's different, doesn't matter as I've tweaked enough for now was purely interested in the possibility of limiting vertical view.

 

Right Ctrl + numpad 1, 2, 3 and 4 cycle ASW modes:

1 = Full Refresh Rate FPS, ASW OFF;
2 = Half Refresh Rate FPS locked, ASW OFF;
3 = Half Refresh Rate FPS locked, ASW ON;
4 = ASW AUTO (kick in with less FPS than Refresh Rate).

 

You need to restart AMS 2 for it to take the adjustment, otherwise you just end up with as you discovered a squashed image.

 

yeah but the issue is it won't "blank" out the top & bottom of the image which is what is required to help improve FPS further, that's why the FOV adjustment won't work for me with this scenario. FYI adjusting FOV with the Toolkit does not require a restart

 

It does require a restart because it has to request a new render resolution which is what crops the image.

 

I apologise you are correct, I'm so used to the Toolkit saying it needs a VR restart I was relying on that but it didn't state it (like it does for some other options). Unfortunately lowering both UP/DOWN Vertical FOV to their lowest amounts changed nothing with the FPS, like with the Disable Mask HAM setting available in MSFS which disables the hidden area mesh (and helps performance) that is what I need for AMS2 but as above it's not available.

I guess with the FOV change even though you see less it's still rendering underneath the blank areas regardless, a shame but not a major loss.

 

Hi Marc,

Are you referring to the opencomposite.ini file in the x64 folder?
hiddenMeshVerticalScale=0.3

I don't know if it really works though. Don't see much difference

 

no need to apologise, I got caught out by exactly the same thing intially. And also in my case with the pico 4 I actually take a performance hit so it does nothing for me either but, hopefully it's helpful for someones use case.

Anyway overall, I'm pretty happy with performance, realistically only a new gpu is going to get me over the nightime + rain barrier at acceptable settings and even still the aliasing isn't worth it for me. So I just have to live with boring old daylight hours for the time being.

 

Yes, but the small wireless keyboard I use on my lap from the rig doesn't have Numpad and the full keyboard on the desk is a bit of a stretch to reach from the rig so just use the keyboard track pad to toggle ASW in the Debug Tool before starting up the game.

 

hello


can you confirm few things? because your Graphics settings are pretty high so I wonder how you can maintain 90fps in night&rain conditions.sorry maybe many questions but I am curious as I ahve a Q2 and RTX3080 and thats not easy to run at 90fps honestly in such weather conditions

1. you mentioned Daytona and Nord but do you do Race or Hot lapping?
2. if Race, how many cars on track and how many visible?
3. If Race, is 90fps sustainable when you are in the middle of the pack?
4. do you drive in cockpit view?
5. any assistance of tools like Openxrtoolkit to adjust the rendered resolution (not only FOV as you did but foveated rendering resolution and upscaling like FSR or CAS)

thanks a lot!

 

for Pico users, feel free to comment as I own a Neo3 Link with the DP cable so pure image clarity with no compression

I have spent my afternoon doing lots of runs at Imola, 31 cars and 12visible in night&rain conditions, cockpit view

I do use relatively high Graphics settings

Texture Resolution: High
Texture Filtering: Anisotropic 16X
V-Sync: Off
MSAA: Variable (see below)
Reflections: High
Environment Map: High
Car Detail: High
Max Vehicles: 12
Track Detail: High
Pit Crew Detail: All
Shadow Detail: High
Enhanced Mirror: Yes
Motion Blur: Off
Render Frames Ahead: 2
Detailed Grass: Low
Particle Level: Medium
Partical Density: Medium

1. maintain 90fps is possible with stock PICO Link drivers but MSAA Off and openxrtoolkit with CAS 90% sharpness and FRR at Performance and Narrow
2. maintain 90fps is possible with modified PICO Link drivers (so called 1.3 hacked resolution, available on discord) and MSAA High and openxrtoolkit with CAS 90% sharpness and FRR at Performance and Narrow
   
3. maintain 72fps is possible with stock PICO Link drivers with MSAA High and openxrtoolkit with CAS 90% sharpness and FRR at Performance and Narrow

 

Hey here my answers:
1.I do races there, no hotlapping!
2.maximum cars on two classes (all cars visible)
3. I have at the race start min. 40 fps and after the first corners it's about 60 fps. Than it's after 2 minutes (not exactly) between 80 and 90 fps. It goes a bit down when someone overtakes me or I'm overtakes somebody (but not lower than 60).and yes, I've started in the middle.
4. Of course in cockpit view!
5.no other assistance!

For me it's absolutely driveable, because in rain and night it's only at the start a bit laggy and in good conditions it's much better, that's okay!

 

OpenXR - How to Remove Artifacts from FFR with MSAA active:
Small report about another VR finding regarding OpenXR-Toolkit.
Background: FFR (Fixed Foveated Rendering) is a nice way to enhance performance in VR by heterogeneous resolution over the field of view. In the center it's as high as possible and it gets more pixelated at the borders. This is done via rings or ellipses in the openXR toolkit. When driving, it's hard to recognize at all.
However, in my case combining this option with MSAA (to remove the shimmering) and FSR (upscaler), I was always getting heavy artifacts in the outer parts, like missing objects, partial objects, stripes, crosses, etc. I tried this morning a few settings, whether there are some "magic numbers" to remove those artifacts. The good news is: Yes, there are. There are no bad news, except maybe that I still don't know the exact formula to derive the correct parameters
Using MSAA medium, the only resolution reduction factor which works for me reliable is 1/16. Also the middle ring makes problems, so I basically switch it off by setting it's size to the outer one (see the settings below). However, this is not enough. To get no rendering artifacts the headset resolution and the FSR resolution needs to be at very specific numbers. In reality it's probably only the FSR, but it's only controllable in 1% steps and some integer-casting or rounding is going on. The "magic resolutions" I found so far are (first one is the headset resolution):
- 3100, FSR 0.80
- 2918, FSR 0.85
- 3200, FSR 0.72 (my current baseline), if my hand written notes are correct.
- 3960, FSR 0.54
To get the final numbers I sometimes need to add or remove 1-3 pixel on the headset resolution (always reboot the game) and suddenly for a certain pixel no. everything is fine. Typically the first number*FSR factor is dividable by 16, however, the last one proves this wrong . So fine tuning by a few pixels to really get the artifacts away after FSR (rounding effect I guess) remains.

Here are the settings for very aggressive FFR (combined with my FSR 0.72 baseline above):
FFR: custom
Inner resolution: 1x
Inner ring size: 40% (same as below, increase this one to increase both)
Middle resolution: 1/16
Outer ring size: 40% (same as above, lower this one to decrease both)
Outer resolution: 1/16
Horizontal scale: 160%
Vertical offset: -16%
Left/Right Bias: none

The nice thing about the FFR is, that it can be switched on/off and the size can be modified on the fly, without any restart of the game. So when I encounter a low fps situation (Monaco track, or weather, etc.) I just switch it on or tune a bit the size (the settings stay stored), though, without pausing, something like the Döttinger Höhe is recommended

Final note, probably already written somewhere, but I just discovered it today: when trying various openXR configs, where multiple parameters need to be tuned, it gets hard to remember all of this (old brain). In the registry (regedit) under HKEY current user / software / openXR. You can simply export the current settings per game (right click on its folder) into a reg file, e.g. to desktop. Simple double-click on it before starting the game sets the settings correctly. With this I can compare very fast two different "baselines" and decide which is actually the better one.

Greetings

 

Use VoiceAttack

 

Nice experiment

Thanks a lot for sharing

 

I uninstalled a bunch of VR stuff today and fixed some problems I was having for all my games, but now in VR for AMS2 my HUD components are all angled - leaning forward. How can I adjust this?

 

Access the HUD settings and select Help. The key's to fix are there.

Edit: giving credit... found post where I discovered this: VR Discussions, Questions & Feedback

 

Will do. Thanks.

 

"I'm sorry, can you please repeat that?"
I do use Crew Chief occasionally for fuel calculations etc, but he often does not understand me. Maybe doesn't like the Aussie accent or something? Anyway, noted to maybe one day trial voice commands again in the future

 

I'm currently trying to experiment with the sharpness in the distance and am wondering how I can get the sharpness in the distance a little better.

Initial situation:
-I have msaa: high
-Anisotropic 16x
-Texture res.: high
-following settings in the graphicsconfigoculusdx11.xml:
<prop name="SharpeningStrength" sharpeningstrength="1.00000" />
<prop name="SharpeningClamp" sharpeningclamp="0.090000" />
<prop name="OffsetBias" offsetbias="1.100000" />

Nvidia settings:
FXAA & MFAA: ON
Power Management mode: Maximum

My Problem: When I'm on a track I can only see clearly 50 - 100 meters away (I use the 50m signs before corners to know what 50 - 100 meters are)

Unfortunately, changing the sharpening strength in the graphicsconfigoculusdx11.xml (between 0.0-2.9) does not improve the sharpness in the distance.

My questions:

1. Does anyone have any other ideas to improve the sharpness in the distance?

2. What do the two parameters “sharpening clamp” and “offset bias” stand for? I do not get it!