draconus Posted February 19, 2024 Posted February 19, 2024 2 minutes ago, freehand said: Sure I want your opinion I have owned many headsets in the past but have the chance to buy a rift s very cheap and would like to give it another go I run a 3080. For sure you can get it cheap, it's old tech. With that card you could run it with high fps (if not CPU bound), no shimmering and pretty high PD, tracking is great, but it's low resolution these days - you have to take it into consideration. I never had any comparison though. 1 Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
freehand Posted February 19, 2024 Posted February 19, 2024 5 minutes ago, draconus said: For sure you can get it cheap, it's old tech. With that card you could run it with high fps (if not CPU bound), no shimmering and pretty high PD, tracking is great, but it's low resolution these days - you have to take it into consideration. I never had any comparison though. Thank you.
Lange_666 Posted February 19, 2024 Posted February 19, 2024 (edited) Rift-S (since that was what the topic was created for): I still use it (although on half the refresh rate through ASW). Think it's a good headset but i only have (had) a Pico 4 to compare it to and i prefer the Rift-S over the Pico simply because it has a display port. The Pico has too many artifacts when using ASW (or it's implementation of it) compared to the Rift-S. Biggest drawback for me of the Rift-S is the disconnection (not being recognized) each time the PC has been shutdown. So i need to un-plug / re-plug the USB each time after a PC restart. I had that also with my previous headset on my previous PC but there it would only disconnect 20% of the reboots and even then simply stopping and starting the Oculus service would make it re-connect. On this PC my first Rift-S never disconnected but my second one does disconnect each time and cycling the Oculus service doesn't do the trick with this one. So it's a bit headset depended. Edited February 19, 2024 by Lange_666 Win11 Pro 64-bit, Ryzen 5800X3D, Corsair H115i, Gigabyte X570S UD, EVGA 3080Ti XC3 Ultra 12GB, 64 GB DDR4 G.Skill 3600. Monitors: LG 27GL850-B27 2560x1440 + Samsung SyncMaster 2443 1920x1200, HOTAS: Warthog with Virpil WarBRD base, MFG Crosswind pedals, TrackIR4, Rift-S, Elgato Streamdeck XL. Personal Wish List: A6 Intruder, Vietnam theater, decent ATC module, better VR performance!
draconus Posted February 19, 2024 Posted February 19, 2024 (edited) 25 minutes ago, Lange_666 said: Biggest drawback for me of the Rift-S is the disconnection (not being recognized) each time the PC has been shutdown. During 3 years I've seen it only a few times, I even changed the CPU, GPU and RAM in the meantime. My current problem is huge RGB noise (since a few months) and I have no idea what's the cause. Sometimes it's clear image but most of the time now it's more or less noised and sometimes it's huge noise up to flickering and black screens. I'm quite shocked that you quit on the Pico 4 with such big resolution and still prefer Rift S. Edited February 19, 2024 by draconus Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
Qcumber Posted February 19, 2024 Posted February 19, 2024 1 hour ago, freehand said: I used to have a rift s interested in people opinions in 2024 ? It's still a viable headset. The main issues are FOV and visible screen door. Push the resolution up and the image is pretty good. I use a QP now so find it difficult to go back to. 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.
freehand Posted February 19, 2024 Posted February 19, 2024 I have owned a questpro pico4 , g2 and other older headsets my all time favourite is the G1 very light comfy easy to drive but we all know how wmr is going to pan out so thought I would give the rift s another go the VR snobbery is all washed out of me now I just want something useable, I give up trying to find a unicorn many moons ago lol.
Lange_666 Posted February 19, 2024 Posted February 19, 2024 1 hour ago, draconus said: My current problem is huge RGB noise (since a few months) and I have no idea what's the cause. Sometimes it's clear image but most of the time now it's more or less noised and sometimes it's huge noise up to flickering and black screens. I'm quite shocked that you quit on the Pico 4 with such big resolution and still prefer Rift S. RGB noise: Could be the cable Pico: Overall clarity is better but there are so many ghosting artifacts when the image moves quickly while using ASW. Without ASW at native refresh freq it was very good but it was difficult to keep the FPS above the native refresh freq on my setup (5800x3d+3080Ti). Once it dropped below that it started to stutter. And since ASW was so bad i did send it back. ASW also only worked with Virtual Desktop, with their own Streaming Assistant it even didn't. So i preferred a headset with less resolution but with a lot better overall performance. Win11 Pro 64-bit, Ryzen 5800X3D, Corsair H115i, Gigabyte X570S UD, EVGA 3080Ti XC3 Ultra 12GB, 64 GB DDR4 G.Skill 3600. Monitors: LG 27GL850-B27 2560x1440 + Samsung SyncMaster 2443 1920x1200, HOTAS: Warthog with Virpil WarBRD base, MFG Crosswind pedals, TrackIR4, Rift-S, Elgato Streamdeck XL. Personal Wish List: A6 Intruder, Vietnam theater, decent ATC module, better VR performance!
Qcumber Posted February 19, 2024 Posted February 19, 2024 12 minutes ago, Lange_666 said: RGB noise: Could be the cable Pico: Overall clarity is better but there are so many ghosting artifacts when the image moves quickly while using ASW. Without ASW at native refresh freq it was very good but it was difficult to keep the FPS above the native refresh freq on my setup (5800x3d+3080Ti). Once it dropped below that it started to stutter. And since ASW was so bad i did send it back. ASW also only worked with Virtual Desktop, with their own Streaming Assistant it even didn't. So i preferred a headset with less resolution but with a lot better overall performance. If you are looking for a good upgrade to the rift s I can recommend the QP. I got one used, immaculate condition as I think a lot of people bought them for the "pro" standalone experience. Where it shines for me is relatively low pixel count, eye tracking and DFR, and wide horizontal FOV. Link Cable gives 960 Mbps. I can run DCS on high/ultra with an fps of 40-80 and ASW is a lot better than VD SSW. Overall a better experience than the P4. 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.
Lange_666 Posted February 19, 2024 Posted February 19, 2024 Might be an option if my current Rift-S dies but I'm preferring one with a DP connection instead of wifi/USB-link. 2 Win11 Pro 64-bit, Ryzen 5800X3D, Corsair H115i, Gigabyte X570S UD, EVGA 3080Ti XC3 Ultra 12GB, 64 GB DDR4 G.Skill 3600. Monitors: LG 27GL850-B27 2560x1440 + Samsung SyncMaster 2443 1920x1200, HOTAS: Warthog with Virpil WarBRD base, MFG Crosswind pedals, TrackIR4, Rift-S, Elgato Streamdeck XL. Personal Wish List: A6 Intruder, Vietnam theater, decent ATC module, better VR performance!
Phantom711 Posted August 3, 2024 Posted August 3, 2024 (edited) Am 19.2.2024 um 13:08 schrieb Lange_666: i prefer the Rift-S over the Pico simply because it has a display port. The Pico has too many artifacts when using ASW (or it's implementation of it) compared to the Rift-S. Even though that‘s two sentences, it sounds to me, as if you conclude, that the motion reprojection of the Pico4 is bad because of the USB connection as opposed to the Rift‘s DP. Let me state first, that you are also using the term „ASW“ way to indifferently. „Motion reprojection“ is the more general term and the different companies have their own particular versions of it. ASW is Metas version. SSW is the one from VD and I don‘t know what Pico has really. Now several people agree with me, that ASW (Meta) is a very good implementation of motion reprojection and noticably better than SSW. So I would argue, that the artefacts that you observed are rather a matter of SSW vs. ASW and not so much (or at all) due to DP vs. USB/WiFi. You might simply have drawn the wrong conclusion there. Edited August 3, 2024 by Phantom711 1 vCVW-17 is looking for Hornet and Tomcat pilots and RIOs. Join the vCVW-17 Discord.
unlikely_spider Posted December 20, 2024 Posted December 20, 2024 Haven't launched DCS in a while, and now there's a new launcher and DCS will not open in VR. I hit "Launch DCS" in the launcher, the launcher goes away for a few seconds, then comes back again with the "Launch DCS" button available again. Anyone else experience the same? Modules: Wright Flyer, Spruce Goose, Voyager 1
spikenet Posted December 20, 2024 Posted December 20, 2024 Have you gone into settings and made sure the VR is enabled. Not sure if it is the right way, but I have found you have to load a graphic setting before using the launch for 2d or VR. I had opposite problem, would only launch in VR not 2d. Did a reinstall and it fixed it.. 1
sleighzy Posted December 21, 2024 Posted December 21, 2024 (edited) 1 hour ago, unlikely_spider said: Haven't launched DCS in a while, and now there's a new launcher and DCS will not open in VR. I hit "Launch DCS" in the launcher, the launcher goes away for a few seconds, then comes back again with the "Launch DCS" button available again. Anyone else experience the same? You should probably be raising this as a new post. vs. adding to this one. However, try installing the latest version of the Microsoft C++ distributables, https://aka.ms/vs/17/release/vc_redist.x64.exe (which come from here https://learn.microsoft.com/en-us/cpp/windows/latest-supported-vc-redist?view=msvc-170). Failing that remove all custom mods and run a slow repair of the game, or verify files if on Steam. A number of mods are now broken with later releases of DCS. If it still doesn't launch then upload your "C:\Users\username\Saved Games\DCS\Logs\dcs.log" file (may just be a text document named "dcs" if your Windows is hiding file extensions) here for review. This should probably be done as a new post. Edited December 21, 2024 by sleighzy 1 AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2
unlikely_spider Posted December 21, 2024 Posted December 21, 2024 Ok, thanks both of you. I ended up telling the launcher not to launch by default and just going back to the old start menu to launch DCS. After disabling VR in the DCS options then re-enabling it DCS launched in the Quest once again. Modules: Wright Flyer, Spruce Goose, Voyager 1
Lace Posted April 14 Posted April 14 Does anyone know how to get rid of the blue circle when using the Quest 3? It never appeared with my old Rift S, but since upgrading I can't seem to switch it off anywhere. It is quite distracting when looking down into the cockpit and completely unnecessary when using a sitting (stationary) boundary. 1 Laptop Pilot. Alienware X17, i9 11980HK 5.0GHz, 16GB RTX 3080, 64GB DDR4 3200MHz, 2x2TB NVMe SSD. 2x TM Warthog, Hornet grip, Virpil CM2 & TPR pedals, Virpil collective, Cougar throttle, Viper ICP & MFDs, pit WIP (XBox360 when traveling). Quest 3S. Wishlist: Tornado, Jaguar, Buccaneer, F-117 and F-111.
sleighzy Posted April 14 Posted April 14 27 minutes ago, Lace said: Does anyone know how to get rid of the blue circle when using the Quest 3? It never appeared with my old Rift S, but since upgrading I can't seem to switch it off anywhere. It is quite distracting when looking down into the cockpit and completely unnecessary when using a sitting (stationary) boundary. Turn off the guardian, or reset it in a position so that when learning forward you aren't getting close to it. AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2
Lace Posted April 14 Posted April 14 2 hours ago, sleighzy said: Turn off the guardian, or reset it in a position so that when learning forward you aren't getting close to it. How do you actually turn it off? I can't find it anywhere in settings. It's also the floor which is causing the issue, I can make the horizontal distance big enough, but looking down shows the circle. Maybe I need a bar stool Laptop Pilot. Alienware X17, i9 11980HK 5.0GHz, 16GB RTX 3080, 64GB DDR4 3200MHz, 2x2TB NVMe SSD. 2x TM Warthog, Hornet grip, Virpil CM2 & TPR pedals, Virpil collective, Cougar throttle, Viper ICP & MFDs, pit WIP (XBox360 when traveling). Quest 3S. Wishlist: Tornado, Jaguar, Buccaneer, F-117 and F-111.
erniedaoage Posted April 14 Posted April 14 I believe it's somewheree at the device list in the meta quest software. I am not at home right now, but i believe it's there when you setup everything, you can also setup your playspace. Specs:WIN10, I7-4790K, ASUS RANGER VII, 16GB G.Skill DDR3, GEFORCE 1080, NVME SSD, SSD, VIRPIL T-50 THROTTLE, K-51 COLLECTIVE, FFBBeast Virpil Alpha+VFX Grip, MFG CROSSWINDS, JETPAD, RIFT S Modules:A10C, AH-64D, AJS-37, AV8B, BF109K4, CA, F/A18C, F14, F5EII, F86F, FC3, FW190A8, FW190D9, KA50, L39, M2000C, MI8TV2, MI24P, MIG15BIS, MIG19P, MIG21BIS, MIRAGE F1, P51D, SA342, SPITFIRE, UH1H, NORMANDY, PERSIAN GULF, CHANNEL, SYRIA Thrustmaster TWCS Afterburner Detent https://forums.eagle.ru/showthread.php?t=223776 My Frankenwinder ffb2 stick https://forums.eagle.ru/topic/254426-finally-my-frankenwinder-comes-alive/
Aapje Posted April 14 Posted April 14 1 hour ago, Lace said: How do you actually turn it off? I can't find it anywhere in settings. Developer settings and then Physical space features: They logically don't want to show it as a normal setting, because then people will turn it off, jump through a glass window, and then sue Meta for having died. --- Note that you can also reduce the sensitivity of the boundary. That is in the regular boundary settings, though. I personally set mine to the lowest sensitivity, but it will then only warn you if you get very close to the border of your boundary. 1
Lace Posted April 14 Posted April 14 Thanks. I don't remember seeing the 'Developer' tab last time I looked - does that need to be enabled first somewhere? I'll look again later today. Laptop Pilot. Alienware X17, i9 11980HK 5.0GHz, 16GB RTX 3080, 64GB DDR4 3200MHz, 2x2TB NVMe SSD. 2x TM Warthog, Hornet grip, Virpil CM2 & TPR pedals, Virpil collective, Cougar throttle, Viper ICP & MFDs, pit WIP (XBox360 when traveling). Quest 3S. Wishlist: Tornado, Jaguar, Buccaneer, F-117 and F-111.
Aapje Posted April 14 Posted April 14 (edited) It is hidden a bit under the System settings. Did you check there? If it is missing, you might have to enable developer mode in your account. I did that a long time ago, because it is needed for side loading. Back then it was a bit of a hassle, but apparently it is fairly easy now. It should work thusly: Open the Meta Horizon app on your phone with the Quest on and near you Click on the headset icon on the top left Scroll down a bit and click headset settings There you should find the setting somewhere Then restart the headset Edited April 14 by Aapje
DrSnooker Posted June 25 Posted June 25 I have an Oculus Rift S that I would use with DCS. As far as I understand, I can use it in a way that I can see my hands and my HOTAS through the VR headset. Is there a guide that I can use to set this up?
draconus Posted June 25 Posted June 25 25 minutes ago, DrSnooker said: I have an Oculus Rift S that I would use with DCS. As far as I understand, I can use it in a way that I can see my hands and my HOTAS through the VR headset. Is there a guide that I can use to set this up? It's not an AR headset. You can only see in-game cockpit including the HOTAS as is in the modeled aircraft, not your own. Additionally you can turn on simulated hands which you can control with Oculus touch controls and also control the in-game HOTAS instead of your own. Win10 i7-10700KF 32GB RTX4070S Quest 3 T16000M VPC CDT-VMAX TFRP FC3 F-14A/B F-15E CA SC NTTR PG Syria
sleighzy Posted 22 hours ago Posted 22 hours ago (edited) On 6/25/2025 at 11:04 PM, DrSnooker said: I have an Oculus Rift S that I would use with DCS. As far as I understand, I can use it in a way that I can see my hands and my HOTAS through the VR headset. Is there a guide that I can use to set this up? You can do this if you're using Virtual Desktop to connect to your PC. It has native support to show a passthrough for your hands. I'm not familiar with the Rift S however as to it's camera support for passthrough for this, you may need to inquire on the Virtual Desktop Discord server. EDIT: I just enquired, no Rift S isn't supported by Virtual Desktop for hands passthrough. VD only supports standalone headsets. Edited 22 hours ago by sleighzy AMD 7800x3D, 4080Super, 64Gb DDR5 RAM, 4Tb NVMe M.2, Quest 2
Recommended Posts