Jump to content

Recommended Posts

Posted

I bought a Pixel Crystal Light...
- i love the resolution, close to 2D experience
- switching between game and 'desktop' is instant
- sound of non-DMAS speakers is....better buy the DMAS speakers too
- tracking is not as good as the quest. I have issues when looking at my F-16 wingtips. Could be due to my background. Besides this position, it is perfect and better 'smoothened' than the quest, which you will notice when aligning the JHMCS in the Viper.
- quality upon delivery was not perfect. Had to correct contrast and brightness of the individual panels, throught the normal software, to balance left and right. One dead pixel in the right panel, no response from customer service on these issues for 3 workdays and a weekend.
- setup was 'click and play' instead of those Quest 3 unwanted intro's and safety wizards.
- wearing comfort is much better than the Quest 3. It is heavier, but feels lighter.
- i get the best performance at 72Hz, quadviews FOV rendering, high(est) resolution. Low-level FPS depends on the map and visible distance setting, FL006+ is steady 72 Hz (and perceived as fluent). The 90Hz setting only works for me with Pimax upscaling enabled, but that comes at the cost of less crispy views.

- the asferical lenses have a sweet spot. The pancakes from the quest have better 'edge to exge' sharpness. It took some time to learn to turn my head more, than just the eyes. Ther is also more chromatic abberation, comparable to a quest 2. Primarily visible with high contrast and red colors.

 

Summary: not going back to the Quest 3.

  • Thanks 1
Posted
4 hours ago, Jar_VFA-113 said:

the visuals still aren’t as nice as with the link cable.

It would be worth making sure you are comparing like for like. I find that the quality is equal between VD and link cable as long as both are set to the same resolution and have the same degree of sharpening. Also worth considering is the quality of you connection in VD.

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 - F4 - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.

_A644840 (2).jpg

 

Posted
В 27.05.2025 в 08:34, Jar_VFA-113 сказал:

I bought a new router and flew in Virtual Desktop for a bit which was nice but the visuals still aren’t as nice as with the link cable.

Similar here with the picture quality in VD, the difference only I'm using hardwire connection through USB-C/Ethernet adapter. Agree, the picture quality was better with Quest Link, still playing with VD settings in order to get similar to Link and hoping that meta will fix the link issue in this century at least ...

 i9-11900K, MSI MAG Z590 TORPEDO, DDR4 32,0GB RAM, Gigabyte RTX3090, Samsung SSD 980 PRO 2TB, Quest 3, standalone DCS.

Posted (edited)
On 4/28/2025 at 9:31 PM, Tensorial_Architect said:

When the sh#tz developers at Meta fix one bug they often introduce two new ones. Go to Control Panel -> Device Manager -> Expand the "Display Adapters" sub-section -> Right click on the "Meta Virtual Monitor" -> Choose "Uninstall Device" -> Click Confirm

Now, repeat the process for "Human Interface Devices" sub-section by clicking on every single grayed out HID-compliant consumer control device and uninstalling those as well (this will not hurt anything on your desktop rig).

image.png

 

Now, reboot your rig and reboot your Quest 3 (with it attached to your desktop computer by the Quest Link cable). Device manager will create new entries for you. 

There is a roughly 70% chance that your Quest 3 will be back to good working order.

Hi all, I'm sort of glad to see I'm not alone with this problem. I just bought a quest 3 recently and the link cable is not working (tried literally everything else, even replacing the link cable twice, and the headset). Only thing I haven't done yet is uninstalling these HID-compliant consumer control devices. 

You're description says to click on every single "grayed out" one. But none of mine appear grayed out. Should I still try uninstalling them, or will that screw up something else of mine? 

edit: I've have done ALL of the Meta support suggestions - over the course of about 20 emails and 5 days. Now they say they are passing the problem up to a different team to look for a solution (year right). And when I say they, I mean whatever chatbot was responding with generic text. 

about 1 in 20 tries and my headset works. Never tested it for more than about 10 minutes, because by the time I get it going I have no time to play anymore. If I simply disconnect and try to reconnect it doesn't work again. Getting all kinds of different errors. Failing to find my PC, thinks the cable is USB2, freezing on loading screen in headset, freezes as soon as the desktop (grey grid-like room) loads with glitchy borders, disconnects immediately, disconnects after a few seconds or minutes. i7-13700KF, 32 GB 5600 DDR5, RTX 4070, Windows 11. 

Seems I'll be trying Virtual desktop, only problem is I can't plug my computer into my router because it is on the ground floor. But I see there is a way to use a dedicated router just for VD even when the PC is connected via wifi to the internet. 

In any case, good luck all who have this problem. Maybe I'll ask meta for a 10 euro voucher for my troubles. That will solve everything. 😉

Edited by Kozo1
Posted (edited)
29 minutes ago, Kozo1 said:

 

