Mnemonic

All settings are in first post. On your discretion, in my case with all the rest of the settings 4x produced less jugged lines, and didn’t impact performance. I use MSAA Radius = 30%

Theoretically if you can fit textures + all the buffers with PD>1 into your’s GPU VRAM then you’re good to go! Actually it works for me with default empty carrier just fine. But I like to fly with Supercarrier, loaded with other Tomcats, Hornets and equipment, so didn’t really worked out. I didn’t try to go for Low textures though, it might work.

Just for illustration purposes, here are some of my measurements with MSI Afterburner. With PD=1, I have VRAM usage stabilized around 7.2 GB, with some headroom for new units that can appear in sight. Same level, same scene PD=1.4 - VRAM fully clogs at 8GB and jumps a little as GPU offloads and downloads textures from RAM. Witch leads to stuttering in VR. The progression is actually should be non-linear but square, so 11GB would not help, 16GB or more could help a bit. So here is a reason, MSAA which is computationally expensive, actually works well, because GPU has resources to render them, but PD that increases all render buffers doesn't let any room to VRAM.

Well we have a new setting in DCS - MSAA Mask

Good to know! DCS has it's own feature now, with kinda similar goal (MSAA mask). Thanks for clarifying it, scratched out of the post!

Thank you! I have a driver 445.87 it could be just RTX setting, not sure at the moment.

I have added my missions that I use to test to the first post. The "heaviest" one is not that heavy, but it has reasonably populated deck and things are moving :)

1.4 sure looks sharper, I used to fly with 1.4 all the time. But it does take it's tall. It all depends on your scenario, if you put a Hornet at Tsenaki Kolkhi on the empty airfield, sure it will not impact at all, and will look better. What I'm writing here is about reasonably populated Super Carrier, with light rain, in an F-14 Tomcat. And staying above 40 FPS. You will see that PD influences size of all render buffers that DCS uses, as such uses more VRAM, add many more textures and you have a recipe for FPS drop.

Happy for you, if that works for you - awesome, less things to render

Yes, that’s why I recommend “Medium” shadows. High - eats too much resources, low doesn’t look as good, but at least have it in Low/Medium than no shadows at all, without shadows there are too many incorrectly lit surfaces in the cockpit that flicker too much because of high contrast. Much better to have any shadows than this.

Yes put 1024 for the screens if you fly Hornet. For the F-14, 512 Every Frame is sufficient, and doesn't impact frames as much as 1024. Honestly in Hornet 512 screens work fine for me. PD is the biggest FPS killer, look at all other settings I published, that's why to get to "never drop below 40" I opted to get more AA vs more PD, because my RTX2080 has enough power to do AA, but not enough VRAM to have high PD with the rest of the things on my test mission. And I used to fly with PD = 1.4 before Supercarrier.

Thank you! No, Oculus Tray Tool was tested during this, I played with all the settings. Change in PD in DCS vs change PD in Oculus Tool doesn't give any benefits in performance. It's practically doing the same thing, so you can just use the one in game. In the end Oculus Tray tool was not used here.

And few more...

More pics:

