VR Discussions, Questions & Feedback

My VR performance is also worse than before the update. I experience some microstutters.

 

Yep my performance is worse gpu usage is also higher, 7800x3d rtx4090 pimax crystal

 

Hello it’s because whatever we do us meta headsets users the game will launch in oculus mode

there is no call to steamvr by the Game means all the openxr tools are not accessible

mat least that’s what I have learned and experienced

to improve the performance with my Q2 I use vrperfkit instead
Resolution scaling and FOV rendering can be adjusted by editing a file
Some tutorial exist on YT to achieve that purpose

 

Hi,
I use Virtual Desktop instead of Oculus link. And instead of installing OpenComposite, I only copy the Opencomposite dll file (openvr_api.dll) in the AMS2 folder, replacing the AMS2 original dll file. With that I can see the OpenXR menu in game and configure everything, launching the game with SteamVR option. I hope it helps.

Additionally and for better performance, in Virtual Desktop PC options I have selected VDXR.

And about the other last comments in this thread, I have also noticed a worse performance after last AMS2 update from yesterday. Some sttuter even driving alone (3080 RTX) when in previous version everything was far better.

 

I have to concur, although I only got to run a couple of cars at Oulton, Brand’s and Donny last night, my FPS was immediately suffering since updating and I too had drop quality settings to regain.

 

Fair point about VD

If the standard way to launch can be bypassed by VD. and get the openxr triggered that’s great

I did a couple of runs yesterday after the Game update also with a RTX3080 and no significant stutter
I don’t use fpsvr that was told to create such stuttering with their latest update in other Games

 

I need to take a look at this, as I understood OpenComposite would not work. Thanks for the detailed response you gave.

 

I am quoting myself because I was testing VR with Render scale set at 0.9 as it used to be before the Game update.
If I set to 1.0 so native resolution from the headset its true that stutters is noticeable.
I am current testing a PICO VR headset(the P4),I need to see whether it happens the same with my Q2, or not


Extract of the vrperfkit file here
# enable (true) or disable (false) upscaling
enabled: true
# method to use for upscaling. Available options (all of them work on all GPUs):
# - fsr (AMD FidelityFX Super Resolution)
# - nis (NVIDIA Image Scaling)
# - cas (AMD FidelityFX Contrast Adaptive Sharpening)
method: cas
# control how much the render resolution is lowered. The renderScale factor is
# applied to both width and height. So if renderScale is set to 0.5 and you
# have a resolution of 2000x2000 configured in SteamVR, the resulting render
# resolution is 1000x1000.
# NOTE: this is different from how render scale works in SteamVR! A SteamVR
# render scale of 0.5 would be equivalent to renderScale 0.707 in this mod!
renderScale: 1.0

 

I have tested again today and no stutter. It seems that yesterday something else what impacting in the performance just after the update. Strange. I will continue testing next days.

 

Would like to know why the update has effected vr performance, tracks like Montreal l could hold 90fps no problem now getting drops into the mid eighties on certain parts, tried steam vr and openxr both drop at the same points on the circuit, haven't changed any game settings.

 

I can’t say I have noticed any change in performance since the release. I’m on a Quest 3, 3080 10 gig and 5800x3d, 32 gig of RAM and I just run the Oculus version from Steam.

I’ve got the encoding set to 500 in Oculus Tray tool and I run 0.8 on horizontal and vertical for the FOV tangent multiplier. That does give a slight letterboxing on the vertical but when driving you don’t notice it.

The only real stutter I get is one that I’ve also had at various times playing flat screen where a car turning in front of you seems to skip a frame or two.

Running with the performance display on in VR this seems to correspond with random spikes in the game that doesn’t seem to really correspond with something particularly heavy happening on screen. I think it’s a game engine issue that is more obvious the closer you get to the limits of your hardware.

I got rid of it in flat screen mode by dropping down from everything on Max in 4k to 1440p with some supersampling and the game looks pretty much the same. Unfortunately in VR you don’t have that much headroom to play with. I could lower a bunch of settings to deal withe the occasional spike but I’d get a worse image for something I only notice a few times a lap.

 

Sorry if this is a noob error, but I'm new to AMS2 and I'm trying to get it running on my Varjo Aero using OpenXR through OpenComposite. I'm using OpenXR without issue in iRacing so I'm confident the OpenXR installation is at least OK.

I installed the latest OpenComposite and ran it, allowing the DLLs to install. I then use it to switch to OpenXR runtime and tried to launch AMS2 through Steam using SteamVR as the popup choice. Is that correct?

Anyway, I'm getting a popup error with the following:

"OpenComposite DLLMain ERROR: Cannot init VR: unsupported apptype 0"

AMS2 does not launch.

Can someone please point me in the right direction here? Much appreciated!

 

Can the helmet overlay please be altered slightly so that it provides better visibility when playing in VR?

I love the idea of actually seeing your helmet in-game, especially because the overlay actually bounces around and visibly has the the sun shining into it and casting shadows - but the one we have in the game currently feels like you are wearing a mediaeval knights helmet because of how incredibly narrow the opening in the helmet is.

So basically I would love for the current helmet overlay to be edited slightly for VR players to simply make the opening larger.

 

Just my 2 cents. But given that some people don't have issues and some other do, might it be driver related? I know I have issue with th latest drivers in Blender for example.

 

I tried several different drivers, and no joy. Anyway, it sounds like I became a lot more CPU bound than before the update. Even with a low number of opponent cars.

 

I rolled back to a previous driver, still getting frame drops into the mid eighties on Montreal where l was comfortably over ninety, something has changed in this update for the worse rtx 4090 pimax crystal

 

I'm with you on this one. I'm definitely getting some performance dips since the update.

 

for me its more stutters that have appeared. but in the same time,I am testing a new PICO headset so it might be related.

will revert back to my Q2 later today as it was driving AMS2 at high resolution/graphics like a champ, with the help of an RTX3080 and 5800x3D that is

that's what I get with the PICO, ruining the VR experience right now

 

I’m using a Quest 2, Wired Link at 90Hz, 1.0x rendering in the Oculus PC app.
Oculus launch option in Steam.
Medium MSAA, high car & track details(going higher yields diminished returns).

I encounter no issues. I would push things slightly higher, if I had a separate capture PC to take the recording strain away completely, but I need any overhead to account for that too.

 

I did not have the spray clipping befor but I have it since the last update. Also some of the smoke from campfires and some of the smoke from cars but not all. is clipping through the map, cars and helmet. There was already a lot clipping through the helmet like frontscreen of almost every F1 car and with the F1 Reiza you see all the buttons of your wheel through the helmet. But the new spray and smoke has priority since it is unplayable in the rain now and I realy like to do it.