Nagilem

Yup - sounds about right for a 2080 card. You can dial back the SS to 160% and still get a pretty great experience. I am using 200% to test out driving HP reverb level pixels. @180, I was getting better performance with no stuttering or micro judders. Even at 150% or 160% it should look pretty darn good. That may give your 2080 a bit more headroom to keep up. That's where I would start first. I'd leave the rest in place. Also, do be sure to look at the Process Lasso piece, that did help my stutters caused by processor affinity issues with DCS on my CPU. basically Process Lasso sets the CPU to single cpu no Hyper threading, and pushes the priority of the DCS.exe to higher in the stack.

@Alec D - not yet but on the list to purchase. Using MSI I get what you suggested with all cores showing 30-40% Will get it so we can see what that tape says.

I've gotten consistent kills with C variant at 50miles from A34 @ 275kts

What I have found so far is the Probability of kill or even damage to radars or other vehicles like URALs is actually minimal. The only way I've gotten the 154 a to damage the Hawk radar units I released them on is to lower the burst altitude to 500ft and even then it only slightly damaged a few of them. Testing - from carrier, no real wind, 8 JSOW As in test 1 and Cs in test 2 On Test 1 with As, put in a target coordinates, set half to burst at 900 and the others at 500 - result, two of eight targets were lightly damaged. Previous tests with As at 900ft yielded no kills or damage to any targets... On Test 2 with Cs, all 8 targets fully destroyed. (same coordinates means I have correctly targeted the Hawks and URALs) With these results, I am not really seeing a use for the A Variant.

So after completing some very unscientific testing, I am finding that the 154A will only kill radars and equipment if the height is set very low. I just reran my missions from last night: 1. I made a change to lower the height of the a variant on 3 of them to 500 ft. 2. The three at 500 ft produced 2 kills, all others set to 900 (per video) did nothing against Hawk radars and insurgent positions 3 Reran the same mission, same coordinates, scored 8 kills with C variant so coordinates are correct. Maybe the A variant BLU97 bomblets are under-powered? or is the expectation that burst altitude must be very low and Pk for A variant is low as a cluster munition? Just looking to understand the weapon better to know how and when to employ.

Is it just me or is this starting to feel like the hamster wheel of waiting for the next HMD to release? HAHA "We'll get'em next time" comes to mind... I suspect we are where we are for the next year or two unless Samsung or Sony have some uber secret project in the wings. I *personally* haven't had great luck with Acer so I'll likely pass. I hope the reverb I get sent has no issues so I can really see how the extra pixels change my DCS experience.

@AA Thank you sir. @Alec Delorean - I know there is a penalty to MSAAx2 to a degree, but I will say that the game shimmers something awful without it for any fine textures - buildings, ships, even some planes. I mean really bad. No other Anti Aliasing has had significant effect for me in DCS other than MSAA. I don't use SSAA because I agree with you, the penalty not worth the gain. I have also tried the nvidia settings with nearly unnoticeable results. Also, the biggest change I made with 2.5.5 is moving the SS from DCS to Steam. Since the SteamVR engine is working with WMR to reproject at 45FPS, moving the SS values to 180% or 200% gave me much better performance and a lot less ghosting and artifacts with higher clarity. I mean A LOT. I guess that makes sense since it reduces the complexity by limiting the render process to 1-2 engines (either just steam, or steam and WMR) vs 3 (Steam, WMR, AND DCS). I think there may still be issues with DCS's rendering engine for Super Sampling. And with them changing the code to add in the VR optimizations, my ghosting and artifiacting with DCS at PD 1.3-1.5 was high after the patch. If you look at the link I put in for the o+ settings earlier, you will see my GPU isn't pegged, my CPU is just above idle, and I am getting what I consider to be excellent image clarity @ a consistent 45FPS. Where the rubber meets the road for this thread is I plan to continue with the Index to use Steam for motion reprojection and SS, and leave DCS at PD 1.0 with MSAAx2 and AF. I am very much looking forward to seeing how the Index performs!

