Shaman

Try this, backup your entire Saved Games folder somewhere - and then remove it. Allow DCS to rebuild it from scratch. Launch DCS and confirm you still have the same issue. This was a huge update; took me over 300GB to update. Yes, after update I got MiG-29A Fulcrum new module installed. No issues with F/A-18C like yours spotted so far. (Edit: Tested for you both Nevada and Caucasus too)

I have checked for you what you are reporting and all is good here. No mods, clean update. I am sure Repair will sort this out. After that, install only one mod at a time and test thoughtfully. Mods which are sitting in Saved Games can also conflict with overall structure of units, controls, functionality of different modules, and therefore are not supported. Edit: Sorry! Repair will not remove mods from Saved Games subfolders, you got to clean that yourself.

You should have uninstalled all the mods prior updating. Now just try to run DCS Repair tool checking option to delete all unused files. Do not install any mods and start DCS and check again.

Thanks for sharing!

Is there a solution to this?

Hey, could you send a picture of your Optiscaler configuration? I had to enable also Non-Linear sRGB Input to make i.e. Hornet's MFDs clearer to read. Running Optiscaler DLSS ( FSR 3.X w/Dx12 ) in DCS's DLSS Balanced setting.

Hi guys, I have used OptiScaler v0.7.8 as a workaround meanwhile on latest AMD drivers, now running DCS on forced FSR4 through this app, and this gives me proper anti-aliasing, and no issues with HUD jagging and disappearing pixels and also sharp MFDs. I have just switched from NVIDIA to AMD card and noticed that too, so annyoing. My current driver is 25.8.1 -> bug reported to AMD.

That could be also a Special setting to change its default state.

Nav lights and anti-col light are still very weak in daylight, is it a DCS engine issue? You'd expect you can spot these at long ranges.

It would be great if there was a highlight like during training missions what you are expected to check switch next, when Jester calls it.

I can't get rudder deadzone to work on my end. Could it be related? No matter the value of rudder axis deadzone I apply, I don't get any, there is nil change while in cockpit with controls overlay view.

bump, bug is still present in Feb 2025... I just turned it off completely.

It is definitely a bug. Even if you want to take control at last mile, you basically run out of trim range... there's no way to pull up after ACLS is disabled at last mile and you wish to save the airplane.

I have to admit that since Sep 2024 when I got FBB (VPForce base) I am having issues with autopilot altitude hold (not every time though) and ACLS too (pretty much all the time, despite being very careful with glideslope capture and in perfect trim).

Since this thread has been ressurected. I have tried it with FFB stick (VPForce). It is not working well if FFB Trim Actuator special function is set to on. Even if FFB Trim Actuator special function is set to off, ACLS is all over the place with ATC on. Tested it again and again being perfectly trimmed on glidepath and according to procedures. It might be FFB implentation that throws its logic off. Something for Heatblur to test. I think it ACLS is quite useless with proper FFB gear and will just get you killed.