KidCharlemagne

Oh man, I can't wait to play!

It's definitely been documented that the AI aircraft "cheat" a little bit in dogfights, so that is probably contributing! That being said, what was the fight like? Low speed, high aoa? Or a high speed rate fight? One circle or two? When you say he outmaneuvered the Hornet, how do you mean? As in, he out-turned the hornet all the way to a shooting position? Or did he just jink enough to throw off an attacking hornet?

Hello all, I'm excited to see that AI wingmen will be able to perform an actual overhead break with the new Supercarrier module. Will this behavior also apply to airfields? I'd love to be able to order my AI wingmen to "kiss off" and actually follow me to the runway. Stay well everyone!

I'm actually convinced that FlyingIron might make a DCS F-117. They're currently making an F-117 for X-Plane 11, and recently released images of their WIP A-7 for DCS. Plus, F-117 pilots were dual-qualified on A-7's as their cover story while the F-117 was still entirely classified. So it just might be the case that DCS pilots will be able to do the same...

As cool (and strange) as it would've been for the Hornet to carry AIM-54's, that missile was exclusive to the Tomcat. The upcoming AMRAAM changes should help out us Hornet fans though!

I'm thrilled that this is being worked on! I've always thought that the flight deck and various modern missions are incomplete without the Super Hornet and Growler. I can't wait for some realistic modern buddy tanking too!

I've heard the new carrier comms while approaching the Tarawa, so I'm hopeful that the new ATC will be applied to other ships.

With a Ryzen 5 2600 and a GTX 1080, I went from 16GB to 32GB and noticed some improvement in loading times and performance on multiplayer servers. However, I rarely see my memory usage rise above 12GB in normal usage, even with my preload radius at maximum. I saw much more significant improvement after replacing my 2600 with a 3600X and my old PNY SSD with a Samsung 970 EVO. So go for the new memory if you want since it definitely won't hurt, but it might also be worth seeing what your usual memory usage is in normal play.

Thank you all for your suggestions and help! In the end I replaced my PNY SSD with a Samsung 970 Evo and the stutters have disappeared!

Oh man, that's a really useful site! Thanks for sharing!

Thanks for all these suggestions. The first thing I always try is deleting the FXO/Metashader folders, so I'll edit my first post to add that in. This afternoon I tried pulling out my ethernet cable, no luck there. I also tried renaming my saved games folder and allowing it to create a new one, but no luck either. Something I noticed, however- the stutters were only present when disk active time was increased. There were considerable pauses with spikes up to about 50% active time on the C: drive, but the sim was smooth and stutter-free anytime the disk active time was low. Looking at Resource Monitor, the file with the most activity was AppData\Local\Temp\DCS.openbeta\~tr00007E2A.bin. Does anyone know what this file does, or if it may be causing stutter?

Hello all, I'm out of ideas and could use some help. I've been playing DCS for about 3 years now, and have been struggling with stutters that whole time. These micro-pauses are much more pronounced in VR, and really take away from an otherwise incredible simulator. I've read just about every thread I can find with the word "stutter" or "lag" in it, and haven't been able to figure out my problems yet. Some background: System: Ryzen 5 3600X GTX 1080 8GB 32GB DDR4 @ 2666 MHz DCS on 1TB SSD, OS on 480GB SSD Oculus Rift S Settings: Textures HIGH Terrain Textures LOW Civ. Traffic OFF Water MEDIUM Visib. Range MEDIUM Heat Blur OFF Shadows OFF Res. of Cockpit Displays 1024 MSAA OFF Depth of Field OFF Lens Effects DIRT HDR OFF Clutter/Grass 0 Trees Visibility 75% Preload Radius 150000 Chimney Smoke Density 0 Gamma 2.2 Anisotropic Filtering 4x Terrain Object Shadows OFF Global Cockpit Illumination OFF Vsync OFF Full Screen ON Scale GUI PERSONAL PREFERENCE (Recommended: OFF) PD 1.2 Things I have tried: -Disabling Windows 10 Game Mode -Uninstalling NVidia drivers with DDU, then reinstalling -Disabling hotplug in autoexec.cfg -Disabling Network adapter (seemed to work briefly, but couldn't reproduce) -Turning off real-time protection in Windows Defender -Starting DCS with no USB devices plugged in -Closing as many extraneous services/programs as possible -Uninstalling GeForce Experience -New GPU (previously RX480) -New CPU (previously Ryzen 5 2600) -New VR headset (previously Lenovo Explorer) -Disabling VR and flying on 2D monitor (~110 FPS, stutters still very noticable) -Reinstalling Oculus software on different drive -30GB paging file -No paging file -Paging file on same drive as DCS -Making sure I don't have MalwareBytes installed (I don't) -PD's from .8 to 1.5 -PD at 1.0 in DCS, 1.1 to 1.4 in Oculus Tray Tool -Deleted FXO/Metashaders I know there's more I've tried, I'll edit this post if I think of anything else. I've also attached my Log file here if it helps. Anyone have more ideas? dcs.txt

We thrust you.

Any ideas on how to solve a "GetHeading" error? I'm trying to build a campaign from scratch and keep receiving this error in the UTIL_Functions.lua:71:, "attempt to perform arithmetic to field 'x' (a nil value)".

Sounds like you have the procedure correct. Slew the TGP toward where you think the laser should be and uncage the TGP. You'll know it's searching because the TGP screen will freeze but a white dot will be circling the indicator, showing the azimuth on which the TGP is searching for the laser. Once it finds it, you'll see the TGP screen update with the designated target in view.

I'm looking forward to this! I'll probably finish up some of my campaigns if I don't have to do all the loadouts by hand!

Thank you all for these findings! I disabled my network adapter and was able to fly the first (largely) stutter free flight in two years! I had previously tried creating an autoexec.cfg file and adding the "no_device_hotplug = true" line, but it didn't stop the stuttering. I'm running 2.5.5.38140. For now I'll just shut off my network adapter until I can figure out a more permanent fix. It's progress though!

It was my understanding that the lights will be activated when the external model is finalized, which I assume is coming soon.

This is actually the first time I've ever heard about that product. Thanks for sharing!

It has always been my impression that pilots will be proficient in all aspects of their aircraft's capabilities, but they or their unit may be tasked with a specialization. For instance, the 148th Fighter Wing in Duluth, MN specializes in SEAD tasks, and even has some HAVE GLASS aircraft with reduced RCS for the purpose.

I also have a Rift S and I've been having trouble reading the MFD's. Interestingly the HUD is perfectly readable to me.

Really? I'm thrilled to hear that, I thought it was a problem with my engine management!

As a Colorado native, I'd definitely second this one. I though the 120th was actually equipped with big mouth Block 30's, but I'd still love to see this in game. Are they upgrading? Edit: Looked it up, I see the VT ANG had Block 30's as well.

Oh man, I loved the first mission and can't wait to play these! As soon as I finish my Harrier throttle, these will be the first missions I fly!

You could always try changing the "startup_time_player" in the camp_init.lua file. As a default it's set to 1200 seconds, giving 20 minutes before the mission really gets going. I have mine set to 420 seconds (7 minutes), which seems to result in a properly timed mission. KC