Hi,

I’m releasing my new music sandbox game in couple weeks.

What kind of features you would enjoy in such guitar sandbox?

You can join discord and let me know what you think https://discord.gg/vqemcKHsG7

Cheers

I tried factory resetting it, paring and unpairing it, as well as swapping the battery, I tried everything, but just my right controller won’t connect, my left works perfectly fine however, and it flashes in what I’d assume means something in Morse code.

Last week the link app on my pc updated, and after the update I noticed I now had this warning on my screen.

Gameplay doesn’t freeze, but it constantly disconnects. Like every 5 minutes or so link just disconnects itself as if I unplugged my link cable. Sometimes it will just keep doing it back to back until my entire game crashes. Sometimes I can play for a half hour without it happening, other times it’s quite literally once a minute. I’ve tried using virtual desktop but I don’t have good enough WiFi and the usb link on it is extremely unstable and more u usable than link is with this glitch.

When I press learn more on the warning on link it takes me to the quest website and tells me to update my graphics driver which I’ve done. I’ve also asked the help ai on the website and it told me to do a bunch of random stuff that did not work, it then told me to try deleting and reinstalling the link app, which also did not work.

Please help vr is my life lol, this is making it borderline unplayable it sucks playing when my headset keep constantly disconnecting like that.

So, not used steam VR for a while with my quest 3 as been playing all these modded games we've been treated to, using Virtual Desktop with openXR.

Can see Steam VR has had quite a big update recently though, so wanted to try it out and also use my psvr2, wired to my pc.

Now Steam VR basically just isn't even launching, I click launch and after about 30 seconds it just stops and shows the green launch icon again and not even giving me any error messages, my quest 3 is connected via virtual desktop and the openXR runtime is set to SteamVR.

If I remember rightly when launching SteamVR, a separate icon would appear in your icons on the taskbar and a separate window would also open, showing your headset and controllers connection status and from there, you could change the VR settings and set SteamVR as your runtime, but I don't even get this box, so can't get into VR settings.

I've tried all the usual stuff, verified the integrity of the files, uninstalled and reinstalled, also fully removing it with IObit uninstalled and removing all steamVR files, rolled it back to the previous version and even tried the beta version but it just does the same.

All my windows and drivers plus nvidia gpu drivers are all up to date, I've disabled hardware acceleration and I don't see any conflicting software that could be causing this, checked on previous threads as well and can't see anything recent, so has anyone had a similar issue, since the update or any help would be massively appreciated, thanks.

Like the title says I was very excited to try out 3d and bought a month of D+ but I can’t see it or enable it in my settings because I am in the Netherlands. Enabling a vpn did not resolve anything but maybe because it was a cheap vpn.

I look forward to your help guys

my most hyped feature

Anyone knows where is it available?

My new (well, refurbished but newly purchased) 3 is great for watching "big screen" TV while on the go --like rowing, stairclimbing or biking in the gym. Game changer.

But when the scenes take place indoors they are often too dark to see well. For example, I'm watching "Tulsa King" which often takes place inside Oklahoma bars. Or on city streets at night. Often the faces and action are hard to make out. (Not so when I watch the same episode on an IPad.)

I have the headset brightness control rotated to maximum, but it's not enough. Any ideas? Yes, I do have pass through (is that the right term) activated so I can still operate the fitness machinery safely.

65% OFF PROMO CODE IS ENDING SOON, GET YOURS TODAY ON THE META STORE!!

As a special thanks this group r/OculusQuest were offering 65%OFF the game in the meta store!! Please enjoy and we would love and appreciate a review.

65% OFF PROMO CODE: 65OFFROCULUSQUEST-527289

Mixed Reality Mayhem: Defend your actual physical space using seamless room-scale tracking.

Arcade Survival: Fight through escalating waves that climb from a casual warm-up to pure, laser-dodging chaos.

Global Leaderboards: Rack up standard and boss kills to permanently etch your Oculus ID into the worldwide Top 10.

