LeCuvier

I suspect there is a syntax error in these 2 lines: LEFT_MFCD - RIGHT_MFCD - I think there should be a "=" instead of the "-"

I support the option. If I decide to use a SP mission someone else created, it becomes my mission and I modify it to suit my needs. And if that breaks some smart gadget that's my problem and not the problem of the mission designer. One should not forget that mssion designers are not perfect; and they may create some functionality that doesn't work for everybody, and then I want to be able to adjust it. No dictate please! In MP missions you can dictate, and that's one reason why I do not fly in MP.

I agree it's disappointing at this point in time, and for the time being my F-15E is unemployed. I still hope they will correct this mess, and then I will start playing. As long as they haven't done it, I won't consider buying any further Razbam module.

I will stick with manual laser activation. With auto-lase I've had quite a few misses, and I'm not going to try and find out why. Manual lase works all the time for me.

That's what I'm doing now. I activate the laser just after releasing the bomb. This way the bomb always manages to acquire its target. When I used auto-lase, I tended to set the lase time to something like 10s. But when I'm at 16,000 ft, the fall time is about 30s and the laser is is only activated after about 20 s. I suspect that the bomb then struggles to "find" the laser "dot" because it often misses target. With manual laser activation I never miss a target.

The Bf-109 Kurfürst has significantly better dogfight performance compared with the FW-190 Dora. The only AI warbird I cannot defeat with the Kurfürst is the Spit.

I see the HUD speed indication disappearing almost regularly in a scenario where I take cover on the ground to evade an impending fighter attack. When the threat is gone and I take off and fly back to the battle scene, it takes quite a while before I see the speed indication in the HUD. In that phase I don't do any wild manoeuvering.

I respect your opinion but I hope it does not prevail. With that mindset you would probably also vote to remove the auto-start macros from all modules

I agree!

You guys make me wonder if I miss something when I use the MAV with the A-10C. I have never done anything like this and the target transfer from TGP to MAV always works fine. If that's unrealistic I hope it stays that way.

I would support the request to get rid of he default assignments altogether, except where a game controller is a replica of a simulted aircraft's HOTAS. I have spent lots of time clearing out these default bindings which are mostly nonsense.

I'm investigating. DCS version Open Beta MT I use the default profile which is "GBU-12", which I update for Auto-Lase and Lase Time. Where do you get the "M/GBU-12"? I do not select the weapon station. Edit: I disabled all mods and created a test mission, and the auto-lase worked all the time. So the issue is either in my process or my mods. The ball is in my court. Thanks guys!

I have come back to the A-10C II after some time, and in one of my missions I use the GBU-12. In the profile I have set Auto-Lase to ON, and the Lase Time to 8 s (I also tried with 10s). When I release the bomb, the Laser is not activated. I have to manually activate the laser with the NWS button on the stick. I drop this bomb usually from about 12000 ft. While I can adjust to this situation, it doesn't feel right. So my question: Is this a bug, or am I missing a step in the process?

I found that the "Options" file which is included in the .miz file contains a snapshot of the "Options.lua" settings at the time when you last saved the mission. Example: I found that my copy of the "Takeoff.miz" for the Anton had the parameter "assistance" (which is Takeoff Assistance) set to 100%. As I have experienced several cases where some of my options settings (especially the takeoff assistance) were changed after an update, a lot of my missions could contain unwanted option values. Now there is an option under Options/Gameplay in the bottom right of the page, labelled "Presets/No force from mission, use mine". I have now ticked this option, hoping that it will prevent this scenario. And hoping of course, that this one won't be overridden by the mission

I fail to see where you can force Takeoff Assistance in ME. Please enlighten me!

@_IvyMike_I tried your solution with JOY_BTN20 on my TM WH throttle (APU START), and I saw the same behaviour as you describe. Note: this switch is a maintained ON/OFF switch. But when I invert the bindings (JOY_BTN20 --> Extend and JOY_BTN20_OFF --> Retract) it works just fine. I cannot explain this, but maybe you can use this logic with your throttle.

Right! I had posted something quite similar some time ago. Nothing has changed. I find that I must practically babysit them. Quite often they fire their Vikhr into the blue sky. Or, when I send them to engage a Vulcan or LAV-25 from like 5 km distance, they don't even try to use their Vikhr. Instead they try to engage with the cannon and get shredded. So I have to call them back. When I tell them to RTB, at least 2 of them will collide. So I tell them to RTB one at a time. Or they crash into the trees. In the Tkhvarcheli mission (which I converted to Ka-50 III), when I tell my wingman 2 to RTB, he will happily land on the hostile FARP. It's frustrating!

I'm puzzled by your "duplicated pedals". Please post a screen shot!

This thread contains a how-to document for editing the "default.lua" files in the game folder:https://forum.dcs.world/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/#elControls_4646929_menu When you use the Quaggles tool, you use default.lua files that contain only your additions and those are located under "Saved Games". The method for editing the .lua lines is he same.

In fact, the "F10 View Options" under Gameplay was set to All. But there is a related option "F10 AWACS View" in the MISC tab which I had forgotten because I set it to TRUE a long time ago. And this is one of the many options the last update had changed. I have now set it TRUE and the F10 view now works. These two options should be side by side on the same tab. And Updates should not make a mess of our option settings. I do not expect ED to follow my advice, and I will need to work out a solution that captures my Options settings and allows me to restore everything ED's faulty process has messed up.

Since the last update, the F10 map no longer displays at all. I have normally set it to "All", but I also tried the other options like "Map only", "Own aircraft only" etc. I excluded override from mission settings. I disabled all modifications I tried with 5 different aircraft modules I ran a repair (slow) The F10 map just won't display. Track attached. I'd be grateful for any helpful suggestion. F10 Theater Map Fail.trk

ED's update had reset a lot of my options settings to their "default" which kept me busy for a while. And I had overlooked this one. Thanks for pointing me to the culprit!

No authorization issues. My recent authorization issues were caused by my ISP's routing. It took so long to reach the DCS server that the connection timed out and I hd to play offline, which you can only do for a few days. I worked around this problem by using VPN. The ISP eventually changed their routing and the problem disappeared completely.

I don't know if this got worse in the last update, but I now find that the backlit labels and the legends of the instruments in the cockpit are almost unreadable. The HUD, Shkval and ABRIS are ok. Only the Ka-50 (both the Ka-50 and Ka-50 III) modules have this blurred cockpit. I attach a screen shot.

Confirm. When English Avionics is selected in the general option, the ABRIS displays English. The issue underlying the OP's complaint is that this last update again changed many of the option settings I had adjusted to my liking over time. Example: most of the warbirds had Takeoff Assitance set to 100%. I suspect ED has added some options to "options.lua", and instead of just inserting the new options into the user's file, they just overwrite the whole file with their defaults.