Nagilem

@Supmua - I am surprised by this. I get very consistent game play with 6 cores and 6 HTs dedicated to DCS and the VRcompositor on 2 cores/HTs, and anything else That runs during my DCS sessions setup on one of those two cores. I set DCS and VRCompositor as high or very high priority.

@LeCuvier - Thank you sir! You got all of my issues resolved! Both code snippets work great and the suggestion for the KB worked like a charm. Thanks again!

So after reading all of this, I think what is being said from a put into practice list is - 1. radar acquires targets as radar bricks or HAFUs if donated 2. One can use TDC press to L&S one target, and DT2 a second target giving some info 3. As targets approach, TDC Depress on either target OR SCS toward the radar ddi should move the L&S contact to STT 4. Employ weapons and SCS right to AACQ the DT2 target Does this sound correct? In all of the talk between real and in sim, I am trying to understand what is available and how to employ. What I have found so far is AACQ does not priority lock the L&S contact, so I end up having something random locked and having to use the cursor with TDC press to STT the specific target I had L&S (or DT2) soft locked.

@supmua - I don't think MFAA does anything without in game MSAA on. Are you noticing better aa with it on without in game MSAA?

Ok. Got the goggles working... Having issues with Flashlight, Kb pop, and Hook bypass. I can get the switch to work with up once for on up again for off configuration that is default, but none of them work as a toggle. Any ideas for the F-18?

I am currently flying the hornet and having some issues with creating toggles. Ive created something for my Master Arm, but these two don't look to have the code in the default lua for the toggle. I would like to have toggles with warthog switches for Flashlight NVG goggles activation Kneeboard Pop up I am looking to NOT have to use the toggle twice... Anyone already solved these? I did some searches but nothing is popping up.

@pchRage - before you fully reinstall, rename your saved games\dcs openbeta folder to .old and restart DCS. Most of the settings are saved there. You may have a corrupted file. If you rename it, DCS will create a new one. Then you can selectively move over what you want to reuse... I moved over my controls folder, mission folder, and a few of the mods I have when I had frame issues. Something got corrupted and caused me massive stutters until I recreated the saved games folder. I now keep a fresh copy on hand just in case, and manually sync the pertinent folders for what I create.

@chief - just curious to know if you are saying that ED chooses not to use the correct model for the 54 for the purpose of making the F-14 more desirable? The folks that I see flying the F-14 would likely fly it no matter what... They like the AC. I wonder how much impact on sales there would be if they nerfed the 54 back to reality?

https://bitsum.com/

I don’t have any issues with my index. Sounds like you got a bad one. I’d contact steam support. Have you tried any other games? Do you have any issues in steamvr home?

You may want to look into something like process lasso to set up specific cores in your processor for VR vs DCS. I saw my game smooth out quite a bit through the affinity assignment of specific cores and HTs. I currently have 1 core +HT affinity set for the support apps (srs, VA, etc), 1 core +HT for VRcompositor, and 6 cores +HTs for DCS. That seems to give me a good balance and the best smoothness in game. I'd also turn everything down first, get the visuals to move smoothly first, then ratchet up the SS resolution and the post processing effects (MSAA, MFAA, AF, etc.). That way you can judge what is worth turning on and what isn't. Personally I want smooth over less shimmer. That is put me at SS 148/138 in Steam VR with AF set to x2 in game. I had to do the processor affinity work first to get and keep the game smooth.

Doing a bit of reading - I don't think MFAA does anything UNLESS MSAA is already on. The algorithm forces MSAA to use frames over time to improve the AA. If you have MFAA on without MSAA I don't think its doing anything.

@Glyn - I would get one headset and two base units. You can use v1 base units if you can find them to make the cost lower. While 'technically' you could get away with one, you will be moving around a lot to check six and one base may not give you enough coverage.

@imacken - if you are running MSAA anyway you should consider using MFAA as it will provide more AA for very little performance cost. You set up MFAA in the Nvidia Control panel.

