Twwhitey

Interesting - I did recently make the change to “Optimized for Performance” in the WMR (based on a YouTube recommendation I saw this weekend), that sounds like a very feasible cause. I will DEFINITELY try that once my 2nd attempt at a 240GB download and re-install completes.

Good question - I've toggled through all the Visib range" options (as well as the scenery details slider from 0.1 to 1.0) and it doesn't seem to matter. I broke down and decided to do a full on fresh OB re-install at the moment. Once completed I'll carefully start testing prior to and after adding the Kegetys Shader Mod to make sure it's not related to that... Its certainly not something the cross-eye recovery tool thing can seemingly fix either, the objects don't appear offset they're just flat out not rendering in the eye on the opposite side of the object.. note in the screenshots I'm adding I'm just highlighting super obvious examples... in game looking left and right by brain is going nuts because the scene is absolutely littered with missing objects in one eye depending on where I look, it's quite maddening...

Done. 2.7 VR Issue: Objects not rendering in both eyes

** Update - the fix for this (as noted by Maksim below) is ensuring that in WMR settings under "Headset display" you have "Experience options" set to "Best Visual quality". If you have it set to "Optimized for performance" you’ll experience the issue I was seeing below. Can't seem to rid myself of this issue on the Reverb G2 but since updating to 2.7... objects at a certain distance (not close but not too far away) don't render in both eyes resulting a weird headache and cross-eye inducing effect. Finally able to create a screenshot depicting the issue (notice the missing buildings in the right eye) ... anyone find a fix for this? Its present on every map and irrespective of airframe as far as I can tell (this is Syria, Beirut). I've tried all iterations of options.graphics.stereo_mode_use_shared_parser option (true, false and removed altogether) from the autoexec.cfg - no help.... Didn't have this issue on 2.5.6.. Any thoughts?

Yeah funny you mention that.. I just got finished watching a few YouTube’s (Redkites being one) detailing pretty profound side-by-side FPS differences between clouds = none and clouds = low, high, ultra. I was under the impression that most players were NOT seeing perf impacts... apparently not the case. I’m going to go back and retry today. I tend to use the Instant Action missions as my benchmark missions so I have to dig those out and update the cloud settings. I will say shortly before giving up yesterday I seemed to notice that on the same map some location (instant action Persian Gulf, Abu Dhabi) the perf differences between the Viper and F/A-18 was pretty profound. The Viper being way worse IMO... will play around more today.... *** Update *** You are correct..... I disabled clouds in my benchmarking missions (set Clouds preset to "Nothing") and it made a world of difference in frametimes and FPS.. so yeah... no free lunch with the new clouds.

Thank god for this thread.. I thought I was going crazy myself but there’s definitely something amiss. Flying around the F/A-18 free flight in the Persian Gulf (over Abu Dhabi I believe) there is definitely a weird effect with the buildings at a specific distance. Objects close and distant appear fine but there’s a distance like 3-5 miles where the term “distorted stereo rendering” sounds like the right description. I actually active paused at one point and noticed that there’s a threshold distance where small buildings or trees would render in one eye but not the other creating a weird single vision effect (like the HMD being rendered in one eye). I know that’s def an issue i.e. you can close one eye see a building/house then close the other and it’s not rendered yet... but I’m not sure if that’s the only issue though. I played around with the force_cross_eye_recovery_tool a bit to see if that helped but ultimately reset the values back to default projection. Ugh... a tough one to articulate for the testers....

*** reposting this in the proper thread... I will say - as far as 2.7 goes on my system ( ASUS Hero XI Wi-Fi MB, i9900K OC’d 5GHz, ASUS Tuf 3090 OC, Reverb G2) - I have noticed that densely populated areas on many maps (e.g. Beirut, Damascus, areas around Ramat David on the Syria map for instance) now absolutely choke/bottleneck the 3090 whereas same settings/drivers with 2.5.6 I could pretty comfortably maintain 90fps w/o needing to run motion smoothing. Now, in 2.7 I 100% need to run motion smoothing in order to negate stutters... despite the claim in the patch notes about perf improvements on Syria I’m definitely seeing the opposite... bumping the new scenery details and forest details sliders down to 0.1 don’t appear to alleviate the issues so I’m wondering if they wholesale increased the density of objects or something? I’ve lost just enough GPU headroom to cover those densely populated areas. Kind of a bummer because I was running pretty lean settings in 2.5.6 in order to run motion smoothing off (no shadows, no illumination, no lens flare/blur, no traffic, no ground clutter, medium distance, etc. just 2x MSAA, 50% SS, 1.0 PD, w/ Kegetys VR shaders) not really too much else I could dial down.... the good news is I think since I stopped using Steam Motion smoothing in the past they’ve definitely improved the algorithm quality... it’s much better in my limited experience so far than a year+ ago I think (less really bothersome artifacts). ive also noticed (again flying around places like Beirut, and this free flight with no other vehicles on the map, etc) that the CPU core DCS is running on is almost completely pegged the whole time... don’t think I noticed that before on 2.5.6. Clouds on or off don’t seem to make a difference so I guess kudos to ED for that but unfortunately my experience is that 2.7 doesn’t perform “better” than before in VR. Enabling ReBAR didn’t net any noticeable improvements so maybe a clean/reinstall is next... The never ending tweaking continues....

