rfxcasey

I wasn't attempting to be deceptive honestly.

I got tired of having to set up my weapons and radar profiles every time I hopped in a new Hornet, so I came up with a solution, cockpit automation that simulates data cartridge functionality. PLEASE NOTE, the 'AppData' folder is a hidden system file, you must have 'view>show>hidden items' enabled in Windows File Explorer to see it. Hornet Automation.7z

Maturity? I think you need to check yourself brother, what's with the hostility, it's not becoming of you. Known you for a long time Tom, expect better than this.

Doesn't bother me at all, people like different stuff, nothing to get offended or upset about.

DCS is more of a hobby than a game. As a long time flight sim enthusiast, it was for decades a dream to have simulators that not only simulate well, but also look great. Graphics used to take a back seat to the actual simulation, it was kind of a given. Today, after decades of both software and hardware development, we seem to be in a golden age of simming, with access to stuff we've desired for years and years, the level of immersion obtainable is insane. Now me, I'm never going to be able to fly a real jet or helicopter, especially military, but I've grown up seeing and wondering at the engineering and operation of aircraft going back to the 70's. I've also been a bit of a WW2 buff and have watch countless documentaries on aircraft development through the ages, something about this stuff has captivated and fascinated me my whole life. When I was younger, aviation was a bit of an enigma to me, and over the years, I've learned more and more about it to the point where I can hold my own pretty well in a hardcore sim like DCS World and several others. That gives me a great sense of accomplishment and satisfaction, while also providing for hours upon hours of entertainment, wonder and comradery with community members. Sims like DCS World are a bit of a commitment, but flight simming was something I was semi-committed to anyways, so having such high fidelity, to really learn and get a sense of what it takes to cold start an F-14 Tomcat, taxi and launch it off the carrier, successfully perform my mission and then bring it on home and execute a perfect landing back on the carrier while chatting and laughing it up with friends, well, it's what I call fun. Having a sim pit helps, and like music theory, you can take that as far as your imagination (and wallet) warrants. You can get away with a decent desktop setup however but it really helps having experience people to help you with ideas and walk you through the process of getting things set up the best for you. A head tracker is a must. Against the advice of many, I wouldn't suggest starting out in VR it will just complicate things and possibly add another level of frustration. A good HOTAS is pretty critical, I wouldn't recommend anything less than at least a CH Fighterstick, X52 Throttle or similar and some decent rudder pedals like a set of Logitechs. If it something you're going to stick with, go ahead and get a Winwing, Warthog or Virpil setup, you won't regret it. The Gladiator stuff is good too. While a full motion simulator is more of the end game for many people, you can get a sim shaker setup like a Buttkicker or make your own, with the right software it will give you tactile vibration feedback like feeling the bumps when rolling down the runway, turbulence and aircraft shutter when you're getting too far outside of the planes flight envelope. Hardcore sims aren't for everyone, with what we have today, you can get as hardcore as you'd like but you can still take a more casual/practical approach, especially when you're getting started, and then grow into a full blown hardcore sim freak from there.

Can confirm, I've seen this on the carrier deck on night missions. The light shining from the tower is illuminating what looks like giant snowflakes. Very strange.

Who said anything about not listing bugs, all I said was, it should be low on the priority list, i.e. at the back of the line behind all the other bugs.

With so many bigger fish to fry, even if this turns out to be an actual issue it should be way down on the priority list.

Hmmm, perhaps it was a bug and they've patched it then. Haven't flown the Hornet since the update, it's been all Apache.

This is what macros and voice commands are for.

What does "better" mean to any given person? Why do any of us care what you fly? Why would you automatically assume that 18 pilots think it is "better" than anything else just because they personally enjoy it? Just be happy we have both. If you need to ask, then just don't fly it. There problem solved. That wasn't too hard was it? I like them all, I used to fly the other 16 sim as well. I own and know the DCS A-10, Ka-50, F/A-18, F-16, F-14, A4-E, UH-60L, Hercules, P-51, F-15 and now learning the AH-64D Apache. No one is better than any other in my opinion, I thoroughly enjoy them all.

