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.

I have been flying ED sim since Su-27 Flanker 1.0 demo released by SSI in 1995. Every single iteration of their product. This outcry for them trying their chance with F-35A is just insane. When first Su-27 sim was released aircraft was like a decade in service. When Jane's released their F-15E and F/A-18E, Strike Eagle was like decade in service, the Super Hornet entered service like a year prior. Now when ED releases their F-35A (likely in 2-3 years time), this aircraft will be in service for over a decade. There will be enough information to make it a cool consumer market level study simulation game out of it. If you are hating this or that module announcement for any reason, it only tells what kind of person you are. I personally keep waiting for full fidelity Su-27S, but I am still happy will receive MiG-29A. Some of you are so difficult to satisfy.

I have just found this thread. I wonder whether within a year time module developers have already implemented this optimization to their own set of liveries or they have not?

Yea, would be nice to have your AI wingman switch to F2F Datalink on request.

So what did you do wrong settings wise, so other users can find their answer?

I have just gotten to fly DCS in Quest 3... I think I know what the problem is. I think the reason is we tend to lean back on our seats (I have ACES II replica) due to seat construction, also the weight of VR headset makes us raise our chin compared to where our head would be without them. The HMD is perfectly centered on screen and this is why ED devs can't replicate this issue. HMD vertical adjustment should be a special option for every module, not only Ka-50 2 and Ka-50 III.

Switching to 500Hz in Amoury Cate for my ROG Spartha has resolved the stutters. How annoying! You only get few hours to play a week and everytime you return you must troubleshoot something after DCS update.

I am having a problem with checklist stuck after "harness" step - my pilot positively confirms it and it just doesn't progress further. No idea what is going on.

Inside Special F-4 options, increase FFB gain to at least 200% Roll. I also use 150% for pitch now. VPforce Rhino - with curved extension 15cm and TM Warthog stick on top of it. The top two FFB options are off in my profile. Stick deflection limited off Stick force blending off

Encountered similar problem on VPForce Rhino FFB stick.

Having similar problem on VPForce Rhino FFB stick.