kris018 Posted June 3 Posted June 3 Picked up a Crystal light today as i spotted it on sale and...well why not right ? Challenge 1 : Im old, never set anything like this up before. Challenge 2: I am what you can call "it should work out of the box" kinda guy. Found these 2 links today : and The settings/installation advices still ok to follow? (I by no mean need 120fps, locked on 90 in 2d so....) My specs are : i9-13900 64bg ram 4090. Any tips/links would be deeply appreciated
Lange_666 Posted June 3 Posted June 3 3 hours ago, kris018 said: Picked up a Crystal light today as i spotted it on sale and...well why not right ? Challenge 1 : Im old, never set anything like this up before. Challenge 2: I am what you can call "it should work out of the box" kinda guy. Challenge 1: There's a first time for everything Challenge 2: Take your time, you'll get there. Don't rush things, take it step by step. Just go into VR without going into DCS and get used to the feeling of the VR environment. 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!
Moxica Posted June 3 Posted June 3 "it should work out of the box" ..It doesn't Put your PC specs in signature or smth.. Answer is namely "it depends" ASUS ROG Strix B550-E GAMING - PNY GeForce RTX 4090 Gaming VERTO EPIC-X - AMD Ryzen 9 5900X - 64Gb RAM - 2x2Tb M2 - Win11 - Pimax crystal light - HP Reverb g2 - Oculus Quest 2 - Thrustmaster Warthog HOTAS - Thrustmaster Pendular Rudder - 2X Thrustmaster MFD Cougar - Audient EVO8
Qcumber Posted June 3 Posted June 3 3 hours ago, kris018 said: Picked up a Crystal light today as i spotted it on sale and...well why not right ? Challenge 1 : Im old, never set anything like this up before. Challenge 2: I am what you can call "it should work out of the box" kinda guy. Found these 2 links today : and The settings/installation advices still ok to follow? (I by no mean need 120fps, locked on 90 in 2d so....) My specs are : i9-13900 64bg ram 4090. Any tips/links would be deeply appreciated Every VR set works out of the box but not necessarily as you expect. VR is still a bit of a challenge but there are plenty of people here ready to help. My first bit of advice is don't panic. Take your time and you will get there. My second bit of advice is that age gives experience. If you don't have the knowledge exploit the ability of others! 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.
Dangerzone Posted June 3 Posted June 3 (edited) 6 hours ago, kris018 said: I am what you can call "it should work out of the box" kinda guy. I hate to tell you, but expect to spend as much time (if not more) tinkering with your VR settings as you do flying in DCS. Not only can VR be time consuming to setup, but it can also eat up a lot of time with diagnosing/trying to fix settings. Just something as simple as a DCS update can ruin previous smooth experiences. (The latest DCS version has created micro stutters for me that weren't there before that I had to go finding and tweaking again to try and get a better experience). Windows updates can automatically revert settings that you've set (such as re-enabling core parking, windows game mode, etc), so it's worth having a 'check list' of the things that you've changed that you know work to go over if you start experiencing problems again in the future. I would put VR under the 'experimental' category with DCS. Both Pimax software, and DCS seem to be released in perpetual "BETA" states now - and I'm not a fan of how windows takes full control over it's updates either. That's not to say that it can't ben an enjoyable experience, but the first thing I highly recommend is lowering your expectations to ones that are realistic. That way you won't be as disappointed, and can start enjoying the positives. I didn't watch the video - but a few things that's definitely worth checking: Disable HAGS in Windows Disable Windows Game Mode Make sure your NVIDIA CPanel is set to 'Prefer Max Performance" Windows Power setting to Ultra Try Rivatuner and lock the FPS to the same as your headset. (ie, if running 72hz, then lock to 72fps to see if this helps). Be prepared to experiment with this. You may find a better experience going to 120fps in your HMD even if you don't hit 120fps). YMMV - Everyone seems to have different experiences with DCS as to what is better for them. Disable windows core parking. (This is a big one - park control is good software for helping with this). Consider restricting DCS to P-cores only (using process lasso). YMMV - some say to do this, others say not to - so you need to try and see what works for you. Turn down mouse (and keyboard if you have a gaming one) polling rate to something lower than 1000. Start with extremely low/conservative Graphic settings, and get it smooth / working OK for you first. Then you can increase the settings to what you like. This helps eliminate whether it's DCS settings itself that's the issue, or something external. Disable TACView if you have it installed (at least until you have things working smoothly). Don't be afraid to rename your saved games\DCS folder to DCS.OLD, and let DCS create a new 'fresh' configuration for you that you can play with. This helps eliminate any previous settings/mods/etc from the equasion until you have something running smooth. You can always copy DCS.OLD back to DCS to revert (or copy just things like the config\input directory) if you get a better experience with a fresh config without having to rebind your whole setup again. Test on a resource-friendly map first. (ie: Caucasus), and not in the Apache, Chinook, or other aircraft that are demanding with textures, but something easier if you have a module that's more simple first. Consider dropping Pimax back to version 1.29 if nothing else works (Again YMMV - but I've heard of some users that are staying on that version for the time being until there's a solid release/update). In addition to this, I would also consider dropping back to 2.9.14 in DCS if you're still experiencing issues and see if this helps. As mentioned, numerous users are having problems with DCS 2.9.16 (and .15 might be OK - but IIRC some are dropping back to .14) and stuttering/FPS issues - so if you seem to be having no luck after trying all the main things you can find on the internet - it may be worth rolling back to see if the current version might be a contributing factor to your experience. In a strange twist of fate, I've found that DCS can't hold 72FPS with the latest update in Germany CW. It stays at 72FPS mostly, but drops with stutters to 60 however if I change my HMD to 120fps - it can maintain 120FPS and drop to 110 around the same interval. Why it can't maintain 72FPS at 72HZ but can stay above 100FPS if I switch to 120HZ is a mystery. I can lock onto 60fps no problems without the stutters though, but of course Pimax doesn't have a 60hz refresh rate. This was the biggest problem coming across from HP which I had a smooth experience, to Pimax -as for whatever reason, these stutters are caused by momentary 'cpu bound' messages in DCS. I think it may have something to do with polling/interrupts and DCS not handling these efficiently with it's multi-thread implementations but that's a total guess. I'm no hardware/IRQ/interrupt expert (even if I do recall having to learn how to set the IRQ manually back in the DOS era with soundcards ) Good luck - I hope this is of some help. Edited June 3 by Dangerzone 3 1
jaydee Posted June 5 Posted June 5 Kris018, you will be fine . I am old too and I still ride A Motorbike every day !..Dangerzone has given some great Tips above . I have the Crystal . It took me a long while to get it tuned for my liking !...Now I can fly in online servers in VR !..And Loving it ! Kris, start with the basics with your headset . Comfort,, Learn the Settings in Pimax Play. Experiment with your Device Settings !.. There are some Great people here that are willing to Help with you with your new VR journey into DCS ! 2 R7 7800X3d,64g 6000 Ram,4090, Pimax Crystal.
kris018 Posted June 8 Author Posted June 8 (edited) Thank you for reply everyone. Actually having a blast just flying helicopters around, seems to run ok, some miner stutter if i look to the sides but i can live with that. Spotting is kind of a pain but just need to get used to this i guess. Still playing around with settings as it seems no matter what i change/add is running around 65-70 fps. My biggest issue atm is getting my IPD correct, i know is set it correctly in play but it just feels off (hard to explain) Also need to get some padding as the headset itself don't really fit my head, this is a good place for that? https://www.studioformcreative.com/ @jaydee Just sold my Mv Agusta F3 800 RC and im crying myself to sleep every night Need to get a new one asap No regrets yet and its a blast in iRacing Edited June 8 by kris018
Steel Jaw Posted June 8 Posted June 8 What advantage is there to disabling tacview? "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.
Gun Jam Posted June 8 Posted June 8 2 hours ago, Steel Jaw said: What advantage is there to disabling tacview? Tacview can add extra load to the cpu and cause inconsistent FPS or an overall reduction in FPS. It has been my personal observation that after DCS went to multicore this is now a non factor and there is no advantage to disabling tacview. But doing so Its not a bad suggestion for a first time startup with Vr, having as few of variables as possible can make any troubleshooting much easier. 1
Recommended Posts