Seems I'll be trying Virtual desktop, only problem is I can't plug my computer into my router because it is on the ground floor. But I see there is a way to use a dedicated router just for VD even when the PC is connected via wifi to the internet. 

In any case, good luck all who have this problem. Maybe I'll ask meta for a 10 euro voucher for my troubles. That will solve everything. 😉

Yeah, mine is screwed up too and I switched to VD. Works great. You CAN use a second router connected to the PC your running the game on. My home router is downstairs and my gaming PC is upstairs, about 75feet of cable would be needed to snake it around the house. Screw that. You DON'T have to physically connect the two routers though. It's called Internet Connection Sharing. I bought my router and followed these directions. Works just fine: https://github.com/Crayphish/vrdocs/wiki/Internet-Connection-Sharing . 

Edited by BluesRocket
clarity
  • Like 2

Alienware Aurora R16,  i9-14900KF, Crucial Pro RAM 64GB Kit (2x32GB) DDR5 5600MHz, NVidia 4080 Super with 16GB, 2TB SSD (Windows 11) and 2TB SSD (DCS)
Alienware 34" Curved QD OLED Gaming Monitor AW3423DW

Meta Quest 3 for VR with Virtual Desktop via AXE5400 router
VKB Gladiator NXT EVO SCE right hand, VKB Gladiator NXT EVO Omni Throttle left hand, VKB pedals
HF8 Gaming Pad with SimShaker for Aviators

Posted
9 hours ago, BluesRocket said:

Yeah, mine is screwed up too and I switched to VD. Works great. You CAN use a second router connected to the PC your running the game on. My home router is downstairs and my gaming PC is upstairs, about 75feet of cable would be needed to snake it around the house. Screw that. You DON'T have to physically connect the two routers though. It's called Internet Connection Sharing. I bought my router and followed these directions. Works just fine: https://github.com/Crayphish/vrdocs/wiki/Internet-Connection-Sharing . 

Great! Thanks for the link - this is just the instructions and confirmation I was looking for before purchasing a new router.

Posted

Thanks to everyone in this thread helping me keep plugging away at this, great info everyone thank you.

Switched to new router and Virtual Desktop and have been enjoying DCS again without constant fear of disconnects. I even bought the meta battery strap and flew for over 3 hours on the weekend without charging and still had an hour left I think of battery so that’s pretty awesome to be totally unplugged.

Was talking to other pilots in the Stingers as we have all had VR from CV1 day one and it worked much better back then ha ha.

Some of our guys are still on the older headsets (CV1/Samsung Odyssey/Reverb) and are enjoying solid DCS performance. Not sure why it’s so hard for Meta now but it’s very frustrating.

But yeah I’ll keep and eye out for updates but just for info I gave up and switch to VD / wireless and it’s working good.

  • Like 2
Posted

I have a quest 2 on link cable and i make it run by "end tasking" all related to meta in task manager (win10), then starting the link app, exiting it, and again do end tasking all and starting link app for a secound time. 

Next, start the hedseat, connect link cable, activate link. 

And in 50% cases i need to do a even third end tasking-restarting process because link exits on it's own after a few secounds.

Turn off headset, diconnect cable, do end tasking, start app, start headset, connect cable, activate link from headset

Then it runs normally for hours. 

AMD 5800X3D, RTX 4070ti super, 32Gb DDR4, 2Tb nvme m2, Win10, Quest2 on link cable with max resolution (slider all right) , OTT profile with 0,8 h&v fov reduction, QVFR (h&v focus size 42%, foviate res. 145%, periph.res. 18%), DCS settings all ultra and high, PD 1.0, DLAA, No hangar mod, and usually maintaining 72Hz.

Posted (edited)

Link also for me starts to make problems. Yesterday all of a sudden while on landing configuration it juste stopped working, pushed me back to the home screen. 

I did not had any time to reproduce that because I immideately switched to VD because I know it just works. Performance is poorer than with link but it works. 

 

Am 2.6.2025 um 09:28 schrieb Zligor:

I have a quest 2 on link cable and i make it run by "end tasking" all related to meta in task manager (win10), then starting the link app, exiting it, and again do end tasking all and starting link app for a secound time. 

Next, start the hedseat, connect link cable, activate link. 

And in 50% cases i need to do a even third end tasking-restarting process because link exits on it's own after a few secounds.

Turn off headset, diconnect cable, do end tasking, start app, start headset, connect cable, activate link from headset

Then it runs normally for hours. 

Thats not a solution for me. i am not willing to do that everytime I want to start DCS. No way. 

Edited by RoboHackfeld

MSI Gaming Plus Max X470, Ryzen 7 5800x3d, 5080, 4*16GB DDR4 3200, Samsung 1TB M2 SSD. 

Quest 2

Posted
46 minutes ago, RoboHackfeld said:

Performance is poorer than with link but it works.

I am getting very good performance with VD now. Actually it's a bit better than meta link since once the last update. Plus it is more stable. 

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 - F4 - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.

