peanuts0441

Make sure the radio mode selector is set to Transmit/Recieve (REM) You can confirm this by making sure the white light next to it is lit And also make sure you have channel B selected on the radio panel, in this picture channel D has been selected

I meant DCS's in game multi threading option - keep that turned off Keep Hyper-Threading on in BIOS, it will help with performance in other applications Did you do those tests on the multi threaded version of the game or the ST version?

Seems like a DCS bug If you have multithreading turned on, turn it off and then try I remember reading a post that had the same issue and they fixed it by turning off multi threading

Record a video of yourself designating a target Also the in flight alignment wont do anything if your INS is already aligned

Ok I didn't see that part But even without any active launch, an aircraft that has a lock on you is still more dangerous than an aircraft that isn't locked on to you The aircraft that is locked on to you can fire a missile at any point with high accuracy, while an aircraft that isnt locked either has to use a firing solution which doesn't require a lock (which has a lesser chance of being successful), or it has to first get a lock and then fire (more time required) It's also done for better situational awareness

Yea it is normal, the radar that is actively guiding a missile towards your aircraft is the most dangerous threat, an aircraft that isn't doing anything (whether it is closer) is not a threat Once the closer aircraft starts tracking you, it will show up around the center of the RWR display as well Also 50mi is well within range of some missiles, so it makes sense that even that far out an aircraft tracking you is considered a threat, AIM-120D for example can definitely be fired from that sort of range & the AIM-7 can also achieve that range under specific conditions and most surface to air missiles have that range too Also without making it too complicated, the F22's RWR (AN/ALR-94) uses this exact method to determine range to a target, but it requires way more data than just emission power The F22's RWR alone can provide enough information for a Single Target Track

The F18 also uses its Radar in IFA mode for velocity updates if GPS is not available

Use a tool like MSI afterburner + RivaTuner Statistics server to monitor your GPU and CPU usage in game, whichever component is the bottleneck, upgrade that For VR, GPU matters most of the time, and GPU VRAM But if you upgrade to a 4080 the i5-11600K will become a bottleneck If you upgrade your CPU your current GPU will hinder the CPU and the performance gain wont be that much in DCS Honestly speaking you'd have to upgrade both to see a reasonable difference Also DCS has no GPU preference, just get the one with better specs

The simplest way to think about it is like so: Frametime is the amount of time 1 frame is shown on screen, so as an example, if you're playing at 60 frames per second, a new frame would show up every 16.5 milliseconds, thus giving a smooth 60FPS, but this is not always the case in a real scenario, due to other things, the frametime constantly goes up and down, one frame could be as short as 13 milliseconds while another lasts 40+ milliseconds, this would cause a noticeable "stutter" as its called, generally you want CONSISTENT frametime, not one that is constantly going up and down A frametime that stays at a fixed number (e.g 16ms) is better than a frametime that is lower but jumps up periodically (e.g 14ms but spikes to 30-40ms every so often) 1% and 0.1% lows are a value that measure frametime (or stutter) in a more accurate manner. To make it easy to understand: The higher the 1% and 0.1% lows, the better 1% low measures the average of the slowest 1% of frames, so say your playing at 60FPS but periodically drops to 30-35 for a few hundred milliseconds, it will measure this drop and average it out, in this example; the 1% low would be 33 0.1% low does the same thing but for 0.1% of the slowest frames, so it measures an even bigger drop, lets just say periodically for a few milliseconds you drop to 25-29FPS, it will average these drops and report the 0.1% low to be 27

Its meant to be released at 30 degrees For higher angles you have to do it from a further distance (6-7NM instead of 4-5), you were too close to the target

Go to task manager > Details tab and set DCS's affinity to not use Core 0 (or whichever core is the bottleneck) See if it helps Example:

You know whats funny? I totally noticed that too in the video you posted earlier showing task manager, but I disregarded it because you also said in that post "Nothing seems out of the ordinary" so I thought it may have been normal with your drive Initially, even my eyes went straight to the response time of that drive when I saw the video Lol could've saved so much trouble if I just atleast told you about it

Why are you asking a bot? Just google it Pagefile can be set to anything Just make sure you have the storage space on that drive for it And also create the pagefile on an SSD, since they are faster than Hard drives, you will see an improvement if you have the pagefile on an SSD, but it will reduce the lifespan of the SSD because of more write cycles

Yea it is possible if you had an old mod that wasnt updated, some incompatibilty arises with newer versions of the game (For my own knowledge), once you figure out the cause, can u post it here pls

Could be, could also just be a problem within DCS and how it accesses memory, but as glide said, get memtest86 Some motherboards have a built in memory test that you can access within the BIOS, run that too if you can find it Also just know that turning off XMP will affect your system's responsiveness in other applications, so turn it back on once you've stopped playing dcs, and then turn it off again once you want to play dcs