VR Discussions, Questions & Feedback

For me, VR was great before the update.
VR still looks fantastic and even better with the new shaders and particles but it is killing my frame rate.

I have all settings in potato mode now @72hz and i can't race in a multiplayer lobby without my FPS just getting hammered. I'm pretty sure it is the new particles.

The patch notes mentioned that particles in MP lobbies would be forced to "LOW" setting for everyone to negate the advantage drivers have when turning them "OFF"

It seems even having particles on LOW they look much better and real then they used to but for the sake of performance multiplayer lobbies should force the particles 'OFF"

In multiplayer aside from the particles i also get a spike on the frame graph overlay using the oculus debug tool i can see it repeat like a heart beat.

I know my system is not the best, cpu is aging and i plan on a upgrade but i hope this can be resolved because it used to run like butter

 

spikes are more from people joining and leaving the server, normally only when youre not driving (for me). what system are u running

 

To update my previous post, i am in testing in single player race with settings on high in the rain and i am getting the performance i would normally expect plus the benefit of it now looking so much better with the new graphics.
Something in multiplayer must be hogging down the FPS, it runs and looks really good in single player.

q3 link @72
i7 8700k amd6900xt 16gbVram 32gb ram

EDIT.
The problem seems to be track related. Sebring in both single player and multiplayer run very badly in comparison to Interlagos with the same weather/rain and race settings

 

Sebring is just very bad optimized, the worst out of the new tracks. I hope in near future patches this is addressed. For me, there is also one corner in Mosport where I lose frames, whereas Road Atlanta is completely fine (as well as older tracks)

 

I agree about Sebring - I love the track but even on my 4090, 13900k and Index i have very bad stuttering with low fps around the track.
Worst place is Sunset Bend

 

MP always was a crap in PCars 2 and AMS2.

Someday, with good dedicated servers that have a MP logic that don't stutters every client, will be really nice in a fast paced racing game.

This isn't Reiza fault, it's really poor MP capability of Madness Engine.

 

The stutters aren't because of MP (of course there can be such too, but it's not related to VR performance).

For some reason I haven't really have big fps drops on VR (though I run quite low graphical settings in the first place to have headroom), but I have occasionally annoying stutters. These don't happen when using ultrawide (which much higher graphical settings and fps) at all, so I suspect it might be caused by some other problems, such as windows/gpu drivers/headset updates etc. and not the game update.

 

I am playing on Quest 3 but does anyone know how I can assign a 'Select' or 'Confirm' button on my wheel or even the Quest controller ? In vr on a motion rig it is incredibly slow & difficult trying to use a mouse. Every other sim I can assign wheel buttons for movements or select options but cannot find a way in AMS2. I guess nobody at Reiza plays in vr because it seems an obvious oversight having to be tethered to a mouse I would think ?

I did read on reddit that someone was using their Quest controller but I am connected via Link Cable and it does not work. Appreciate any advice. cheers.

 

There is a setting in game (VR options) that enables a pointer that shows up after a few seconds of inactivity. You move it just by looking around and press your usual wheel bottom to click.

 

Yeah that is the gaze control and I have that but there is no wheel button that can select or confirm it. I still have to reach for the mouse button to press and select.

When you say to 'press your usual wheel button' what wheel button are you talking about ? There is nowhere in the assignment of wheel buttons that I can find a select button. What are you using ?

 

The same button that I use when selecting stuff with the pad controller of my wheel. In my case, wheel is t150 and the select button is the 'x'. I am pretty sure it can be mapped if it doesn't set up for you by default

 

I use joytokey and map my mouse to my wheel hat switch and button

 

A ps5 controller is what i use for menu navigation. its wireless too

 

I am reading that VR has become harder to run since 1.6. Definitely the case for me. I just created a thread for Reiza to add Quad view foveated rendering to AMS2 as this would help tremendously with performance. Please take a look and like to make the post visible. Thank you.
Quad View Foveated rendering for VR mode

 

Thanks for the suggestions, my SC2Pro wheel does not have an a,b,x,y pad on it and there is no option within AMS2 to map a select or confirm button to a wheel unfortunately. Looking back it seems this was raised several years ago and still not added.

Perhaps I am wrong but I would have thought that modifying the code for assigning buttons to a wheel would not be a huge task, or is it ? Reiza maybe prefer flatscreen and do not go too far into VR too much or they would notice the inconvenience of having to use mouse for selecting. The gaze control is actually pretty good so I am going to try joytokey and map right mouse button to a wheel button and that should work.

 

The dpad on my thristmaster TSPC wheel was detected and confirm/back buttons as well

it was also working in PC2

I moved to MOZA DD wheel last year and now SIMAGIC NEO GT and in both cases functionality was gone

not sure if that’s Reiza issue or wheel makers

 

My two cents for all the Quest 3 Users:

1. Use Quest Link (I use wired, but wireless also works fine)
2. Open the Debug Tool (Google for Oculus Debug-Tool, not sure if I can post links)
3. Set FOV-Tangent Multiplier to 0; 0.4 or lower

This reduces your vertical FOV to 40%, making it so you don't see your feet and your roof anymore, but in turn also saving massively on rendered pixels. Performance doesn't improve by 60%, but it still improves considerably.
I'm currently rocking 0.25 because it enables me to run at 120fps with a Ryzen 5 5800X3D and Raden 6800.

What it doesn't help with are stutters that I am having at certain parts of the track all the time.
Coming over the crest at the end of Road Atlanta constantly freezes for a few milliseconds. Anyone else experience this?

 

They've actually made it worse.
Project Cars 2 allowed full control over every part of the menu with the wheel buttons/joypad.
AMS2 up to and including v1.5 allowed full control over every part of the menu but had weird behaviour with not being able to return out of watching replays and changing weather once you've ran a race with "hazy" weather.
AMS2 v1.6 now doesn't allow you to select the "Options" section at all from the wheel. |It still acts weird with hazy weather, breaks the car/track selection menu as it's impossible to tell if you're selecting a car or a car group. But now allows you to return from replays.
Back buttons no longer take a step back out of menus, you have to select the option and confirm on every single step.
They've designed the UI menu around a mouse when 100% of players are using a wheel/controller.

 

Yep, I get those kind of stutters occasionally and often on same places on the track (though it's not guaranteed, some laps might be better than others), even if I'm driving alone in a test session. It's usually the hairpins or the like where that happens. If I use flatscreen, it's smooth even with much higher graphical settings that what I use on VR (on VR, I have a lot of of the settings as "low")

I wonder what it is.. it's like some bandwith isn't enough temporarily in certain situations. My FPS seems to stay the same though.