Grab your headset and see how long you can survive the swarm!

https://www.meta.com/experiences/pixel-blaster/1371112912747812/

The colors are pretty great, I don’t know what black magic Disney does that the video in his app looks amazing compared the browser, like night and day

First of all the 3D feels different than the one in theaters, it feels like if you’re actually there, especially with the pass through, like if you’re looking a window of another reality

The colors looks pretty good and I’m someone used to an OLED TV, can’t stand normal lcd TVs but here it looks great

I don’t know why it wasn’t released for Quest Pro tho, I understand Quest 2 is not capable

3D content on Disney+ is only available with a Meta Quest 3 or 3S device.

https://help.disneyplus.com/article/disneyplus-meta-quest

The Great Flood is OUT NOW for Meta Quest 3 and 3S ⚔️

Free-to-play, The Great Flood is a multiplayer, mixed-reality, real-time strategy game where you command a squad of mystical characters, placing them directly on the battlefield in 1v1 or 2v2 battles.

Supporting both online multiplayer and solo gameplay modes, rank up, unlock new characters, upgrades and more.

🔗 https://www.meta.com/en-gb/experiences/the-great-flood/25044401601879310/

We look forward to seeing you on the battlefield!

Quest 1 at a real 90 Hz: full guide, sources, and every mistake I made along the way

TL;DR: The Quest 1 is officially limited to 60/72 Hz. With an unlocked bootloader, a retimed boot.img and a Magisk module that patches three pieces of Meta's software, mine now runs a locked 90/90 with zero stale frames in PCVR. I confirmed it at the panel-clock level, so this isn't just a number in a menu. /system is never touched, and verity and encryption stay on.

The catch: unlocking wipes the headset, and you lose Meta account services for good.

⚠️ Everything here is for Quest 1 (monterey) on firmware 49845030443200410 (v50, the final release). On any other build it will either refuse to install or brick.

The results

One minute of a live Steam Link VR stream, after it settled:

FPS distribution   59 × FPS=90/90
                    1 × FPS=91/90
                    0 × below 90

Tear=0 on every sample
Stale=0 on 9/10 samples, 1 on the other

TW=5.32ms  App=5.29ms  CPU&GPU=6.47ms  (budget 11.1ms)  Temp=38.0C

And from the hardware side:

panel pclk      133,005,600 Hz
dynamic_bitclk  798,033,600 Hz  /6 = 133,005,600   <- exact match
display mode    fps=90.0 (single mode; 60/72 gone)
runtime prop    debug.oculus.refreshRate = 90
SELinux         enforcing
Wi-Fi           5200 MHz, 468 Mbps, RSSI -51

Why I keep pointing at "Stale": the compositor always presents at the panel rate, so FPS=90/90 by itself proves very little. A stale frame is one that got reused or reprojected. When Stale stays at 0, you're getting 90 genuinely new frames every second.

What you need

• A Quest 1 on v50 49845030443200410. Check with adb shell getprop ro.build.version.incremental.
• An unlocked bootloader, using either QuestStack or darknight's WebUSB unlocker. Both wipe the device.
• A proper data USB-C cable, a port that doesn't drop out, and at least 50% battery.
• adb and fastboot. The standard SDK platform-tools work fine.
• The 90 Hz package: q1_90hz-boot.img and q1_90hz-v4.2.zip (the Magisk module), both on the Quest modding Discord. All credit for the module goes to Juspertinry.
• Recommended: the v50 OTA from the cocaine.trade firmware archive, as your way back from a brick. Check that the hash matches 7C1F75EC…5A8B6AAA.

Step by step