Seriously? What kind of a post is this, the F/A-18 gets trashed and trolled enough. I don't believe you're really sincerely curious. People like what they like and fly what they fly for their own reasons, it's really none of your business, not sure why it would concern you as long as everyone is having fun. The childishness in these types of this airframe vs. that airframe discussions just get old, tiresome and annoying after a while. Anyone can buy and learn every module, perhaps you'd be happier if everyone just flew the same thing? Perhaps it makes some feel better to bash on others for getting enjoyment out of flying anything other then the "best" plane in the game, and yes, it is a game at the end of the day. And the "We can avoid carrier talk as thats an obvious one but besides carrier ops - why do any of you pick the 18 over something else?", would it bother you if carrier ops was the only reason someone enjoyed the module? Is that irrelevant? Seems you just wanted to poke people. No one owes you an explanation for why they enjoy what they enjoy.

Was doing some testing recently. Haven't tried it with the latest patch but, in a sustained turn, setting the flaps from auto to half actually made the jet less draggy. Where I was bleeding off speed like at a given G set to auto, putting the flaps to half not only prevented the speed loss, in some cases I was actually able to gain speed at a given throttle setting. I'm wondering if the flight computer is too aggressive with the flaps set to auto or perhaps it's just a bug. Try it yourself and see, I haven't done any extensive testing for much observation of the external model to see if I can tell a difference in flap angle. Just something to look in to.

Yes, I think so, seems to run smoother with virtually no hiccups. Still testing though.

Screaming at the wind but why have a TOO mode in the first place then if targets are always pre planned. And since sensitive info is classified, what does it matter how DCS chooses to model the Hornet systems, who is to know if it's wrong or if it's right besides those sworn to secrecy. If DCS took stabs in the dark at it, or best assumptions, and got it close to right, that means the government comes along and says, no that's too accurate even though you don't actually know whether it is or isn't so change it. That just tells us it was probably right in the first place. Not sure why something like TOO 2 would be classified but whatever. I mean, program target, drop bomb, bomb goes to target, that's just common sense.

Someone else from a Windows 10 forum figured it out. https://www.tenforums.com/general-support/192180-appdata-folder-wrong-drive.html#post2397233

