VR Discussions, Questions & Feedback

Yes it was! Made my day!

 

We can edit the sharpening strenght in the config file now ?

 

Up until recently I have been using AMS2 with Quest3 and before that the Reverb and had no major issues .

But now after the latest batch of updates I have considerable drawing of both on and off track artifacts like lorries, gantries and the like . I run at 90fps with around 20% head room , with all the usual shadows / reflections/ set on low , with no outside interference other than Oculus debug tool which i use to reduce fov to .8 x .7

I have tried the usual downgrading of settings but nothing seems to be showing up as the culprit.

What would people suggest I delve into to see what may be causing this as seeing a row of 20 lorries being drawn in front of you does become a little distracting

 

Did you turn on the LOD graphic setting? Try disabling that perhaps

 

Perhaps the maximum number of vehicles displayed can be found in the graphics options.

oh and maybe Track details too...

 

Meta updates Link software... Someone else now have crap performance?

I just want a cheap and good headset with a DisplayPort...

 

i just upgraded to the pimax crystal light from the quest 3 and have noticed that i am faster the gears go in faster and the pedal inputs are faster so i am very happy with it ,and most graphic settings on ultra except shadows , i also have a 5090 now
So in conclusion i think you get some input lag with the quest 3

 

Thanks for responding - still scratching my head though

Already off

number of vehicles only at 15 and alos this is in test day so only me on track
Track details already at low

simples solution - i removed all graphics files from the my documents ams2 folder - restarted game - and using defaults the draw issue has disappeared

Funny thing is using the game defaults i saw no difference in quality from my hours of tinkering !!

my only observation would be that the only thing i messed with recently was TAA and i have a suspicion (and its that only) that when you do this and try to revert back it somehow leaves some issue with the other settings

 

This isn't directly related to the Quest itself, but rather to the frame rate you're using. If you compare 72 frames per second with 120 frames per second, you'll have significantly better frame times at 120. This results in the brake pedal registering almost 50 more inputs per second, making it much more precise.

In addition, there is the latency caused by, for example, Wi-Fi to HDMI.

Sim racing is kind of pay-to-win. If you're just 0.1 seconds faster per lap, multiply that by 50 laps.

 

I’m no expert but…..I think it’s a mix of a few things, the latest quest updates have impacted, the latest Reiza update has impacted and the fact that sharpening file no longer works all contribute.

I had to knock my quest 3 back to 72hz and 1.0 just to be able to play in vr (before it was at 120hz and 1.5 and was absolutely beautiful). What I did notice as well was that the meta link when on screen has become all pixelated

I think my rig is decent enough and AMS 2 was running absolutely amazing before Christmas but now I’m hardly on as it’s just not the same unfortunately

 

If you have a Quest 3, then switch to Virtual Desktop in conjunction with an Ethernet-to-USB dongle. This way you get the best of both worlds and get rid of MetaLink.

(90Frames with 28-35ms latency)

 

i always used the 72 hz mod with latency very low , i think it was cpu around 5 ms and gpu around the same ,if i used the 120 hz mod i could never get 120 fps unless using space warp and i didnt use virtual desktop , i used the usb cable

 

not sure if this is pure coincidence or not - but ams2 wouldn't start in oculus mode today even if selected it started in steam vr . Guess what has been updated today though and when i uninstalled steam vr - oculus worked again!

 

hi all

I'm having trouble with the Oasis Driver for SteamVR / WMR. This might be a SteamVR problem and not AMS2 related, but I wanted to bring it up, perhaps someone knows something.

Long story short, after WMR's death in Windows 11, Oasis driver was created to keep the WMR headsets like the HP Reverb G2 (what I use) still alive. And it works! It works great, actually. Except for me, after a certain amount of time, tracking completely crashes.

I have some logs that I could share, not sure if there's any hope out there for me though.. I did notice the first lines relevant to the crash directly reference AMS2AVX. so... idk.

This is all running currently on Windows 11 25h2


Closing pipe 28304: AMS2AVX because it was broken from the other end
Process 28304: AMS2AVX disconnected (Thread(0x00000189192F0950/0x000)
oasis: Switched to app:
AppInfoManager.ProcessDisconnected processid=28304 eLaunchingApp=LaunchingApp_None
AppInfoManager.ProcessDisconnected: Clearing application steam.app.1066890 PID was 28304
AppInfoManager.ProcessDisconnected: Clearing application steam.app.1066890 PID because 28304 has exited

For what it's worth, after a google search, their AI seems to think it's related to AMS2?

AppInfoManager.ProcessDisconnected: Clearing application steam.app.1066890 PID because 28304 has exited

"This log message indicates that the Oasis Driver (used for running Windows Mixed Reality headsets like the HP Reverb G2 on Windows 11 without the legacy Portal) has detected that a VR application or game (PID 28304) has crashed or closed unexpectedly.
The Oasis driver is attempting to clean up the temporary files and connection data associated with that specific application (steam.app.1066890) after it exited

 

Anyone here using a Quest 3 and experienced a second of black screen during normal use whether Virtual Desktop or link cable mode ? Just started happening two days ago, after more than two years of use without issues, now once an hour it just goes completely black for one second but then comes back on like nothing happened.

I do not know if it is AMS2 related or headset related because AMS2 is the only thing i play in VR. My specs are Windows 10, Virtual Desktop, 3060 Ti latest Nvidia drivers, Ryzen 7 3800X, 64 GB Ram.

 

I thought i was going crazy. It started happening right after Oculus outage last week and Oculus app update. As you said, it goes black a couple of seconds and it comes back.

 

Okay so based on what is being writte on the Virtual Desktop discord by DOZENS of people, i am pretty certain this is a new Oculus software/update bug that has just been introduced and has been happening for a week. Here is hoping there will be some update very soon to fix this right back !

 

Except for the fact I cant use OculusVR anymore, everything is fine with SteamVR for my Oculus Rift S

 

What codec do you use ? Somebody wrote :
"I was having the same behavior and then after switching from HVEC 10-bit to h.264 it completely stopped"

Also this discussion thread started on the VD discord.