Twwhitey

Roger that thanks dburne. They are my current settings as well. Whats weird is that a complete, fresh re-install of Win10 Pro coupled with a focused effort at “optimizing” (based on some lengthy YouTube videos) has netted out slightly better Cinebench and Unigen benchmark scores vs. my pre-built Win10 Home install BUT oddly some weird perf issues/hiccups in DCS. Just trying to nail down what might be different or a missed configuration setting...

I recently did a complete OS re-install trying to clean up pre-installed bloatware and optimize somethings I was having issues with... Can someone remind what the preferred setting is (with DCS in mind) regarding the Oculus Home "Graphics Preference" setting? "Prioritize Quality"? or "Prioritize Performance"? My system prior to the re-install was running great from a DCS perspective but I was having weird issues that led to some system instability and I can't recall which setting I used in the past. Anyone out there with a similar system who can check their system and let me know what's the optimal setting?

I personally don’t think I’d use the in-flight toggle you are speaking of but the 2nd fix you mention above would be greatly appreciated. I played with mouse on for months thinking that I couldn’t use the mouse to access the comms menu (because the blue cross doesn’t trigger selections) only to realize later that the mouse dot was just offset but was there the whole time... :doh: that would be an appreciated fix indeed.

Funny you mention that as I recently found it as well. Ive been SLOWLY whittling away watching his 4hr(!) Windows 10 1903 tweaking video. He’s at a whole ‘nother level of tweaking with his recommendations. He’s got a guide linked in that video that’s huge. I’ve got a fresh install of Win10Pro that I’m slowly applying his tweaks to (and backing up regularly)... learning a lot about Windows 10 architecture for sure...

Right on makes sense. I’ve used both and find the clarity better on the Index - especially in my case because I definitely need the IPD adjustment. you’re right though it seems the Index requires more horsepower/tweaking to get acceptable perf. Not bashing the Rift S at all... it works and works well, I’m just on the outside of the recommended IPD range so I need something that allows adjustment...

Wait doesn’t the Valve Index have a larger native per eye (thus more total) pixel/resolution than the Rift S? 1440 x 1600 per eye (Index) vs 1280 x 1440 (Rift S)? Reverb, based on my understanding is indeed larger than both though at 2160 x 2160 That was my understanding at least - or are the some technical details that make it a bit more confusing that? (Serious question I very well could be confused)

Completely agree.. I’ve been playing this mission non-stop every day off-and-on for several weeks now... it’s awesome... Im slowly grinding away at the enemy thanks to the addition of persistence. I’ve made a few tweaks myself (added some user flags to allow adjustment to the number of active enemy caps, tweaked the default load outs & added a few A-10s and F-16s to the Khasab airbase). One thing I’ve been looking into is augmenting the “Other” menu to add the ability to select a specific mission but I’ve had a thought... Surrexen do you think it’s technically possible to add the current active mission number as a variable exported to a persistent file? As a single player I find myself getting assigned a mission, spend a decent amount of time whittling away at the defenses (sometimes multiple sorties) then essentially run out of playtime to actually finish that mission.. I’d love have that mission number saved so when I load up again later I’m assigned that last mission so I can sort of pick up where I left off... based on what you know is that even possible?

Interesting.. good to note, I’ll keep that in mind, for $7 I’d pick one of those up just in case... thanks for the heads up!

Ahhhhhh got it - that makes perfect sense now... thank you for the clear explanation. sounds like I need to look into BT modules as I don’t *think* my Asus MB has a BT receiver. Have to check that... Interesting stuff I think I’m closer to pulling the trigger...thanks again... Edit: sweet! Asus Maximus XI Hero does indeed support BT 5.0...

Nice - that’s a great update. I recently started using JDAMs (targeting via the TGP) and was like why haven’t I been using these before! Unrelated question for you Surrexen. Are enemy airfields destroyable (or damagable) the way this mission is constructed? Say I take on a rogue mission to bomb one of the enemy CAP airfields and succeed in bombing the runway would that suppress future CAPs spawning at that airfield? Those pesky enemy CAPs do make it quite a challenge to break out the A-10C for some dedicated ground pounding. Loving this mission, with persistence turned on it’s great to slowly make progress clearing out threats so I can focus on the real strike missions.. excellent stuff