Ok - some additional testing Goal is flying downtown Dubai with frame times of 18-19ms with good smoothness and good anti-aliasing. Baseline Settings: SteamVR:1.7.13 beta running 90hz NVidia Driver: Latest as of 8/30 with NVCP setup with max performance and almost all other settings vanilla. DCS: All textures high, cockpit at 512, no grass, 50% trees, all shadows flat, preload max, visibility set to high, and no AF. Premise: I wanted to look at the difference between high super sampling via SteamVR (video/app settings) vs using MSAA with MFAA. I tested three scenarios: Scenario 1: SteamVR SS ( 148/138 ) with motion smoothing on with no AA; Performance: reasonable, vCard maintaining ~80% @ 70c, frame times stay within 14-18ms on average Experience: smooth with some visible artifacts at the edges; some shimmer with aliasing; no significant stutters even with hard plane maneuvers but the frame times pushed 20ms during these times Scenario 2: SteamVR SS ( 148/148 ) with motion smoothing on: Performance: pushing the edge, vCard ~90% @ 70-71c, frame times range generally 18-24ms with periods of much higher when the CPU or GPU peg Experience: mostly smooth with more warping and ghosting; shimmer is low but not very noticeable; a few more noticeable stutters when aggressively moving the plane Scenario 3: moved SteamVR back to default ( 150/100 ) and turned on MSAAx2 AND MFAA in NVCP. MFAA allows more anti-aliasing in MSAA while also lowering performance threshold Performance: pushing the edge, vCard ~90% @ 70-71c, frame ranges generally 18-24ms Experience: Smooth with nominal artifacts, shimmer is non existent, distance objects are softer with less super sampling but very playable/recognizable. TL;DR - Performance is about trade offs. If one wants higher clarity and can live with some shimmer, turn MSAA off, increase the SS in Steam, and tune resolution to your card capability. with my card 148/138-148 works, but starts to seriously tax the vCard as I push the app resolution up. If you want to kill shimmer, turn MSAA x2 with MFAA turned on in NVCP and lower the Steam Settings to default. No shimmer, but not quite as clear in the distance. performance seems quite good in my opinion, these two sets have similar performance in terms of frame times in this testing scenario, but experience is at the extremes - more clarity vs less shimmer. More testing in MP and other scenes will be needed.

Oh, and I saw there is a bug report for water reflection shimmer with DCS weather set to dynamic. Will also test that.

Thanks guys - I'll push water back up to high. I have a few mods to add equipment and such into the game, a NVG mod to bring NVGs in the cockpit into focus, and one to make the Stennis look more realistic and fix the IFLOS. Nothing that changes the shaders, and definitely NOT Kegetys hack. I decided to move to 148/148 split and have seen "similarish" results with 45 fps over Dubai at 90hz and frame times in the low 18s. Not sure I'll leave it, but it cleaned up more jaggies, and that still performs better than MSAA x2 which blew out the frame times to over 22+ms with 148/138. I'll keep working it :) Thanks again!

@WIcked - I know what you mean. We tweak, but it should be about dropping planes and breaking stuff on the ground :). My biggest frustration right now is water. When I fly over water with my textures at medium, I get what I call "shimmies" all over the place. The carrier will be rock solid, then just out of no where vibrate back and forth, then settle. Happens to my hud elements too. Almost like a glitch. I also get serious flicker when I see reflected sunlight on water. Happens 70% of the time. Very annoying. Anyone else have these issues? I haven't tried dialing up the textures yet. Water is one of those that kills frame rates. Will do some testing tonight / tomorrow and see what happens. I suspect these are issues that will not get resolved soon.

@wicked - On the 150/138, I did set 148 but steam keeps reverting it up to 150 and the app page resolution shows the same so I left it. I went back to stable SteamVR for now since I wasn't happy with all of the changes and such on beta. I may try it again sometime. With AF at 8x, and making some minor adjustments to my nvidia driver for DCS - High performance power, AF Sample optimization on, negative LOD bias set to clamp, TF Quality high perf, and trilinear optimization on, I get a decent balance between smooth and reasonably low shimmer. Its not perfect, and it never will be until we get more CPU and GPU power, but I do get good performance with good visuals and I am happy. Hopefully they work for you. On HT, I have not overclocked because I live in a hot climate (80 here in the house during the summer months) and I want the chip to throttle to stay cooler (I'm one of those who don't believe water and electricity should mix ;)), so leaving the HT on with my current setup leaves me with temps in the low 60s on average with utilization averaging 60-70%. I run scripts in DCS so I think some of that extra CPU load is MOOSE and Airboss.