I will say - as far as 2.7 goes on my system ( ASUS Hero XI Wi-Fi MB, i9900K OC’d 5GHz, ASUS Tuf 3090 OC, Reverb G2) - I have noticed that densely populated areas on many maps (e.g. Beirut, Damascus, areas around Ramat David on the Syria map for instance) now absolutely choke/bottleneck the 3090 whereas same settings/drivers with 2.5.6 I could pretty comfortably maintain 90fps w/o needing to run motion smoothing. Now, in 2.7 I 100% need to run motion smoothing in order to negate stutters... despite the claim in the patch notes about perf improvements on Syria I’m definitely seeing the opposite... bumping the new scenery details and forest details sliders down to 0.1 don’t appear to alleviate the issues so I’m wondering if they wholesale increased the density of objects or something? I’ve lost just enough GPU headroom to cover those areas. Kind of a bummer because I was running pretty lean settings in 2.5.6 in order to run motion smoothing off (no shadows, no illumination, no lens flare/blur, no traffic, no ground clutter, medium distance, etc. just 2x MSAA, 50% SS, 1.0 PD, w/ Kegetys VR shaders) not really too much else I could dial down.... the good news is I think since I stopped using Steam Motion smoothing in the past they’ve definitely improved the algorithm quality... it’s much better in my limited experience so far than a year+ ago I think (less really bothersome artifacts). ive also noticed (again flying around places like Beirut, and this free flight with no other vehicles on the map, etc) that the CPU core DCS is running on is almost completely pegged the whole time... don’t think I noticed that before on 2.5.6. Clouds on or off don’t seem to make a difference so I guess kudos to ED for that but unfortunately my experience is that 2.7 doesn’t perform “better” than before in VR. Enabling ReBAR didn’t net any noticeable improvements so maybe a clean/reinstall is next... The never ending tweaking continues....

Just to add another unquantified data point seeing that ASUS released a BIOS update for the Z390 Hero XI MBs I went ahead and took the plunge this AM working through the process of activating ReBAR for DCS (ASUS Hero XI Wi-Fi MB, i9900K OC’d 5GHz, ASUS Tuf 3090 OC, Reverb G2). No real immediately noticeable improvement (or obvious degradation for that matter)... which I suppose is expected given it sounds like any perf gains won’t appear to be demonstrably overwhelming. Going to leave it activated and see if I notice anything worth reporting....

Unfortunately I don’t know if the 3080 Super is going to alleviate the issue for you. I recently noticed this issue on my system as well 32GB of RAM and an ASUS 3090 w 24GB. As stated above it only seems to occur on the Nevada. I don’t spend a ton of time on that map but recently put together a training mission with a mix of targets to practice various weapons on the F-16. Exiting the F10 map takes the somewhat rock solid 90fps down to 45-50fps for 2-4 seconds every time. Weird as I never noticed this before. I’m going to monkey around with FPSVR and see if something reportable is happening GPU, CPU or memory wise.. I had a theory this had something to with the fact I had all units “visible” on the map with a group of enemy vehicles “moving” with waypoints etc but I have no evidence that has anything to with it. Somewhat reassured it’s not just me...

Facebook :doh: Reverb G2 can’t come fast enough...

Ahhhh ok got it and that likely explains my issue. The YouTube tutorial I watched yesterday the guy landed at Kutasi and got clearance for 070 hence all was peachy in that direction and naturally there was no mention of non-ILS runways or runway specific ILS. Good stuff and thanks all for the explanation I knew it was something that I was missing...

So that's interesting and potentially the issue. The Kneeboards for both Kutasi and Kobuleti show the ILS frequencies for Runways 070 (apparently they both have 070 runways) but the Kneeboards don't show ILS frequencies for the reciprocal runways (250). I've programmed in the frequencies for runway 70 but the tower always gives me clearance for runways 250... if I've neither programmed in the ILS for that runway or they don't tell me to land on 070 I guess I won't get an ILS signal then right?