_A644840 (2).jpg

 

Posted
vor 2 Stunden schrieb Qcumber:

I am getting very good performance with VD now. Actually it's a bit better than meta link since once the last update. Plus it is more stable. 

I havent played with VD for a while now but yes indeed I also noticed some perfomance improvements due to the FOV Settings. I will make some more tests when back from vacation.

  • Like 1

MSI Gaming Plus Max X470, Ryzen 7 5800x3d, 5080, 4*16GB DDR4 3200, Samsung 1TB M2 SSD. 

Quest 2

Posted

At this point I'm fairly happy with VD (I just need to create a small passthrough window to see my keyboard) and probably will just keep Meta Link as a backup option, once it is fixed.

Alienware Aurora R16,  i9-14900KF, Crucial Pro RAM 64GB Kit (2x32GB) DDR5 5600MHz, NVidia 4080 Super with 16GB, 2TB SSD (Windows 11) and 2TB SSD (DCS)
Alienware 34" Curved QD OLED Gaming Monitor AW3423DW

Meta Quest 3 for VR with Virtual Desktop via AXE5400 router
VKB Gladiator NXT EVO SCE right hand, VKB Gladiator NXT EVO Omni Throttle left hand, VKB pedals
HF8 Gaming Pad with SimShaker for Aviators

Posted (edited)

Am i gonna loose cpu resources if i buy quest pro with dfr. Now i have 72fps on quest 2 with ffr and asw only low over large cityes. 

How much cost to cpu make that dfr? 

Sorry for off topic🫠

Edited by Zligor

AMD 5800X3D, RTX 4070ti super, 32Gb DDR4, 2Tb nvme m2, Win10, Quest2 on link cable with max resolution (slider all right) , OTT profile with 0,8 h&v fov reduction, QVFR (h&v focus size 42%, foviate res. 145%, periph.res. 18%), DCS settings all ultra and high, PD 1.0, DLAA, No hangar mod, and usually maintaining 72Hz.

Posted
28 minutes ago, Zligor said:

Am i gonna loose cpu resources if i buy quest pro with dfr. Now i have 72fps on quest 2 with ffr and asw only low over large cityes. 

How much cost to cpu make that dfr? 

Sorry for off topic🫠

With a 5800x3d and a 4070ti you should have plenty of CPU headroom. Prior to my current build I had a 5800x3d and a 4070. The QP will be a good upgrade over the Q2. With DFR you can get away with a smaller foveated region. I have mine set to 0.25x0.25. 

  • Like 1

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 - F4 - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.

_A644840 (2).jpg

 

Posted

I switch to VD due to continuos crash of link in the last weeks... but I ask some tips for a good experience: with Q3/7800x3D/4080 I set Av1 as codec and 150 bitrate/godlike res. I tried higher bitarate but I struggle a bit with latency. Do you suggest different res/codec/bitrate combinations? Thanks

Posted
24 minutes ago, Sparviero1978 said:

I switch to VD due to continuos crash of link in the last weeks... but I ask some tips for a good experience: with Q3/7800x3D/4080 I set Av1 as codec and 150 bitrate/godlike res. I tried higher bitarate but I struggle a bit with latency. Do you suggest different res/codec/bitrate combinations? Thanks

The VD Discord has some info re: Quest 3 and AV1 can have latency issues at higher bitrates. Try h264+ (I do) as can have higher bitrates and better at fast paced things. 

AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2

Posted
2 ore fa, sleighzy ha scritto:

The VD Discord has some info re: Quest 3 and AV1 can have latency issues at higher bitrates. Try h264+ (I do) as can have higher bitrates and better at fast paced things. 

What about your bitrate setting with h264+? I manage a good latency at 200 for h264, but with h264+ @500 I got an higher latency/some stuttering. Thanks

Posted
3 hours ago, Sparviero1978 said:

What about your bitrate setting with h264+? I manage a good latency at 200 for h264, but with h264+ @500 I got an higher latency/some stuttering. Thanks

Would need to double check (away for a few days) but it’s definitely a lot higher than 200. I have a good dedicated router beside my head so no network issues  

AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2

Posted

I'm also getting disconnects lately. Link stops working (cable) and I go back to Oculus Home. Usually right after starting link, or starting DCS, sometimes when loading a mission. Meta has got to have the worst customer service in history.

I tried VD but it's not an option for me due to poor connection.

Posted
6 hours ago, Reflected said:

I tried VD but it's not an option for me due to poor connection.

Have you tried VD using an ethernet-usb cable connected to the headset? This is for the quest pro but I think the Q2 and Q3 can use this by default without needing the android tweak. 

 

 

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 - F4 - F5 - F14 - F16 - F86 - I16 - Mig 15 - Mig 21 - Mosquito - P47 - P51 - Spitfire.

_A644840 (2).jpg

 

  • Recently Browsing   0 members

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