I had some successful tests tonight though I am tired of entering coordinates until my eyes cross :doh:. My understanding is that the A variant has the BLU-97/B munition. From Wikipedia (I know, I know, not the best, but this is quick and dirty :)) The BLU-97/B Combined Effects Bomb is the submunition used in several cluster bomb type weapon systems. When the bomblets fall, they separate from the main bomb and independently free fall to the ground. They contain an inflatable bag (ballute) on the top of them, which slows them down and spreads them out. Once the bomblets reach a force of 6 Gs they arm themselves. As the bomblets fall, they are also spinning. Arming takes about 2.6 seconds. They have a combined shaped charge, fragmentation and incendiary effect on the target. It is very effective against and mainly used for anti-personnel, anti-materiel, and anti-armor. Given what is above, shouldn't this be able to destroy SAM sites with a burst height of 900 ft? Shot 8 off at a Hawk site tonight with no kills (I did screw up the launch so 4 targets got two As a piece). Changed them to C variant 8 kills (with proper drop) @ 50 miles. Coordinates for them were the exact same. Am I missing something?

With all of the mission planning that happens, I would really hope we get a data cartridge type function to setup GPS weapons and other jet prefs once in the mission so I don't have to spend 20 mins on the ground typing in the coordinates.... Pretty please? :)

hmmm. Will test that tomorrow to see if that changes things.

Thanks TacKen! That does help quite a bit.. so most of the actual turbulence emanates outward along the wingtips then? From you are saying, it seems what I've seen in wake turb during refueling may be a touch too much. A small burble with some minor jetwash. Is that a good summary?

BTW - I am using 200% SS in Steam not because it looks that much better, but rather because I am stress testing for when the Reverb arrives. Turning it down to 180% still looked very good with slightly more consistent performance. YMMV

@AA - I just posted this... https://forums.eagle.ru/showpost.php?p=3950179&postcount=35 These settings have been working great on the o+. 45FPS with little to no shimmer or stuttering. If you have time and can try them, maybe they would work well for you...

Actually I have - What I have found with my tinkering is this - I only do post processing stuff (MSAA and AF) in DCS because changes in SS in DCS stutters and ghosts really badly for me. I moved the SS to SteamVR since that is also where the Reprojection is happening. So my current settings that are working fantastically are: NVidia MFAA on Power set to Performance All else pretty much default (FXAA and AF off or redirected to the application) WMR 90hz Visual quality set to VERY HIGH BETA SteamVR Motion Reprojection set to Auto (set in the default.vrsettings file) https://steamcommunity.com/games/719950/announcements/detail/1652133167137673234 SteamSS set to 200% Nothing else really set here other than turn off the dev SS DCS Textures high *except the water which is medium Shadows both flat MSAA x2 AF at 8 No grass, half trees Preload max Object distance high Most everything else is turned off or low PD set to 1.0 - you either set it in DCS or Steam. I choose Steam since that works better for me with reprojection. ALOT LESS GHOSTING and Artifacts. Everything else to taste ;) I can consistently get 45 frames flying downtown Dubai and only very occasional stutters with everything looking crisp and not jaggy. One other thing I did was to install Process Lasso to fix DCS CPU Affinity problems. This fixed those weird out of the blue stutters (CPU >30% AVG with GPU in 70% range and are smooth 95% of the time). https://forums.eagle.ru/showpost.php?p=3947114&postcount=1573 Let me know what you think!

@trigen - I know what you mean about O+. It is a very good headset. My biggest issue, and why I am looking for a new set is the lack of clarity out of the pit. Seeing things at a distance is very fuzzy due to that anti SDE film. I get why they did it, and I do think it would be awesome in non detail games, but DCS we need to see clearly both in and out of the cockpit. I am HOPEFULLY getting a Reverb and an Index by end of the month. Fingers crossed one of them performs!

JSOW AGM154 A Question I had some successful tests tonight though I am tired of entering coordinates until my eyes cross :doh:. My understanding is that the A variant has the BLU-97/B munition. From Wikipedia (I know, I know, not the best, but this is quick and dirty :)) The BLU-97/B Combined Effects Bomb is the submunition used in several cluster bomb type weapon systems. When the bomblets fall, they separate from the main bomb and independently free fall to the ground. They contain an inflatable bag (ballute) on the top of them, which slows them down and spreads them out. Once the bomblets reach a force of 6 Gs they arm themselves. As the bomblets fall, they are also spinning. Arming takes about 2.6 seconds. They have a combined shaped charge, fragmentation and incendiary effect on the target. It is very effective against and mainly used for anti-personnel, anti-materiel, and anti-armor. Given what is above, shouldn't this be able to destroy SAM sites with a burst height of 900 ft? Shot 8 off at a Hawk site tonight with no kills (I did screw up the launch so 4 targets got two As a piece). Changed them to C variant 8 kills (with proper drop) @ 50 miles. Coordinates for them were the exact same. Am I missing something?

