Jump to content

Meta acknowledges bug with OpenXR API layers in v68

mbucchia

By mbucchia
in Virtual Reality

 Share

Recommended Posts

mbucchia

mbucchia

Posted
  • Author
Posted
27 minutes ago, baltic_dragon said:

Hey guys! Is it possible that this also affects my Reverb G2, as OpenXR is also used by WMR?

Definitely not 

I wasn't banned, but this account is mostly inactive and not monitored.

Hoirtel

Hoirtel

Posted
Posted

Well after the last meta update fiasco (v62-v63), I have taken the advice of someone in the thread from that and blocked oculus in and out of my firewall before it forced the update. No v68 for me. 

  • Like 1
mbucchia

mbucchia

Posted
  • Author
Posted (edited)
On 7/30/2024 at 11:03 AM, mbucchia said:

will be fixed in v69,

I have received signals that Meta is going to release a hotfix in PTC. Will still be v68<something>, but should have the particular fix to the issue.

Edit: I have now received users reports that the hotfix is live on PTC.

Edited by mbucchia
  • Like 3
  • Thanks 2

I wasn't banned, but this account is mostly inactive and not monitored.

sze5003

sze5003

Posted
Posted
5 minutes ago, mbucchia said:

I have received signals that Meta is going to release a hotfix in PTC. Will still be v68<something>, but should have the particular fix to the issue.

Funny I just set up sidequest today, loaded filemanager+ and disabled oculus OS updater app. Thanks for the info, once the update is out at least it will be an easy revert.

Asus ROG Strix Z790-E | Core i9 13900K-NZXT Kraken X73 AIO | 32GB DDR5 G Skill Neo 6600mhz | 2TB Sk Hynix P41 Platinum nvme |1TB Evo 970 Plus nvme | OCZ Trion 150 960GB | 256GB Samsung 830 | 1TB Samsung 850 EVO | Gigabyte OC 4090  | Phanteks P600S | 1000W MSI  MPG A1000G | LG C2 42 Evo 3840x2160 @ 120hz

Steel Jaw

Steel Jaw

Posted
Posted
11 hours ago, mbucchia said:

Edit: I have now received users reports that the hotfix is live on PTC.

What should the version number be?  Mine just updated and now says Meta Quest Link app version 68.0.0.433.361 (68.0.0.433.361)

"You see, IronHand is my thing"

My specs:  W10 Pro, I5/11600K o/c to 4800 @1.32v, 64 GB 3200 XML RAM, Red Dragon 7800XT/16GB, monitor: GIGABYTE M32QC 32" (31.5" Viewable) QHD 2560 x 1440 (2K) 165Hz.

mbucchia

mbucchia

Posted
  • Author
Posted
2 hours ago, Steel Jaw said:

What should the version number be?  Mine just updated and now says Meta Quest Link app version 68.0.0.433.361 (68.0.0.433.361)

Report said:

> The version of the Meta Quest Link app software with the fix is: 68.0.0.474.361

  • Like 1

I wasn't banned, but this account is mostly inactive and not monitored.

Steel Jaw

Steel Jaw

Posted
Posted

Thanks...anyone test this yet?

"You see, IronHand is my thing"

My specs:  W10 Pro, I5/11600K o/c to 4800 @1.32v, 64 GB 3200 XML RAM, Red Dragon 7800XT/16GB, monitor: GIGABYTE M32QC 32" (31.5" Viewable) QHD 2560 x 1440 (2K) 165Hz.

sze5003

sze5003

Posted
Posted
Thanks...anyone test this yet?
I can try it tonight but I'm skeptical. I just went through the process to roll back desktop oculus app to v67 files since it updated a while ago.

I also did the os update disabling on the headset. So if I go into PTC and it doesn't work I'll be screwed lol.

Asus ROG Strix Z790-E | Core i9 13900K-NZXT Kraken X73 AIO | 32GB DDR5 G Skill Neo 6600mhz | 2TB Sk Hynix P41 Platinum nvme |1TB Evo 970 Plus nvme | OCZ Trion 150 960GB | 256GB Samsung 830 | 1TB Samsung 850 EVO | Gigabyte OC 4090  | Phanteks P600S | 1000W MSI  MPG A1000G | LG C2 42 Evo 3840x2160 @ 120hz

Qcumber

Qcumber

Posted
Posted
42 minutes ago, Steel Jaw said:

Thanks...anyone test this yet?

Yes. It works for me. I can now run DCS with OXRTK and QVFR using meta cable link. 

PC specs: 9800x3d - rtx5080 FE - 64GB RAM 6000MHz - 2Tb NVME - (for posts before March 2025: 5800x3d - rtx 4070) - VR headsets Quest Pro (Jan 2024-present; Pico 4 March 2023 - March 2024; Rift s June 2020- present). Maps Afghanistan – Channel – Cold War Germany - Kola - Normandy 2 – Persian Gulf - Sinai - Syria - South Atlantic. Modules BF-109 - FW-190 A8 - F4U - F4E - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.

IMG_0114.jpeg

 

Steel Jaw

Steel Jaw

Posted
Posted (edited)

Well DCS runs again with OpenXR enabled, but the stutters in VR are still there.  Max FPS 36 whereas before I was getting 72.

Edited by Steel Jaw

"You see, IronHand is my thing"

My specs:  W10 Pro, I5/11600K o/c to 4800 @1.32v, 64 GB 3200 XML RAM, Red Dragon 7800XT/16GB, monitor: GIGABYTE M32QC 32" (31.5" Viewable) QHD 2560 x 1440 (2K) 165Hz.