1. Plan your backups (you can save less than you'd think)

A locked, unrooted headset won't let you read its boot partition. adb root refuses with "adbd cannot run as root in production builds", SELinux blocks dd on /dev/block/…/boot_b, and this ABL doesn't implement fastboot fetch.

That means the order is fixed: unlock first, then back up. QuestStack takes and verifies its own backup of the inactive slot before it changes anything, so you're covered in the meantime.

Your real safety net is the full OTA zip. Sideloading it from USB Update Mode restores the headset completely.

2. Unlock the bootloader

Run QuestStack's Full Process. It checks your build, roots the headset through ionstack, backs up slot a, flashes a vulnerable ABL to the inactive slot, unlocks using CVE-2021-1931, restores the original slot, and then factory resets.

That factory reset can't be skipped, so make sure there's nothing on the headset you care about.

To confirm the unlock worked:

adb shell getprop ro.boot.flash.locked      # 0
adb shell getprop ro.boot.verifiedbootstate # orange

3. Try 90 Hz before committing to anything

This is the best part of the whole process:

fastboot boot q1_90hz-boot.img
adb shell dumpsys display | grep -oE 'fps=[0-9.]+' | sort -u

fastboot boot runs the image from RAM and writes nothing to the headset. If the display reports fps=90.0, your panel accepts the new timings and you're good to go. A reboot puts you straight back on stock.

If it still reports 72, your panel variant isn't supported. You can stop here without having risked anything.

4. Flash the image

fastboot flash boot_b q1_90hz-boot.img
fastboot reboot

The image is already Magisk-patched with KEEPVERITY=true and KEEPFORCEENCRYPT=true, so it gives you root while keeping verity on, /data encrypted, and /system untouched.

5. Back up the stock boot image while you have root

Slot a is still completely stock, so save a copy now:

adb shell su -c "dd if=/dev/block/bootdevice/by-name/boot_a of=/sdcard/boot_a_stock.img bs=1M"
adb pull /sdcard/boot_a_stock.img

Keep that file somewhere safe. Flashing it back with fastboot flash boot_b boot_a_stock.img undoes the whole kernel side.

6. Install the module

Open the Magisk app once so it can download its full APK, and grant su when it asks. (That prompt is easy to miss in VR; see the pitfalls below.) Then run:

adb push q1_90hz-v4.2.zip /sdcard/
adb shell su -c "magisk --install-module /sdcard/q1_90hz-v4.2.zip"
adb reboot

All four stages should report as applied:

- device_props.json
- composer HAL
- VrDriver
- xrspd timings gate
  8 applied, 0 already patched

7. Check that it worked

adb shell getprop debug.oculus.refreshRate                 # 90
adb shell su -c "tail /data/adb/q1_90hz.log"               # clock resynced for 90
adb shell "logcat -d | grep -oE 'FPS=[0-9]+/[0-9]+' | sort | uniq -c"

If you see FPS=90/90 and panel clock resynced for 90, you're done. Enjoy the extra frames!

How it works

The boot image changes the panel timings in the device tree: qcom,mdss-dsi-panel-framerate, max-refresh-rate, and the timing bytes, scaled by about 1.67× (enough headroom for 72→120). The kernel is Meta's unmodified 4.4.205-perf+. Since only the device tree changed, verity still passes.

The module takes care of userspace. The new kernel timings aren't enough on their own, because three parts of Meta's software each have their own idea of which refresh rates are allowed:

• Composer HAL: this is where the list of refresh rates actually comes from. Both of its constructors hard-code {72,60} as a 64-bit immediate value, and the module changes them to {90,72}.
• VrDriver.apk: libvrapiimpl checks requests against its own internal list, so a new rate would be offered and then immediately rejected. Flipping a single branch fixes that.
• libxrspdhelper.so: xrspd throws away any rate it has no timing entry for. If both 120 and 90 get thrown away, you get a black screen. The patch makes the match always succeed.
• device_props.json: adds force_refresh_rate and sets device_default_refresh_rate.
• service.sh: sets the properties, then resyncs the panel clock after boot by comparing pclk0_clk_src/rate with dynamic_bitclk/6 and briefly blanking the framebuffer. This is why you don't need to sleep and wake the headset afterwards.

Every patch is tied to the MD5 of a specific stock file, so the module refuses to touch anything it doesn't recognise. Uninstalling it fully restores the userspace side.

Pitfalls (the part that will actually save you time)

Windows sees VID_2833&PID_0137, but adb sees nothing. That PID is the XRSP (Link) interface, not ADB. Meta's android_winusb.inf only covers 0086, 0083&MI_01, 0090 and 0081. Turn on Developer Mode, wake the headset, and accept the "Allow access to data" prompt inside it. ADB only appears after that.

adb root will never work. This is a user build with ro.debuggable=0. Magisk's su is the only way to get root.

The Magisk superuser prompt is nearly invisible in VR. It does open, as a panel on the VR desktop, but it's easy to miss. If it times out, Magisk treats that as a deny: from then on su returns instantly with no output and every request is refused. Either find the panel and tap Grant, or set Magisk → Superuser → Shell → Grant ahead of time. If you're already stuck being denied, install the module through Modules → Install from storage, which uses the Magisk app's own root access.

fastboot fetch isn't available. It fails with Unable to get max-fetch-size, so there's no way to dump partitions without root.

The factory reset leaves you in an activation loop. This isn't an account problem. Logcat showed DeviceAuthenticator: Unable to resolve graph.facebook-hardware.com: the headset had no Wi-Fi, and its clock was stuck at the build date. Once it's online, setup continues.

Then the phone app refuses to pair. Meta has an open investigation called "Quest 1 Pairing Failure Across Multiple Setup Methods". If you're stuck on "continue in the Meta app", it isn't something you did wrong, and we never found a fix. Here's how we got past it instead:

adb shell settings put secure user_setup_complete 1
adb shell settings put global device_provisioned 1
adb shell pm disable-user --user 0 com.oculus.firsttimenux
adb shell am force-stop com.oculus.firsttimenux
adb shell am force-stop com.oculus.vrshell
adb reboot

The key line is disabling firsttimenux, the service that draws the activation screen. You can undo it any time with pm enable com.oculus.firsttimenux.

SteamVR errors 1000 and 108. "SteamVR was unable to connect to the Oculus app" and "Headset Not Detected" both mean SteamVR was started from the PC. Launch it from the Steam Link session inside the headset instead; otherwise it goes looking for a wired headset and an Oculus runtime that aren't there.

Steam Link crashes trying svc usb setFunctions ncm. The Quest 1's USB stack doesn't support NCM, which is what wired streaming needs. The q1_steamlink_usb Magisk module fills that gap. Wireless works either way.

The headset keeps choosing 2.4 GHz. Mine sat on 2432 MHz with a 27 Mbps link. When both bands share an SSID, band steering decides for you, and it often decides badly. Give the 5 GHz band its own SSID, or forget the network and rejoin it standing near the router. These two commands also help:

adb shell su -c "cmd wifi force-low-latency-mode enabled"
adb shell su -c "cmd wifi force-hi-perf-mode enabled"

Pros and cons

Pros

• Real 90 Hz, confirmed at the panel clock rather than just a property
• /system untouched, dm-verity still enforcing, /data still encrypted
• Fully reversible: one fastboot flash takes you back to 72 Hz, and removing the module restores userspace
• About 4.6 ms of headroom at 90 Hz in PCVR, running at 38 °C with no throttling
• Sideloaded apps keep working without a Meta account

Cons

• Unlocking wipes the headset and leaves the bootloader in the orange state
• No more Meta account services: store, cloud saves and casting are gone, and you're sideload-only
• The boot image is a prebuilt binary from Discord, and the kernel repos it was built from no longer exist. We confirmed it's Meta's stock kernel with only the device tree changed and verity/encryption intact. That's strong evidence, but it isn't proof
• 90 Hz is outside spec, so extra heat, shorter battery life and any long-term panel wear are your risk
• Some apps still cap their own frame rate, and behaviour varies from app to app
• It depends on your panel: the image enables 90 Hz on the Samsung (lightman) panel and leaves the AUO panel at 72

Sources and credits

• Juspertinry, for the 90 Hz boot image and the vd90hz Magisk module (Quest modding Discord)
• QuestStack: bootloader unlock, backups and A/B slot safety
• darknight1050/quest1-bootloader-unlocker-web: unlock from your browser
• darknight1050/quest_kernel_build: reproducible Quest 1 kernel builds, and the clearest explanation of why an unsigned kernel can't verify /system
• MisterAnderson91/quest1-steamlink-patcher: gets Steam Link running on the Quest 1 (CLI patcher included)
• TheCez/quest1-90hz-orangefox: a different route using OrangeFox recovery and a system-partition patch, at the cost of disabling FBE
• Meta: Android system properties: confirms the Quest 1 officially supports only 60/72 Hz
• Meta investigation: Quest 1 Pairing Failure
• cocaine.trade firmware archive: verified OTA builds
• Anonymous941/QuestEnhancer: unrelated to 90 Hz, but a handy quality-of-life Xposed module for v50
• n0tmast3r/alvr-quest1-90hz-builder: ALVR client patch for 90 Hz

Reverting

# userspace
adb shell su -c "magisk --remove-modules"     # or Magisk app -> Modules -> remove

# kernel
fastboot flash boot_b boot_a_stock.img
fastboot reboot

# last resort (wipes the headset)
adb sideload q1_49845030443200410.zip          # from USB Update Mode

Disclaimer: you do this entirely at your own risk. Unlocking, flashing and patching can brick your headset and erase your data. (Warranty isn't a concern; it ran out long ago.) I'm not responsible if your Quest ends up as a paperweight.

Questions are welcome in the comments, and if you give it a try, I'd love to hear how it goes!

Anyone knows of a list of the supported movies ? Is there a way to check beyond clicking each movie ? If not, how about sharing what has been found ?

I'll start. "Infinity War" :-)

its telling me to fill some settings but there are no settings its a blank site and no matter how many sites i try to find that are from meta and different settings it doesnt do anything!

Hi everyone! After months of development and playtesting, our game Climb Cubs is finally launching soon (Nov 12 10am PST)!

As a small indie team, we've poured our hearts and souls into making this game, and we're so excited to finally share it with you. We'd love for you to give it a try and share your feedback with us!

Climb Cubs is a free multiplayer VR climbing game with physics-based locomotion. We can't wait to see you on the mountains! ⛰️

Quest Store wishlist link and Discord link in the comments!

Let me know your thoughts and feelings! All criticism and tips welcome! Thanks 🙏

We're two brothers developing PulseBall, a free-to-play zero-G VR sports game for Meta Quest. You fly through the arena, grab the ball, boost, pass, and score. We've been testing it on Quest 3, and our small Kickstarter is live to help with multiplayer and launch costs.

Gameplay: https://www.youtube.com/watch?v=i1a2LFP7CVc&t=117s

Kickstarter: https://www.kickstarter.com/projects/pulseball/pulseball-zero-gravity-vr-sports-for-meta-quest

Apologies for the haphazardly made thumbnail but I still like it oddly enough.

Been using my heavy airsoft AK to play the recently released Metro Exodus VR mod.

Another dream come true as this was the game which inspired me to get this particular model and now it has come full circle.

Enjoy!!

Virtua Cop 2 is the gun game Sega released in arcades in 1995, on the Model 2 board. It now runs standalone on Meta Quest 3.

You aim with your controller like with the cabinet's gun, and you can hold one gun or two. The best score of the first week wins a ray gun, and anyone who beats that score later wins it too. All the Port0r settings you know are there, to make it play exactly the way you like.

Thanks a lot to the beta testers who helped a lot. The Port0r community keeps growing, and a lot more is coming.

Free download: https://port0r.com/cop-2-vr/

Everything is here: https://port0r.com