Huh... so is Bluetooth the ONLY option? (i.e. it REQUIRES a PC with a Bluetooth receiver?) OR is Bluetooth just a wireless option but can communicate via a USB connection? I’m very intrigued it’s just the information on the website isn’t super clear.

Totally agree - with unit persistence turned on I’ve been having a blast slowly whittling away the enemy air defenses and I’m spending hours making multiple sorties a night - RTBing, reloading, taking care of scrambled CAPs and eventually taking care of some of the assigned missions. It’s great. As for the coordinates. I haven’t had any issues entering the 2nd (bottom) version of last/longs displayed in the Target Report Option that read like this DD.MM.SSS N DD.MM.SSS E (I think) Sounds like you have “Precise” selected (which is obviously critical) are you entering the N and E before typing in the numbers? Also there is an option (in the HSI data page) to toggle the format of the lat/longs the system uses (I’m not in front of my PC but it’s in the lower right hand side of one of the pages) that needs to be set to the lat/long decimal option (but I’ve not had to change this in the past) Assuming you have options set right and inserted a new waypoint into the waypoint sequence the entry steps should roughly be like this (from memory): Click UFC in the HSI data page Select POS in the UFC Enter “N” (i.e. the number 2) Enter first 4 digits DDMM <press ENT> <UFC will prompt to enter :TTO> Enter SSS <press ENT> Enter “E” (i.e. the number 4) Enter first 4 digits DDMM <press ENT> <UFC will prompt to enter :TTO> Enter SSS <press ENT> Select ELEV in the UFC Enter elevation in meters. <press ENT> I’ve had success with the above process - of course I’m doing this in VR without the ability write the coords down so I’m getting pretty good at furious typing these things into the UFC before the target report disappears! But like I said, this has been working for me and I can actually find the targets...

This is a great thread and post! I’m watching this thread intently and looking REALLY hard at buying one of these... 32 extra buttons good lord that’s awesome I think I could find very good uses for the DMS, DMS & CMS center clicks plus the upgrades to 5-way(?) pinkie & step button on the side. :thumbup: This thing is definitely supposed to plug & play with a standard Warthog base right?

Right on that’s been my experience as well... good stuff thanks for the sanity check..

dburne - and you are running with ASW enabled in OTT as well right? Your settings are very close to mine and I have ASW set to Auto... depending on the action going on in a particular mission I can get framerates toggling between 80 and 40 (when ASW kicks in...) Is that your experience as well?

Glad I’m not the only one... I do like the action but even calling in escort/MIGCAP (as suggested above) I still have a hard time carrying enough AA ordnance, dodging SAMs and ultimately expending the limited AG ordnance I’m carrying. :joystick: That being said. I found the post in the other (Caucasus mission thread) about adjusting the SetSquadronCapInterval min & max intervals (I’ve adjusted them to be hours instead of minutes) so we’ll give that a try...

Hey Surrexen - this mission is fantastic work.. with unit persistence in place you’ve actually created a user selectable 120+ mission campaign that can be fired up at any time. Absolutely awesome! Question for you - I end up playing totally single player (when I can find the time) and I like to focus on SEAD and A/G missions... with all of the air defenses and enemy air units I tend to get smoked more often than not even when calling in support packages. Would you have any recommendations on how to reduce the number of enemy air units that get spawned over the course of playing? Are there any easy to adjust settings within the mission editor I could tweak to tone down the A/A threat so I work in my AG techniques? (Either frequency of flights? or total number? Or both?) Kinda simulate having air superiority? Not a knock on your work at all it’s fantastic :thumbup: - I’m just wondering if there might be a way to dumb down the overall difficulty for missile bait like myself LOL

Edit: turns out it’s just a lame fabric cover not a replacement interface of any kind. Took 6 months for them to create that.... lame If you are like me and have a Rift S that has a foam interface that is falling off and disintegrating it appears that VR Cover FINALLY has an option for us. I have no experience with them nor their products but it has to be better than stock IMO... https://www.vrcover.com/product/rift-s-vr-cover/

In my experience Setting PD (or Oculus SS) to 2.5 is an enormous amount of pixels to push for that rig in VR. I have a similar setup (with the GPU and CPU OC’d) and run SS @ 1.4 with a mix of medium, low and high (water) textures, no shadows, no cockpit illumination, no traffic, no chimney smoke, trees 80%, 0 clutter, 8x AF, 2x MSAA. I have ASW set to auto and can run mostly at 80fps except over densely populated areas or areas where there’s a lot of action going on (especially MP) where ASW kicks in and locks frames to 40fps. With PD set to 2.5 you’ll guarantee ASW is on all the time (40fps max) and even then it’ll struggle to maintain that hence why you see sub 40fps numbers. I’d recommend lowering the PD to something between 1.0-1.5 for VR based on settings you prefer until some form of VR optimization is implemented