Ironically enough I tried Kutasi first same flight. I was using the Instant Action "Free Flight" mission for the F-16 which starts you like 50 miles east of Kutasi so I headed that way, dialed in all the specifics and basically got the same result at Kutasi so I figured "maybe that airfield is buggy" let me try another and headed to Kobuleti... same result at both... Hmmm maybe the Instant Action Missions are buggy in general? Maybe I'll fire up a complete different or new mission...

Interesting... next attempt I'll check that. I was indeed hearing audible beeping (which I assumed was the TACAN) but I definitely have not checked the Volume or ON/OFF status of both on the audio panel. Thanks for input I'll give it a check!

Lord help me but for the life of me, no matter how many tutorials I watch or how many times I try, I can't seem figure out how to get the ILS needles on the Viper to work when practicing landings. Pardon the terrible screenshot but take this approach into Kobuleti for instance... I configured the following: TACAN: 67X Mode: REC (but tried T/R mode as well) ILS: ON; Channel 111.50; CRS: 248 HSI: Mode PLS/TCN No matter what I do, the ILS needles in the HUD and in the artificial horizon are always pinned to the top left with those RED indicators showing. Can anyone help me figure out what I'm missing? Surprisingly google and forum searches yield nothing so I'm definitely doing something wrong because I've seen multiple youtube videos of this working and thought I was performing the correct steps...

Well not sure about the relevance but I placed my pre-order on 5/29 and my order status on the Connections website states “Backordered” as well. I have NOT received an email stating that but the order status page is pretty clear...

For those using the Keyboard version that (apparently) doesn't save the on/off state between sessions I finally took the time to dig through the LUA code to figure out how to change the default state to off (so you don't need to turn it off EVERY TIME YOU LOAD DCS). In the Scripts\Hooks\scratchpad-hook.lua file (again this is the Keyboard version of the scratchpad provided a few pages back), uncomment the scratchpad.hide() function call at line 1478. Should look something like this when uncommented. (Turns out I don't speak/read Romanian but "sa apara ascuns" means something along the lines of "to appear hidden" according to google so this makes sense!) scratchpad.hide() --sa apara ascuns The scratchpad is now hidden on load and you can bring up using the usual hot-key when you need it in cockpit.

So the F-16 ICP is showing as Out of Stock and the ViperGear folks seem to have gone radio silent for awhile. Does anyone know if they'll be kicking off another production run of these bad boys in the near future? I'd preorder if given the option... #takemymoney!

Scratchpad + onscreen keyboard. Absolutely brilliant script/mod for VR users. Why did I wait so long to do this... great stuff and thanks to the designers!

Just adding my name to the interested list for something like this. This doesn’t seem like an outrageous ask and would spice up some of the persistent dynamic SP missions I spend most of my time in. Would be great to load up the usual mission and have it’s time & weather conditions randomly changed (the METAR stuff would be absolute gravy on top!) Anyone have anything close?

This is interesting - with all the “free time” I’ve got at the moment I’ve wanted to try and augment Surrexens great missions in a way to tie runway/airbase attacks/damage to the deactivation of the enemy caps... and then try to find a way to incorporate the fact that an airbase/cap is out of commission into the info saved in the persistence data. This would allow single players (like me) to make all out attempts to bomb enemy cap airfields in an effort to gain air superiority so that you then shift to CAS/Ground attack using the A-10 (which generally doesn’t last long even with support packages tagging along). This is interesting I wonder if it works. The only problem at the moment is the latest few DCS updates have really borked performance for me in these missions. I’ve been pretty much immune to poor FPS forever but I fired up v122 of the Clearfield mission last night and the FPS I was getting was 60%-70% worse than usual...pretty sad.

Yeah I poked around a bit today and couldn’t seem to find a way to utilize them whereas as you say the ED Miles option is front and center. I think it may have something to do with the fact that all the existing modules are already steeply (50%) discounted.. that’s my theory at least... Anyhow thanks for chiming in!

Hmmm ok. Yes that’s the question I had. I appear able to easily apply the ED Miles but couldn’t find any mechanism to use the Bonus points and this was after getting to the external system that processes credit card payments. I’ll take your suggestion and try again maybe I’m just missing it. Thanks!

Thanks for the response BN.. I did come across that page before and it’s...well...about as clear as mud. :) Still have no idea if it’s possible to use my accrued bonus points for the P-51D (i.e. “participating in the bonus program”?) and if so, how to actually do so... At this point I’ll just assume given the shift to ED miles those points are worthless and will just expire in a few months... Thanks anyhow cheers