Czar

Any chance of using AN/APG-70 Radar: ON and AN/APG-70 Radar: STBY functions be useful? I've been using both to swtich radar on and to standby (it won't emit radiation) inflight when needed since EA release without issues, including latest patch.

As razo+r pointed out, crosswind and asymmetric loadout will give the need for aileron trim. Very strange for you to feel the need to trim rudder on such a plane. I don't own the 16, though. Additional tips: -Check your controls output with RCtrl+Enter. -Check your curve settings. -Disable Game Flight Mode at Options>Gameplay. -Check if the F-16 controls are getting inputs from another controller that's plugged in or bluetooth paired like a gamepad.

Yeah, my bad... The test before the last he turned off but kept 0.5 sharpness. Also there is some form of checkerboard pattern looking down at the water. Perhaps some other form of sharpness is being applied. To add: -Disable reshade if you're using it. Sometimes it has sharpening filters that can mess with the clouds and shaders. -Reset control panel settings to default. -Delete the folders: FXO and Metashaders2 from your DCS saved games directory at 'Root OS storage:\Users\>user<\Saved Games\DCS.openbeta'. If you're using stable, it is just 'DCS' instead of 'DCS.openbeta'. -Set gamma no more than 2.2.

Please, ONLY use sharpening if you're using DLAA or an upscaling method (FSR. DLSS etc...) Set sharpening to 0 and try again. Edit Sharpening does not always equal better visibility of objects, but can introduce unwanted noise. At dusk and dawn, the distant clouds do have a poor appearance as of now, regardless. It is an ongoing improvement, I would guess. See if the other problems at daylight has been solved.

It was exactly his point. ....because the dedicated community uses OB and report the issues much more frequently than if they used Stable. DCS has ran better on OB than Stable due to module fixes and performance fixes for years. 2.9 issues are temporary.

Any chance OP have Hardware Accelerated GPU Scheduling ON? Turn that OFF > Restart PC > See if it helps

Isn't the point of these sims to play as the human element? Lots of proper procedures to avoid shooting down a friendly. The Hornet has: Working IFF (SA page+HUD+Radar screen), TPOD visual ID (if you're carrying them), Mk1 eyeballs (every pilot has at least 1, I think), communication (two radios). If it is about quake like A-A servers, an automation to not shoot on IFF positive replied contacts will give you no benefit on overall learning and experience of the simulator. Lower level tech will give you a larger play area. This is why 3rd gen and early 4th gen are so appealing gameplay/simplay/tacticalplay wise.

It is not up to ED. These temporal methods affects all games and will continue to do so unless a new version of them are produced with compensating algorithms to avoid ghosting. It is like having a very slow shutter speed on a camera for the film to absorb more light but at the same time wanting a fast shutter speed to remove motion blur. The gains comes from exactly what produces the ghosting. I found DLAA the best at avoid most ghosting and still have a performance uplift without aliasing/shimmering. All other methods I discarded because of the massive visual disadvantage it leaves you compared with no anti aliasing or 2x/4x MSAA.

Manage your expectations with DLSS, TAA and FSR. DCS is really played down to pixels and those Temporal methods really are unfitting for this sim if you're running 1440p or bellow. It can make impossible to visually ID a plane far away where before you could. Lots of ghosting especially screens with dark backgrounds. These new features can be useful to run 4k, perhaps but they are really unfit for DCS at the version they stand today. But it still is amazing to have.

This is how computer generated graphics behave on high FOV values. There is no physical lens to distort images as you see on fisheye lenses. There are post processing mechanisms that mimics physical fisheye lenses for wider FOVs but that distorts pixels on the center of the images causing blurriness unless you're downscaling. I think there is one shader on reshade that does that. Other games also feature something similar but it degrades image quality in the center. This is a post "fix" on photoshop using lens distortion.

Disable any background application including those managing RGB lighting profiles. Some RGB apps are making DCS crash.

Looks like storage hardware bottleneck. As above comment suggested, set pagefile above 30gb on a SSD (if it is a NVME is better). While playing, even on heavy missions, your disk usage should be very low. Furthermore you'll need to install DCS on a SSD and it will be fine if its not a NVME. If you're already have DCS on a SSD, it is a page file size issue. 16gb system Ram is enough, but you need that page file above 30gb on a fast storage. HDD won't be enough.

I had once interrogated a friendly F-15C with the M-2000C in TWS, reply successful and friendly confirmed. I knew there was a MiG-29 in the area and it did popped up on the radar while I had the 15C still tracked. The MiG came right between me and the friendly, and instead of letting go the friendly 15 I mistakenly pressed IFF again to interrogate and turned out my aircraft did NOT receive the reply from the friendly. If I haven't interrogated the 15 before the 29 came into between us, I would assume there was two hostile aircraft in front. I think there is a bit more on that front. It is not super sophisticated but....

Was this on the ground with no airflow? If it was, it is an effect from CAS. When flying all control inputs are instantaneous. Look on the input graph with Ctrl+Enter to troubleshoot input parameters. CAS and other similar systems moving control surfaces on ground tend do mislead what the airplane can do in the air.

Also the looping sounds on cockpit as the Idle engine sounds or some startup sound keeps looping when on the ground at idle power.

Yeah, I never sat in a Strike Eagle. So I must accept the too high volume level from ECS because the first module iteration that comes in EARLY ACCESS should be deemed as exactly as it is in real life and missed values doesn't happen at all as the developers are pure gods... Some of us are just trying to point out things in order to iron out possible bugs. Over and over again folks points at "IRL the ECS sounds overwhelm every other sound" and "people got used to unrealistic sounds from other modules and they can't handle the real values". It is NOT the ECS mix against other sounds, is the DB levels of ECS that's way too loud on a headset. Same volume levels for all modules, no issue on hearing comfort. ECS is just too loud. Not as in: "I can't hear the aircraft like in a hollywood movie". It is: The output of ECS is too loud. <<<< I've never seen such defense on a brand new Early Access title. The module is pretty cool but is full of bugs as in the next OB patchnotes by Razbam points out. Great work on the dev side but gaslighting people trying to help make it better on the forum is bizarre.

Right inlet ramp seems to be off in comparison to the left inlet ramp. Any flight regime, on mission editor, wherever the model is viewed in sim. As well on promotional material.

Hands on Stick and Throttle at all times. The trim speed is fine.

The aircraft will often ask to re enter coordinates when it goes PP REQ on the HUD if you failed stored heading.