dutchili

The taxi lights appear in really impractical places at Pferdsfeld. Near or on crossings.

actually, since april 25 or even before if other got updates before that.

From meta support: Greetings from Meta Store Support. We sincerely appreciate your continued patience as we work to resolve the PCVR error affecting v76. We truly apologize for the inconvenience this software update has caused and understand how frustrating this situation has been for you. As a gesture of goodwill for the time and effort you have invested in reaching out to us, we would like to offer you $10 Meta store credit to help compensate for the disruption. If you are interested in redeeming this, please provide the following account details: Full name as it appears on your Meta account Current alias/username as it appears on your Meta account Email address linked to the account This store credit can be applied toward any digital purchase within the Meta Store, including apps and games available for PCVR. In the meantime, we recommend keeping an eye out for upcoming updates on Quest headsets, as we continue working toward a resolution. You may visit this link: Meta Quest release notes to monitor future software updates. Thank you for your understanding and patience. If you have any further questions or need clarification, please feel free to reach out. We are always happy to assist you.

Which software version do you have on the headset? I have 76.1025 it still randomly disconnects with VD when playing DCS.

i just tried DCS in 2D, with the headset connected, DCS still crashed. The OVRservice log indicated it concluded the Headset was not connected, then the system hung....

Meta is requesting to send a bug report from the headset when this happens, or you cannot connect to the PC. It is only a few clicks from the Oculus Dashboard. After installing "2025-05 Cumulative Update for Windows 11 Version 24H2 for x64-based Systems (KB5058411)" earlier tonight i played for just over 45 minutes without a crash. I came from the 24H2 preview. I will test more tomorrow. (headset firmware: v76.1025. Meta Quest Link on PTC with version 77.0.0.574.329). So far such delightfull moments have been a one-time-off-lucky-event.

Hahaha. Now go back up again and check the version in your headset too

Version number of Meta link app and firmware?

The joy was short lived...

Played for just over an hour without crashes. However, the anti-aliasing doesn't seem te be working as it used to. Jagged lines.

I have received an update tonight in the PTC channel (Beta). Version number was not updated and is still 77.0.0.574.329, however, I played for 25 minutes without a crash. Hopefully not issues after rebooting and trying again tomorrow. Headset still on 76.1025

In my case the Oculus log files, which you can retrieve by starting the OculusLogGatherer.exe in the diagnostics folder, producing output to your desktop, indicate that the USB connection is lost. When using airlink, the connection to the device is lost too. As a result all operations on the headset fail. Due to lack of exception handling, the system hangs and my dumpfile indicates the GPU was unable to write to some memory address.

v76.1025 dropped on the headset, but no change.

VD din't work for me either since this issue exists

Good news on my initial test after following this meta support advice: - Set meta quest link app to 'non beta'. - set headset to NOT apply automatic software update - factory reset the headset (via the meta horizon app) - don't update after the factory reset. - my meta quest link is now on 76.0.0.452.315 - my headset is (back) on v76.0 (i had v76.1023) - i played DCS for over 10 minutes without the link or pc crashing. - the windows event viewer is still flooded with 'OculusVadApoEventTrace' errors, but yet it worked fine. Love to hear if it works for you too. btw: still need to manually restart the OVR service to get meta quest link to work. Meta acknowledged that 'there is a potential issue with v76 and PCVR'

I've been in contact with ED support and Meta support on this issue. The OVRserver log and oculus dash log reveals a deadlock, meaning the main rendering threat hangs. It seems very much to be an Oculus bug in either Dash (the virtual dasboard you see before switching to the windows desktop) or OVRserver. It correlates with the issue of the Meta Link App no longer starting at Windows start (which can be fixed by going to 'services' in Windows and restart the oculus vr service. Then starting meta quest link). However, getting meta quest link to work does not fix 'this' issue. I delivered the meta logs to Meta in an email chat with support, but it is the developers that need to fix it.

Can't find the answer to the following using search: Is ILS working on the map? I get an annoying static near Hahn and can't the any of the frequencies for Ramstein, Hahm, Pferdsfeld and Spangdahlem dialed in. The frequency is not accepted on the DED.

Temp fix is to: - rename mission to .zip - copy the mission file to your desktop - edit the mission file - search for bullseye - replace the x and y location for the 'blue' to ["y"] = -823001.91645693, ["x"] = -482860.00940784, - save the file - copy the file back to the zip archive - rename the .zip to .miz again - your blue bullseye will show-up near Wiesbaden

I have noticed this too with the Russian assets. Adding + in the ME puts some of the units on top of each other, unable to separate them. I love the content, but also had these issues: - can't find info om max ceiling of SAM units - F-16C HTS pod does not detect Russian SAMs (RWR does after applying that mod) - performance in CWG map combined with VR is downgraded significantly. I don't really understand how that works, but the ground textures are no longer fluent when performing rolls, both low-level flying and FL250, even when not facing the units. Is there a fix for the above? I'd really like to use those new SAMs and Artillery

Thanks @BIGNEWY for hotfixing this so quickly! (haven't tested yet, but already happy with the intentions)

Would this be AI or Map related? Area H FRG 51. Could not set 'on road' in this area althoug there are visible roads. The units drove past the bridge, through the water and then....well..you can see what happened.

Noted that this is a known bug in this version. @BIGNEWYplease don't release known issues is key features of a module. We can't do without them.

+1. Have seen this too with a quest 3, 4090 and max settings

Before the April 17th update, we could change the FCR range by slewing the RDR cursor to the top or bottom of the MFD. The range would immediately change. Now, the cursor stops at the edge. To change the range with the cursor, you need to move the cursor back away from the edge and try again. Then the range changes. Seems related to the change log item: 'Fixed: RDR Cursor movement axis bug.' @BIGNEWYIs the current behavior as intended? I like the feature of not changing the range unintentionally while trying to lock a target at the current set range, but the behavior seems a bit incosistent now. Not posting a track, assuming you have test scenario for this basic FCR operation.

yeah, i do see spikes in those times when looking around or manouvering. It only becomes annoying when flying low over cities. All other situations are classified by me as 'not perfect, but not hindering gameplay'. I do notice that a perfectly smooth gameplay make a big difference in perception: smooth = :), stutters are I think (assumption) that the core of this issue is in how the rendering works / is linked to other computations / I/O. Especially in VR. Reported frame rates in 2D are much higher, yet you see the exact same issues