Svsmokey

Looks like you have done a great job spec'ing a well-balanced high-performance system .

I'm reluctant to trash other people's choices , but since you asked... In my opinion (and experience) the X-52/Pro is garbage . The original Saitek-manufactured units were good and provided good service for years , but since then the brand has changed hands at least twice and quality has gone massively downhill . Those lovely rotaries , mouse stick and slider are all pretty much useless , as potentiometer jitter makes them impossible to use as axes . Likewise the buttons/hat switches are of very poor quality , with no "clicky" action , and a high failure rate . The CH Hotas is a much better option for long-term reliability in the same price range , and the Thrustmaster T-1600 , with which i personally have little experience ( I did purchase a version for the grand-boys playstation ) is highly regarded , and priced far less , albeit with the caveat of having fewer hats/buttons . Doubtless , someone will be along who disagrees with all of this , but the post is based on my personal experience , and written solely for the purpose of forestalling your disappointment .

Sounds like wrong button . You should bind and use tdc designate to lock . Also be sure to sensor-select the radar ddi . (Diamond at top right)

Welcome to the forum ! In order of tracking accuracy/smoothness from worst to best : WMR headsets (Reverb , Odyssey and others) use two-camera inside-out tracking Quest , Rift S use multiple inside-out cameras for tracking . Vive Pro , Index , Pimax use base station tracking .

1: I would try deleting the scripts folder in saved games . If that doesn't do it , i would rename the entire saved games/dcs folder . 2: It looks like you have far too many programs open and running . Try to pare those down substantially . DCS is (necessarily) resource-intensive , and the more programs you can remove from the startup , the better .

Try un-checking "game mode" in settings . Also wanna be sure to do your bindings for each aircraft in "sim" vs "game" .

Building a pc is easy . It is speccing a high-performance pc that can be difficult . When you are comfortable doing so , be sure to post your parts list in the pc hardware section for input .

Within gbu range ?

Point taken :) But i don't see a new guy asking "anyone know of a tv series depicting real-life Hornet training" .

No , the post is valuable to new guys . Leave it up .

:megalol:

Yep . I will be aiming for 4x msaa with my next gpu .

It is a great headset , particularly for those who play games in addition to seated sims . The extra FOV prolly increases the sense of speed as well .

Hornet pilots launch from a carrier with hands on the glareshield , not on the stick , so it is all automatic .

https://andres.shop/jetseat/24-76-vibrating-pad-simshaker-jetpad-fse.html#/11-color-black/30-additional_software_included-none

1: Vulkan will unload the cpu a little by preloading shaders/textures in the gpu vram prior to draw calls . This will improve cpu frametimes , but not necessarily fps . This at the expense of using more gpu vram . 3: it will certainly offer a smoother experience , but may or may not provde better fps . 4: not really . Too many variables and individual preferences to make a blanket recommendation . Do your research bearing in mind your ipd , whether you will use the headset for other than seated simming , price point , comfort etc . 5: who knows? 6: SLI is dead ., and if it weren't , DCS VR cannot make use of it anyway .

I was running the CV1 and cameras on the recommended Innatek card , and all 4 usb's were the same if i remember correctly . I think they were all usb 3.0 . Maybe the camera recommendation was either/or rather than 1 of each . Oculus kept telling me to update the Fresco drivers for the Innatek , but they always showed up to date .

Just ignore . I had spurious warnings on mine (updating Fresco drivers) before getting the S . Even now i get bs warnings that my headset audio is off (I want it off) or that it can't find the controllers (don't use them) I do find it a little strange that your cameras are connected to 2 .0 and 3.0 usb ports though .

To say nothing of two more engines than ED is interested in modeling .

Weird . I'm hands free on the initial climb arming , a/g buttoning , cooling ir maves & flir-ing while turning to course and climbing to cruise altitude (usually 4k or so) . It may be time to do some snakeye practice & stay very low after takeoff to see if what you describe is problematic for me .

Dunno , i don't leave the flaps down . I clean up the aircraft a second or so after t/o , primarily to prevent overspeeding with the gear down .

Check windows audio settings and verify the devices (in and out) you wish to use ? Another possibility is that "unable to perform command" means the command IS recognised , but VoiceAttack can't find the relevant files . Have you updated or reverted DCS ? There is a change in file structure between 2.55 and 2.56 . Finally , Oculus and VA running in admin ?

Stay away from MadCatz-era Saitek though . Utter garbage .

Try this ? https://forums.eagle.ru/showpost.php?p=4305052&postcount=27

Spudknocker on YT has a good vid on the mav-ir and Litening pod use . He is running 2.56 , and uses the soi left only to uncage each mav after designating with pod . All slewing and designating is done with the Litening pod . This is slightly different than what i experience in 2.55 , as i only soi left once . Maybe Ed fixed a bug . The chuck's guide reference is for mav-f's without the pod .