LeCuvier

This trigger does not work any more. I don't know when the bug was introduced, but it can't be very long ago. In a A-10C II mission, new threats appear when the previous threat is > 50% dead. Due to the bug, the mission does not progress any more. As a work-around, I have changed the trigger to "GROUP DEAD" which is not quite the same, but I can continue playing the mission. As the original mission would produce a huge track file, I have create a very simple mission where I attack a group of closely spaced tank trucks with dumb bombs. The mission is set to display a message like "Group Oilers 1 dead". The attached track "Trigger Test 1.trk" shows that no message is displayed at all when it should. For comparison I created a second simple mission which uses the triger "GROUP DEAD". The attached "Trigger Test 2.trk" shows the correct message when the target group is destroyed. I don't know whether the bug is in ME or in the mission execution. It could make a lot of missions unusable and should be fixed! Trigger Test 1.trk Trigger Test 2.trk

I confirm. These two switches do not have any effect in the game, although they are correctly bound and they respond when you are on the control options page. I'm afraid you will have to provide a track in order to get any response from ED.

I had the same problem: Easy Communication enabled after the last update. This has already happened in earlier updates, and not only with this option; thus I'm not sure it was the new launcher. As I had often seen my options changed by updates, I created my own launcher that restores my settings into "options.lua". Plus allows me to select a monitor set-up depending on what want to fly.

I'm afraid LUA editing won't do the trick. The Mosquito, like the Spit, has only one brake axis, which has to be used together with the rudder axis to produce differential braking for steering on the ground.

The Easy Communication option apparently does not affect all aircraft modules in the same way.

I had the same problem with another fighter after the last update. The update had activated Easy Communication. After I disabled that option, Push-to-Talk worked fine.

There is an easy way to test whether other buttons on the joystick interfere with the Weapon Release button: Unbind the Weapon Release button from the joystick, use the keyboard bind 'RAlt' + 'Space'. If the "random release" no longer occurs then you know it's a joystick problem.

You are saying that the Dogfight switch and the Uncage Switch randomly trigger missile launch. Seems that they interfere with the Weapon Release button. Do you have all of these switches on the same game controller (e.g. joystick)? Otherwise the theory that it's a joystick problem wouldn't make sense to me.

Good shot! Yes, that was it. I've never encountered that before. Thanks!

I have been flying the Anton days before Monday's update and there was no problem. Today, after updating to the latest version, the throttle no longer responds to any movement of my TM Warthog throttle axis. I have flown the Dora and the F-16, and there is no problem with the throttle. Does anybody elese see this problem?

I have completed a mission with 8 A/A targets, and I have not seen any random missile launch. I wonder if you might have any double-binding on the Weapon Release button.

There are two "default.lua" files: one under ""DRIVE:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\joystick" and one under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-16C\Input\F-16C\keyboard". The lines of code we are talking about are in both. If you modify the code in one of the files only, you will have conflicting command definitions, and that causes your orange or yellow lines. If you modify a line, you must do it in both files. I therefore prefer to add a new line with the modified code and and a different "name". If you add a new line under "keyboard", that command is available only on the keyboard. If you want the new command to be available on keyboard and game controllers, you need to add it to both files.

I tried to get the UFC export by adding the appropriate code to the file "UFC_init.lua". But the allocated field on the secondary screen shows only live data. It does not show the static parts of the panel. That's a bit like the RWR export.

I cannot reproduce your problem. I bound Canopy Handle Up and Down to a button each, and Canopy Switch Up and Down to a button each, and everything works fine. Except Canopy Handle UP and Down are reversed. And I can still operate the commands with the mouse.

I confirm that the axis previously bound to "JOY_Z" was either replaced by "JOY_RZ", or "JOY_RZ" was added to "my"binding to "JOY_Z" for the aircraft modules listed below: AJS-37 AH-64D Pilot AH-64 CP/G AV88NA Bf-109K F-15E had "Thrust" binding to "JOY_RZ" added to "my" bindings of Throttle Left and Right to "JOY_RZ" and "JOY_Z" resp. F-16C I-16 Ka-50 Ka-50 III P-51D Spitfire It took my time again to correct these unwanted bindings and it's not the first time an update has overwritten my bindings. @BIGNEWY this is not caused by mods. It's caused by a persistent glitch in the update process which does not "respect" the bindings I had set and which should be sacrosanct. I understand that software bugs do occur even in the best development process; but I'm running out of patience with this totally unnecessary nuisance. Edit: I have the TM Warthog throttle and I suspect that the problem is related to default bindings for that specific device which are defined somewhere I don't know where. People who don't have that throttle might not be affrcted.

That's impressive stuff! I have done a lot of VB programming, but I struggle with Lua. It will take me some time to understand your logic to the point that I could apply it. I wonder if it will work with bindings under "...\Saved Games\..." using the Command Injector developed by @Quaggles.

I didn't understand this when I first read it. But looking at the file after today's update I think I get it. Heatblur has a very different approach in the "default.lua". With a single line in that file, using the function "knob_inc_dec_variants", they can create 6 bindings. I used to be very confident editing these files, but for this module I have to re-learn "my trade". The good news is that the people at Heatblur do a strling job with bindings so I will have much less editing to do.

I'm not sure we have enough insight to make that statement, but yes, it looks like the software would need a clean-up effort, with no feature additions during that time. As to Open Beta, I'm one of those who used Open Beta only, with the Stable version only in backup. But I agree, it cannot work for the reasons mentioned above. For a beta test version you need a population of disciplined users who follow the defined process for reporting issues/bugs, examine issues thoroughly and document them clearly.

An exaggerated statement in my opinion. I land the Kurfürst quite frequently and I have no problem at all getting down to taxying speed after touchdown. I use analogue pedals of course. With ON/OFF signals that might be quite tricky, but I've never tried.

Thank you for giving us the facts! And don't worry about trolls who bitch about postponed release dates! Quality should always have priority over meeting target dates.

I tried it with all 3 German warbirds and found it rather useless. I only got a meaningful indication when I was so close that I didn't need it anymore.

1. It is "normal" that the buttons on throttle and stick are not clickable in the cockpit. As far as I can remember, it's that way on all aircraft modules I own. 2. The animation of the Push-to-Talk button is in fact missing, and that's the only missing animation. The animation of the propeller pitch rocker switch ("Drehzahl") is working fine. There are no "...two missing animations". In conclusion, there is only one bug. You should report that in the proper thread under FW-190 A / Bugs and Problem; not under "Squadron Recruiting"!

This is ok for "mature" aircraft modules that see very few additions or changes to the stock files. But this thread is about the F4-E which is in Early Access. And modules in EA tend to see additions and changes to the stock files with just about every update. And when you restore your backed-up files you lose these updates. In other words, you freeze functionality. Better use the @Quaggles tool!

I have been using this tool for quite some time now, and I recommend it to everybody who has made additions to the stock "default.lua" or intends to do so.

But, unless something fundamental has changed, the next update will restore the "original" default.lua, without these additions. Correct?