@Hunchy - Also try the Process Lasso updates to fix CPU Affinity. I had issues with stuttering that using PL took care of... My post on that is earlier in this thread.

I've been holding off on the nvidia driver update from 5/27 since I had seen some folks having issues with it. 430.86 is the release version for that time. Anyone here having issues with that driver?

Not sure - but make sure the action to turn on the tacan and ICLS happens on every Stennis WP. SOme have reported that the TCN turns off upon reaching a new waypoint.

@Alec Delorean - Thanks for the catch on the thread switch - these are all starting to look alike haha For those that are interested - Ok - quickly tried the Process Lasso suggestion and it cleared up my stuttering issues. I have pushed the SteamVR SS to 180% and 200% with 8x AF, no MSAA, and I got 45 frames consistent, no stuttering in the Sochi Free Flight. Interestingly, my CPU and GPU utilization still stayed at ~50% in MSI, which puzzled me with the jump from 180% to 200%. Need to do more specific testing but it is definitely SMOOTHER. :EDIT: Flew for several hours in all kinds of terrains and found my stutters have been resolved. I didn't check MSI, but as you will see below I have one other item to test... Will provide any tangible results I get. Process Lasso config for DCS Priority Class - high CPU Affinity - left it alone; there is no Single CPU option on the newer version. Default was no affinity :EDIT: Was suggested to disable HyperThreading on the processor for this option, which I will try tomorrow, though things are much better than they were with HT on. IO Priority - high Application Power Priority - High Performance I didn't set the mem priority so that stayed as is which I think was defaulted to normal (highest available setting) Good stuff - Thanks Alec DeLorean and FearlessFrog. This experience is getting much better on my current hardware, which will be really amazing on Index!

not sure how much this will help but this guy has a reverb and talks about pros and cons... he is coming from a rift cv1 and o+ I believe... https://forums.mudspike.com/t/vr-news-hp-reverb-second-gen-headsets-are-on-the-way/8165/346

@harlikwin - so what I am doing now is validating my configuration with what I have since the Reverb will just likely be more of the same, just at a higher res. I figure if the WMR, SteamVR, and DCS settings give me a good experience before the Reverb arrives, I'll be in a better position to see the difference the native HMD resolution makes. This is also a learning journey for me in terms of getting good VR clarity with other apps. Since I decided to get an index, I am likely going to expand my VR experience beyond DCS. I've played Elite Dangerous and would like to try Onward, and a few other titles. I think I can say DCS is likely one of the most demanding titles for VR.

@Harlikwin - less boost more clarity...Reverb and Index are both on the way... What can I say? I'm spoiled :P

Ok - quickly tried the Process Lasso suggestion and it cleared up my stuttering issues. I have pushed the SteamVR SS to 180% and 200% with 8x AF, no MSAA, and I got 45 frames consistent, no stuttering in the Sochi Free Flight. Interestingly, my CPU and GPU utilization still stayed at ~50% in MSI, which puzzled me with the jump from 180% to 200%. Need to do more specific testing but it is definitely SMOOTHER. Process Lasso config for DCS Priority Class - high CPU Affinity - left it alone; there is no Single CPU option on the newer version. Default was no affinity IO Priority - high Application Power Priority - High Performance I didn't set the mem priority so that stayed as is which I think was defaulted to normal (highest available setting) Good stuff - Thanks Alec DeLorean and FearlessFrog. This experience is getting much better on my current hardware, which will be really amazing on the new hardware!

@Alec DeLorean - Thanks for that. I will take a look. Just curious, do you run processlasso every time you go into DCS? or just once? How does this fix processor affinity? I saw the PDF, but the how and why weren't very clear...