FupDuck

FupDuck

Posted
Posted
20 hours ago, sze5003 said:

Funny I just set up sidequest today, loaded filemanager+ and disabled oculus OS updater app. Thanks for the info, once the update is out at least it will be an easy revert.

I think the issue is mainly with the desktop app, not the headset firmware. You need to block the link software from updating. There are instructions on the 3rd page of this thread

"...I just wanna fly; put your arms around me baby, put your arms around me baby" - Sugar Ray

RTX 3090, Ryzen 7 5800X3D, MSI MPG B550 Gaming mobo, 64 GB DDR4 RAM, 970 EVO Plus NVMe M.2 SSD 2TB game drive, VKB STECS Standard throttle, Winwing Ursa Minor Fighter stick, Oculus Quest Pro via ersatz link cable, Standalone DCS.

VR only.

 

sze5003

sze5003

Posted
Posted
6 minutes ago, FupDuck said:

I think the issue is mainly with the desktop app, not the headset firmware. You need to block the link software from updating. There are instructions on the 3rd page of this thread

Yea I found the blog post and followed the instructions to replace the v68 updated desktop app files with v67 ones. Now if I want to try the PTC update I need the desktop app to update again back to v68. But it is not triggering an update so I will need to uninstall it and reinstall I suppose.

Asus ROG Strix Z790-E | Core i9 13900K-NZXT Kraken X73 AIO | 32GB DDR5 G Skill Neo 6600mhz | 2TB Sk Hynix P41 Platinum nvme |1TB Evo 970 Plus nvme | OCZ Trion 150 960GB | 256GB Samsung 830 | 1TB Samsung 850 EVO | Gigabyte OC 4090  | Phanteks P600S | 1000W MSI  MPG A1000G | LG C2 42 Evo 3840x2160 @ 120hz

BazzaLB

BazzaLB

Posted
Posted (edited)

I'm not on any PTC but my Meta app updated itself to 68.0.0.474.361 yesterday morning so I can only assume they already rolled out this hotfix publicly. This seems to have fixed any issues I had with OXRTK.

Edited by BazzaLB
  • Like 1
diamond26

diamond26

Posted
Posted

I can confirm the fix is on public release and works as intented. Thanks @mbucchia and eventually Meta who for once responded properly (despite being late)

  • Like 1

MAIN SYSTEM SPECS: MSI PRO Z690-A WIFI DDR4, Intel Corei7-12700K @ 5.0, 64Gb RAM Kingston KF3600C18D4/16GX, EVGA RTX 3080 FTW3 ULTRA GAMING 12GB, Samsung SSD 970 EVO Plus 1TB, Virpil T50CM3 Throttle, VKB Gunfighter MkIV Ultimate with 20cm extension, VKB T-Rudder MKIV, Quest Pro

Laptop SPECS: Alienware X16 R2, Intel Core Ultra 9 185H, RTX 4090 mobile 16GB, 32GB LPDDR5X, 2TB Micron NVMe
 

SOFTWARE: Microsoft Windows 11

DD_Crash

DD_Crash

Posted
Posted

My Quest 3 link cable has stopped working. It ran fine yesterday afternoon but in the evening an error report said "some features of meta link are temporally not working". I have tested the cable connection which has 2.8 gbs but the desktop isnt visible. Anyoe else having issues?

slughead

slughead

Posted
Posted
1 minute ago, DD_Crash said:

My Quest 3 link cable has stopped working. It ran fine yesterday afternoon but in the evening an error report said "some features of meta link are temporally not working". I have tested the cable connection which has 2.8 gbs but the desktop isnt visible. Anyoe else having issues?

Have you tried:

a) restarting the Meta Link app on the PC

b) disconnecting and reconnecting the cable

c) rebooting the PC

d) rebooting the headset

Slugmouse: a finger-mounted mouse button emulator for hand-tracked VR cockpit clicking. Available now!

Slugmouse Demonstration Video

 

signature.jpg

DD_Crash

DD_Crash

Posted
Posted

Yes to all of the above. My router is too far away, the headset sees it but it doesnt meet all requirements. Is there anyway of forcing a reinstall of the software?According to what I saw it said version 67. but no updates where available. Thanks for your interest.

slughead

slughead

Posted
Posted
4 minutes ago, DD_Crash said:

Yes to all of the above. My router is too far away, the headset sees it but it doesnt meet all requirements. Is there anyway of forcing a reinstall of the software?According to what I saw it said version 67. but no updates where available. Thanks for your interest.

I’m confused. I thought this was about meta over cable.

Slugmouse: a finger-mounted mouse button emulator for hand-tracked VR cockpit clicking. Available now!

Slugmouse Demonstration Video

 

signature.jpg

DD_Crash

DD_Crash

Posted
Posted

It is but I want to see if the headset could connect over wifi. I might try the PTC and see if that works. It was running very well so I know the cable is good and dont want the expense of a router and VD. The version I have used to work over the cable.

Phantom711

Phantom711

Posted
Posted (edited)

@DD_Crash

After the last update of the Meta PC app, I had a warning that there was no audio to the headset (QuestPro). I checked in Windows Device manager and for some reason the Oculus Audio and Mic was disabled in Windows. Enabled them and all was good.

Maybe your problem/solution might be similar?!

Headset software is still v67 and there is no newer one apparently. Meta PC App is the hotfixed v68.

Edited by Phantom711
  • Thanks 1

 vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.

image.png

 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...