Since Supercarrier have been released in Open Beta I was spending quite a bit of time revisiting my "VR" settings. The settings and tuning process I describe here allow me to enjoy rich scenarios, with weather, lights, and even mirrors in the cockpit enabled. Previously I aimed to have as high as possible Pixel Density (1.4), highest shadows, textures, and sacrificing the rest, flying only missions that can sustain such settings (empty Stennis deck), and ignoring occasional stutters. While an "Empty" Supercarrier in a good weather worked pretty much ok with just me flying circles around, I thought it's not really fun to do this, since with new carrier I want to have other planes and static crew on the deck, for more alive scenarios. And in such case performance hit can be quite large. I also love to fly an F-14B, and F-14B is known to be a module that "heavy" on resources, combined with Supercarrier it gave me quite a bit more stuttering than usual. So if these setting work for F-14, they for sure will work for F/A-18C!. As most of the players will have different hardware, I would describe my approach toward tweaking settings. Here is my config: i9 9900KS (@5Ghz), 64 Gb RAM, RTX 2080 Super (8Gb VRAM), DCS is installed on NVMe SSD. I use Oculus Rift-S for VR flying. With my config (or with any other config for that matter) I can't just max everything out and enjoy a smooth high FPS in VR. The Goal: If I want to have smooth true-to-life experience I need to have at least 40 FPS minimum, in every scenario. Very occasional drops below 40 is acceptable, but very rarely. 80 FPS - will give me native refresh rate of Rift-S (ideal scenario) 40 FPS (or anything between 40-80) will fit into ASW area where Oculus drivers do really good job smoothing out translational changes in the picture when looking around the cockpit. And no, I can't fly without ASW, like some people recommend to have "Higher FPS", without ASW if you don't have 80 FPS, view in the Rift will stutter a lot. So, with all that aside, let's start with playing around: - First of all, start with "VR" preset. To my surprise it worked very well from the get-go even on relatively populated deck. Eagle Dynamics really tuned this well, it looks surprisingly good and works smooth. - Second, try to play with Pixel Density, keep in mind though, that in populated areas, like Carrier Deck, higher PD settings will have huge impact on overall performance. Usually people exchange Anti-Aliasing(like MSAA) for Pixel Density, in my case I see it worked great in the opposite scenario. I put PD = 1, and put maximum MSAA possible, limiting it to 30% area on screen, which worked wonders. - MSAA, see previous point, why I put it to max to get smoothest picture with PD = 1. - Textures! Usually I would put it to max, however, in VR, with defferred renderer that DCS has, with texture heavy modules, like F-14 and Supercarrier - VRAM consumption can get really high (see here), and having 8GB of VRAM might not be enough (Another point for lowering PD). Put textures to Medium, and free-up some performance for other stuff. You'll get a bit blurrier picture, but if you can tolerate it, trust me it's worth it. Additionally, if you have lower grade GPU, you might want to download reduced cockpit textures for DCS F-14: https://www.digitalcombatsimulator.com/en/files/3303917/?sphrase_id=1255299 Look quite nice, occupy much less VRAM. Note - in the following screenshots I don't use it. - Set the shadow setting, it comes with performance hit, however it alleviates a lot of artifacts on screen, especially in the cockpit, so I would strongly recommend to enable shadows. I found that Medium setting shadows do look fairly good in DCS (better than I remembered them before) and significantly faster to render than High setting shadows. EDIT: Actually I noticed that with beefy GPU you can crank Shadows to High, keeping performance relatively good, but leaving less headroom for other things. Also I did a little comparison of running without shadows and with shadows, to show the artifacts of not having shadows on: Here For late evening / night flying, disable shadows altogether, it improves FPS on the deck when Super Carrier has it's lights on, and at night there are no cockpit shadows anyway. I have created 2 presets for Day / Night flying and then switch before flying. - Mirrors, I found that using mirrors helps me in an F-14 during landing to check status of my DLCs (and totally not used in F/A-18 ). Also it's very cool to see pilot saluting in the mirror on take off, such a cool immersion factor. To have fair quality mirrors, I use Resolution of cockpit displays: 512 Every Frame setting, that works fine with ASW. I also mapped it to my free joystick control so I can flip it whenever I feel like it. - Last but not least, be moderate in your SC missions, too much crowd on the deck will drop your FPS any way, but empty deck is no good either, experiment! NVidia Control panel settings: - Power Management = Prefer maximum performance (obviously) - Texture filtering - Quality = Higher performance (This doesn't look obvious but it does influence performance, especially if there are a lot textures in the scene and we count milliseconds here) - Texture filtering - Negative LOD bias = Allow - Texture filtering - Anisotropic sample optimization = On - Virtual Reality pre-rendered frames = 4 (this can smooth out occasional stutters big deal) - Virtual Reality - Variable Rate Super Sampling = Adaptive (Didn't found out if works with DCS native MSAA setting or not, but kept it) EDIT: doesn't work with DCS, so ignore this one. Nothing can compare to truly smooth picture in VR, so I exchanged a little bit of picture clarity (textures, pixel density) to have it as smooth as possible. With this config on the somehow populated SC in an F-14, in rain, I have stable 40FPS, and it jumps to 80 when I'm off the deck. I'm adding screenshots made in-game, and all my in-game settings on the latest pictures (remember these are stable 40-80 FPS with maximum eye-candy with some units around, with weather effects and mirrors). Hope this would help someone to find their happy settings! See you in the virtual sky! Edit2: Here are my VRAM measurements regarding changes in Pixel Density setting: https://forums.eagle.ru/showpost.php?p=4348913&postcount=28 Edit: I have added missions I made to test FPS, Rain - the heaviest (in fact not that heavy, but has some things on a deck and few moving bots to make it more alive :) ), Lite2 - good weather, lighter, Empty - lightest. All of them are my modification of F-14 carrier qual mission. Allow you to pick a Tomcat or a Hornet. Also works in Multiplayer, tested today with my friend, and had a good stable FPS on "Rain" map. FULL SETTINGS: SCREENSHOTS: Supercarrier_FPS_test.zip

Can confirm! RIO can't use radios when Pilot hosts a server. However when RIO hosts server, and Pilot joins - radios works fine. However in both cases Ground Crew don't listen to the RIO, they say "copy", "power is now on" but in fact they do nothing, and really connect power only upon Pilot request.

When RIO requests anything on the radio, nobody replies (correct mic buttons used) When RIO requests Ground Crew for power or Air Supply, ground crew reply correctly, but power / air is not connected to the aircraft. Radios (both) work only for pilot. EDIT: Radio don't work for RIO when Pilot hosts server and RIO joins EDIT2: Ground Crew never listens to RIO, they reply "copy" and "power is now on" but in fact never connect anything. Only Pilot can command to Ground Crew

It happens during first flight, if you exit the mission and restart - everything works fine

Can confirm, to reproduce just re-arm with full racks of Mk82s

Fully agree! +1

Hi Grizzlie, sure, I found appropriate arguments and names and added following to your script: Now it works with F-16 and Viggen too! By the way I flew with it online on 504 server, and it worked fine

Works excellent mate! Any chance you can add support for an F-16 and AJS-37 Viggen as well?

Wheeehaw! Will check it ASAP

In all modules, single player and multiplayer

probe light works just fine in 2.5.6, you need to turn your master light switch on (pinky switch on a throttle)