Microsoft Windows [Version 10.0.19044.1586] (c) Microsoft Corporation. All rights reserved. C:\Users\rfxcasey>cmd /E /C "prompt $T$$ & echo.%TIME%$ & dir /AL /S C:\ | find "SYMLINK" & for %Z in (.) do rem/ " 20:11:16.07$ 11/13/2021 01:54 PM <SYMLINK> api-ms-win-core-console-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-core-console-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-core-console-l1-2-0.dll [..\..\avg.local_vc142.crt\api-ms-win-core-console-l1-2-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-core-datetime-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-core-datetime-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-core-debug-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-core-debug-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-core-errorhandling-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-core-errorhandling-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-core-file-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-core-file-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-core-file-l1-2-0.dll [..\..\avg.local_vc142.crt\api-ms-win-core-file-l1-2-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-core-file-l2-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-core-file-l2-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-core-handle-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-core-handle-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-core-heap-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-core-heap-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-core-interlocked-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-core-interlocked-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-core-libraryloader-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-core-libraryloader-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-core-localization-l1-2-0.dll [..\..\avg.local_vc142.crt\api-ms-win-core-localization-l1-2-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-core-memory-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-core-memory-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-core-namedpipe-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-core-namedpipe-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-core-processenvironment-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-core-processenvironment-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-core-processthreads-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-core-processthreads-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-core-processthreads-l1-1-1.dll [..\..\avg.local_vc142.crt\api-ms-win-core-processthreads-l1-1-1.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-core-profile-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-core-profile-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-core-rtlsupport-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-core-rtlsupport-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-core-string-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-core-string-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-core-synch-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-core-synch-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-core-synch-l1-2-0.dll [..\..\avg.local_vc142.crt\api-ms-win-core-synch-l1-2-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-core-sysinfo-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-core-sysinfo-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-core-timezone-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-core-timezone-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-core-util-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-core-util-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-crt-conio-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-crt-conio-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-crt-convert-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-crt-convert-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-crt-environment-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-crt-environment-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-crt-filesystem-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-crt-filesystem-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-crt-heap-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-crt-heap-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-crt-locale-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-crt-locale-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-crt-math-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-crt-math-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-crt-multibyte-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-crt-multibyte-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-crt-private-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-crt-private-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-crt-process-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-crt-process-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-crt-runtime-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-crt-runtime-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-crt-stdio-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-crt-stdio-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-crt-string-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-crt-string-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-crt-time-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-crt-time-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> api-ms-win-crt-utility-l1-1-0.dll [..\..\avg.local_vc142.crt\api-ms-win-crt-utility-l1-1-0.dll] 11/13/2021 01:54 PM <SYMLINK> concrt140.dll [..\..\avg.local_vc142.crt\concrt140.dll] 11/13/2021 01:54 PM <SYMLINK> msvcp140.dll [..\..\avg.local_vc142.crt\msvcp140.dll] 11/13/2021 01:54 PM <SYMLINK> msvcp140_1.dll [..\..\avg.local_vc142.crt\msvcp140_1.dll] 11/13/2021 01:54 PM <SYMLINK> msvcp140_2.dll [..\..\avg.local_vc142.crt\msvcp140_2.dll] 11/13/2021 01:54 PM <SYMLINK> msvcp140_atomic_wait.dll [..\..\avg.local_vc142.crt\msvcp140_atomic_wait.dll] 11/13/2021 01:54 PM <SYMLINK> msvcp140_codecvt_ids.dll [..\..\avg.local_vc142.crt\msvcp140_codecvt_ids.dll] 11/13/2021 01:54 PM <SYMLINK> ucrtbase.dll [..\..\avg.local_vc142.crt\ucrtbase.dll] 11/13/2021 01:54 PM <SYMLINK> vccorlib140.dll [..\..\avg.local_vc142.crt\vccorlib140.dll] 11/13/2021 01:54 PM <SYMLINK> vcruntime140.dll [..\..\avg.local_vc142.crt\vcruntime140.dll] 11/13/2021 01:54 PM <SYMLINK> vcruntime140_1.dll [..\..\avg.local_vc142.crt\vcruntime140_1.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-core-console-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-core-console-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-core-console-l1-2-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-core-console-l1-2-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-core-datetime-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-core-datetime-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-core-debug-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-core-debug-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-core-errorhandling-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-core-errorhandling-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-core-file-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-core-file-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-core-file-l1-2-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-core-file-l1-2-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-core-file-l2-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-core-file-l2-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-core-handle-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-core-handle-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-core-heap-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-core-heap-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-core-interlocked-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-core-interlocked-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-core-libraryloader-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-core-libraryloader-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-core-localization-l1-2-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-core-localization-l1-2-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-core-memory-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-core-memory-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-core-namedpipe-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-core-namedpipe-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-core-processenvironment-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-core-processenvironment-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-core-processthreads-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-core-processthreads-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-core-processthreads-l1-1-1.dll [..\..\..\avg.local_vc142.crt\api-ms-win-core-processthreads-l1-1-1.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-core-profile-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-core-profile-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-core-rtlsupport-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-core-rtlsupport-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-core-string-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-core-string-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-core-synch-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-core-synch-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-core-synch-l1-2-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-core-synch-l1-2-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-core-sysinfo-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-core-sysinfo-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-core-timezone-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-core-timezone-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-core-util-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-core-util-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-crt-conio-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-crt-conio-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-crt-convert-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-crt-convert-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-crt-environment-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-crt-environment-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-crt-filesystem-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-crt-filesystem-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-crt-heap-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-crt-heap-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-crt-locale-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-crt-locale-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-crt-math-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-crt-math-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-crt-multibyte-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-crt-multibyte-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-crt-private-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-crt-private-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-crt-process-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-crt-process-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-crt-runtime-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-crt-runtime-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-crt-stdio-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-crt-stdio-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-crt-string-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-crt-string-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-crt-time-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-crt-time-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> api-ms-win-crt-utility-l1-1-0.dll [..\..\..\avg.local_vc142.crt\api-ms-win-crt-utility-l1-1-0.dll] 03/11/2022 03:30 PM <SYMLINK> concrt140.dll [..\..\..\avg.local_vc142.crt\concrt140.dll] 03/11/2022 03:30 PM <SYMLINK> msvcp140.dll [..\..\..\avg.local_vc142.crt\msvcp140.dll] 03/11/2022 03:30 PM <SYMLINK> msvcp140_1.dll [..\..\..\avg.local_vc142.crt\msvcp140_1.dll] 03/11/2022 03:30 PM <SYMLINK> msvcp140_2.dll [..\..\..\avg.local_vc142.crt\msvcp140_2.dll] 03/11/2022 03:30 PM <SYMLINK> msvcp140_atomic_wait.dll [..\..\..\avg.local_vc142.crt\msvcp140_atomic_wait.dll] 03/11/2022 03:30 PM <SYMLINK> msvcp140_codecvt_ids.dll [..\..\..\avg.local_vc142.crt\msvcp140_codecvt_ids.dll] 03/11/2022 03:30 PM <SYMLINK> ucrtbase.dll [..\..\..\avg.local_vc142.crt\ucrtbase.dll] 03/11/2022 03:30 PM <SYMLINK> vccorlib140.dll [..\..\..\avg.local_vc142.crt\vccorlib140.dll] 03/11/2022 03:30 PM <SYMLINK> vcruntime140.dll [..\..\..\avg.local_vc142.crt\vcruntime140.dll] 03/11/2022 03:30 PM <SYMLINK> vcruntime140_1.dll [..\..\..\avg.local_vc142.crt\vcruntime140_1.dll] 03/11/2022 11:29 AM <SYMLINKD> nvspcaps [C:\Program Files\\NVIDIA Corporation\ShadowPlay\nvspcaps] 04/13/2017 07:04 AM <SYMLINKD> avast! Antivirus [C:\Program Files\Common Files\AV\avast! Antivirus] 12/07/2019 04:30 AM <SYMLINKD> All Users [C:\ProgramData] 07/15/2017 09:41 AM <SYMLINKD> ScummVM [C:\Users\rfxcasey\AppData\Roaming\ScummVM\Saved games] 20:13:09.29$ rem/ C:\Users\rfxcasey>

Well see, this is weird, because I also have a C:\Users\username\AppData\Local\DCS in addition to D:\AppData\Local\Temp\DCS. The C:\Users\username\AppData\Local\DCS is empty. Would I be better off just doing a complete reinstall of DCS, though, it's probably going to be a real hassle, I'll need to know what to backup so I don't lose all my controller settings. Still, why D:\AppData\Local\Temp\ exists and why it's being used is something I need to figure out.

I have DCS installed on my fast M.2 Drive F:, but I noticed through Windows resource manager that DCS is accessing my slow mechanical D drive. It seems to be accessing D:\AppData\Local\Temp\DCS. How can I move that folder to my fast drive F:? I was getting a lot of stuttering and I noticed these drive accesses. If I alt + tab out of DCS the D drive activity stops. When I alt + tab back into DCS it starts accessing the D drive location again even though DCS is installed on my F M.2 drive. I think it's causing performance slowdown.

Why do I need the manual when I've got you?

Well I'll be dipped, it'd be nice if that was made a bit more apparent. It works, but it still sounds like they are talking on comms so, kind of a miss if realism was what they were going for.

In all other planes you don't have to have the canopy open and only have to have the engine off to repair. If you need to have the canopy open to talk to the ground crew in the A-4e that's a special case as far as I know, none of the other planes I own require that. I can't get the any of the radio comms to work in the A-4E after installed to latest version 2.0, I don't know what the problem is. I've tired in the quick missions as well as adding the plane to missions I've made myself and normally fly. What the heck is going on is the plane just bugged or what. My pilot will make the radio call but never any response from ground crew or ATC. I can't salute and launch off the carrier but that's it. Even when the plane is completely shut down it's not working. Worked fine in the old version. I complete uninstalled and reinstalled it but it's still not working.

Can't re-arm re-fuel no matter what I do, what is the problem?

Is it normal for the SOI diamond on the FLIR display to be practically invisible? No matter how I set the contrast and brightness of the DDI it is basically impossible to see the diamond in the upper right corner when the FLIR is SOI.

I did, doesn't make what I said any less relevant.