I've taken to using process lasso to help prioritize the apps running during my sessions. I have a 9900k so I have 8 cores. I use 1 core for all my helper apps (viacomm/VA, SRS, etc), 2 cores for VRCompositor, and the rest to DCS. I know folks say only 2 cores get used, but I can tell you, all my DCS cores light up when I start playing. I leave HT on because I get much smoother and better performance with my chip. Others may have a different experience. Definitely had to watch Process Lasso for a while to make sure no other services started to keep the experience in game smooth. Result - I get smooth gameplay everywhere with consistent FPS @45 and frame times ~12-15ms @90hz. I prioritized smoothness over game looks so I have SS set to 150/138 in Steam with motion smoothing on. In DCS I have only AF on at 8x, textures high, water medium with shadows flat. I had cockpit shadows to low and it worked fine, but was a bit distracting for me. I turned off MSAA as it killed frames bad. Just some additional food for thought / suggestion. YMMV

I agree with pappavis - index FTW. It’s comfy, sounds great, and with a a bit of tuning, performs amazing. Every headset is a trade off. Just go in with that mind. I tried the reverb as well and found the trade off wasn’t worth it. I skipped the rift s as I wanted sound and more adjustability. YMMV.

Curious - anyone get viacomm working with Airboss? Will import f10 pull in the menu keywords or is some other action required to enable those f10 menus in viacomm?

@Alec DeLorean - Thank you for the suggestion... I tried disabling the HT procs for 9 and 11 and found my performance in frame times got significantly worse. Many more late frames (red) in frame time graph than with the HT processors on. With HT enabled on the procs, Dubai flows smoothly by at ~18ms frame times with very late (red) frames. Also tried turning motion smoothing off to see if ghosting on other AC went away. And while turning it off lessened the ghosting with planes ever so slightly, having it off also caused ground objects (buildings and terrain) to judder badly and also lost some of the sharpness. WIth motion smoothing on, I see the ghosting around other AC and not buildings or other static objects that move relative to me or my AC. It seems the computations for relative motion between my AC which is moving in one plane of motion, and the other object moving in another plane of motion is the main correlation I can find to ghosting. With motion smoothing on and static objects moving in relation to my plane of motion have no ghosting issues.

So I've been working quite a bit to figure out how to get the best performance I can from my index. I do subscribe to SteamVR beta. For my settings, I keep all of the image processing outside of DCS - no MSAA or AF, PD @1.0, shadows flat, water med, terrain set low, with other textures high, put preload and visibility to max (150000 and extreme) I've setup steamvr to use a global setting of 100% with motion smoothing on, and an app setting of 200% for DCS.exe. I run @90hz. I have also done some work through Process Lasso to set 2 processors (8 and 10 with their HT counterparts checked) for DCS, and remove the VRCompositor and VRserver processes from those same processors. I've set all three to higher priority settings to keep the data flowing. What I am getting from all of this is 45+ frames flying low in Dubai with frame times ranging between 16ms to ~19ms, mostly yellow with very few reds. Mostly getting good visuals inside the game with some warping / tearing looking to the sides as buildings and scene go by fast. I get *some* shimmer from aliasing, but overall the aliasing is not bad. The only thing that is tough is getting up close to aircraft or moving my head tends to make those things fuzzy or look like double vision - with more significant ghosting the faster the objects are moving in relation to me. I guess I should count my blessings as I am getting decent performance with very few issues. I haven not really had the vertical line issue, and overall the experience with the index has been great. Anyone have any other thoughts on how to improve the warping / ghosting issues? any other thoughts on settings to improve performance?

App still does not work for me in VR. I can get it to work on my monitor. I press the hotkeys and nothing happens. Not sure why. Anyonelese having issues? I have an index. That is the only change I've made since it stopped working.