Installed them a few days ago...haven’t noticed any real change in performance either good or bad, at least on my system. I’ve even tried setting the new Low Latency Mode (to the “Ultra” setting) and leaving it at “Off” and noticed no real difference in perf in VR either way. As mentioned above the new Sharpening filter only applies to games on the nVidia Freestyle compatability list.... and DCS ain’t on that list... :/

#2164 was received last week and installed over the weekend. YOU WILL LOVE IT. I can’t overstate how much of an upgrade it really is... especially with the TGP in play for the Hornet now. You can quickly scroll the Hornet TGP position indicator completely across the SA screen in seconds (which was painfully slow with the Thrustmaster version) but you also have the fidelity for precise adjustments on the targets when need be. It’s worth every penny and time spent to install... For those on the fence do it.

Found it interesting that the current SteamVR Beta v1.7.10 change description explicitly mentions DCS World. Granted it seems to imply a fix to a previous fix (that apparently made DCS worse) however I’d be curious if the subsequent fix actually improves the experience with motion smoothing on for DCS. I found the SteamVRs implementation of motion smoothing slightly worse than ASW (Oculus’s implementation)... not by much but noteworthy. An improvement on the Steam side would be great IMO. Would be curious if any Index users out there give it a try (either in Beta or if it eventually gets rolled into stable) and notice improvements. In my experience motion smoothing would introduce a fair amount of warping artifacts (canopy bow on the FA-18, missiles tips on the wing tips warping during aggressive maneuvers or my least favorite seeing 2 - double vision - enemy planes when at a fast moving merge in a dogfight). ASW does it too just a bit less than Steams version. Maybe the new changes improve that? Disclaimer - I sent my Index kit back to Valve for a refund due to multiple RMA issues but I’m hoping quality control improves to the point I’d consider re-ordering again in the future. https://steamcommunity.com/games/250820/announcements/detail/1599262707997233111 Compositor Improved throttling logic when motion smoothing is enabled. Previously, throttling and prediction were locked together when motion smoothing is enabled. Last week throttling was temporarily disabled for cpu bound applications to help with No Man’s Sky, but made some other experiences worse (e.g. DCS World). This update allows throttling to back off of the prediction level based on the current average gpu performance. A typical example is when an app can render at half-rate (i.e. each rendered frame takes more than a single frame to finish, but less than two), but spends an extra frame on the cpu performing the draw calls, etc. This makes each of those frames a total of three frame latent, but can still deliver a new frame every other vsync interval. Note: This only applies to Lighthouse based hmds (e.g. Vive, Index) since most other headsets (e.g. Rift, WMR) use their own compositor and associated logic for throttling and prediction.

https://www.eurogamer.net/articles/digitalfoundry-2019-08-20-nvidia-gamescom-driver-adds-ultra-low-latency-mode-integer-scaling-and-other-fan-requested-features https://www.nvidia.com/en-us/geforce/news/gamescom-2019-game-ready-driver/?cjevent=86d99325c35b11e9819f00660a1c0e0f I suppose it’s a bit of a pipe dream to hope any of these new driver features would make a positive performance impact to DCS...

Interestingly enough I got the invite to join the private firmware beta as well last night. I’ll likely give it a go today when I get a chance. Few folks on Reddit are reporting improvement after installing so that’s something I suppose

+1 that's how I initiated my contact. Note it's taken NO LESS than just over 2 days for them to respond to me each response iteration so it's in your best interest to 1. Clearly state your issue and just as importantly what, if anything, you've done to test/resolve, etc the issue on your part. Different games, resolutions, SS, frequencies, GPU driver versions, USB/display ports. 2. include a system report generated from SteamVR and attach it to the support request. If you don't do the above you'll likely get a very canned response asking you to do very basic things (have you tried updating your GPU drivers? have you tried different ports? have you rebooted your computer?:doh:) at which point you will have to wait ANOTHER 2 days for a another response after doing what they said. You want your initial communication to be pretty comprehensive so you can cut to the chase and proceed with an RMA or pull the ripcord and send it back.