LeCuvier

The command "iCommandChangeRWRMode" is designed to work with a pushbutton. You cannot change its function.

I have adapted the old "Clear Tkvarcheli" for the Ka-50 III and added 2 wingmen. The wingmen have always been misbehaving. The last update fixed one of the issues: When we had to land somewhere to elude F-5 fighters that were going for us, two of them collided or ran into trees, or staid airborne forever and were shot down. But another issue still exists: When we have killed all targets and I send them back to base, one of them tends to crash into trees, and the other flies to the enemy FARP, sometimes landing safely and sometime killing itself. This happens at the end of a long mission and therefore I didn't save a track which would be huge and unreliable.

Sorry, but but I do not understand what you are trying to achieve. The switch version of this command, for use with HOTAS, button box etc. already exists. This is the LUA line: {down = iCommandChangeRWRMode, name = _('RWR/SPO Mode Select'), category = _('Sensors')}, Creating a duplicate command with a different name won't do any good. The switch command has the same functionality as the keyboard command, so it shows on the same line in Options/Controls, under the same name. The unpredictable behaviour you observe might be caused by you replacing "down" with "pressed" which is probably not compatible with this particular command.

I tried but I cannot make it work.

The R4M rockets work fine after you jettisoned the bomb rack of the SC50 bombs. Which means that you have to use your bombs first. I tried the same scenario with the SC500 bomb and found that the SC500 bomb rack doesn't come off when you press the Jettison button ("Jettison Fuselage Stores"). And consequently, I could not fire the rockets. Is this a bug, or is it how the real thing worked? Unfortunately the flight manual doesn't go into these details. Speculating... In a scenario where you carry a SC500 bomb (maybe to attack a ship), you would probably not want to carry rockets, they would be just dead weight. And takeoff with a SC500 under your belly is hard enough without any extra weight (for me at least).

1. YES, it worked before, for years! 2. I cannot agree with your programmatic logic. If GROUP DEAD would mean that the object no longer exists, then you could not even check for its DEAD status. 3. YES, I have applied the same work-around

First of all, I do understand the logic of LESS THAN But, as I clarified in my August 27th post, the trigger fails if I kill ALL elements of the target group in one attack. With zero elements of the group alive, the condition "LESS THAN 50% ALIVE" should evaluate to TRUE and the trigger should activate. It doesn't.

Some people posted a similar issue for the P-51, and I provided a solution for a wheelbrake command ON/OFF with pressure reduced to 50% (could be anything else). If that's of interest I can post the equivalent for the Kurfürst

I'm not personally affected by this issue as I use MFG pedals with analogue brake axis signals, plus I don't fly the Mustang much. But I got curious and looked for a way to produce an ON/OFF braking command with reduced "power". And I got there after some trial and error. I added this line of code to the file "default.lua" under "DRIVE:\Eagle Dynamics\DCS World\Mods\aircraft\P-51D\Input\P-51D\joystick" : {down = iCommandWheelBrake, up = iCommandWheelBrake, value_down = 0.0, value_up = 1.0, name = _('Wheelbrakes Both 50%'), category = _('Flight Control')}, This creates a new command named "Wheelbrakes Both 50%". When you press the bound button, both brakes get 50% "pressure", and when you release the button the pressure is reduced to 0. This command has an inversed signal: Signal = 1.0 --> pressure = 0 Signal = 0.0 --> pressure = 50% Signal = -1.0 __> pressure = 100% With this in mind you can vary the pressure produced by a button press. I bound the new command with the 50% signal to the pinky button on my VRP stick for a test, and my first landing was not brilliant but safe. One could make the brakes a bit softer by changing the "value_down to a higher value like 0. If you want to use a keyboard button, you need to add the command to the "default.lua" under "DRIVE:\Eagle Dynamics\DCS World\Mods\aircraft\P-51D\Input\P-51D\keyboard"

Glad to hear that you could solve your problem!

It seems that your "default.lua" is different from mine. Here is a screen capture of the 4 TRIM lines from my Options/Controls: The lines mean the same, but the wording is quite different. You have not modified the "default.lua", have you?

The red "!" flags in these two examples are caused by the invalid syntax of these lines. They have the characters like ";;LCtrl" immediately following each other without a "+" in between. Now I wonder whether the invalid code is in the file "Keyboard.diff.lua" under Saved Games, or in the "default.lua" under "DRIVE:\Eagle Dynamics\DCS World\Mods\aircraft\F-16C\Input\F-16C\keyboard". Can you send me both via PM?

Are you sure you are looking at the "Date modified" and not the "Date created"? I'm also wondering about the red "!" in the Options/Controls screen. They might indicate "double binds" (key codes bound to more than one command). If you move the ".diff.lua" away or rename it, do the red "!" flags go away? In that scenario I suspect that the default bindings defined in the file "default.lua" under "K:\Eagle Dynamics\DCS World\Mods\aircraft\F-16C\Input\F-16C\keyboard" would take over. You will find those insufficient as they exist only for a small part of the flight and combat commands. In that state, you might just enter a few of your custom binds and verify that they work, before spending more time. It's really difficult to guess what's going on without having the full picture.

Not having access to your data I can't be sure what happened. But it sounds as if ED, in the course of an update, changed your keyboard bindings. I use only very few keyboard binds, but I have seen the same happen to game controller binds. ED should never change these files, but unfortunately it happens. I therefore keep backup copies of the binding files which are under "C:\Users\XXXX\Saved Games\DCS\Config\Input\". I also document my bindings in an Excel format. This makes it easier if I have to re-do my bindings. The keyboard binds for the F-16 are in the file "Keyboard.diff.lua" under "C:\Users\XXXX\Saved Games\DCS\Config\Input\F-16C_50\keyboard". I suppose you have no "good" backup of this file. In your place, I would want to keep the key codes in the simpit unchanged. I would delete the corrupted "Keyboard.diff.lua" and re-enter the keyboard bindings manually. After testing the set of bindings, I would make a backup copy of that file to a safe location .

The trigger "GROUP ALIVE LESS THAN" works for me if I kill the majority of the group's elements, but not all. It fails only if I kill all elements in a single attack. In your scenario it should work, because you will never kill all elements of the group in one attack.

Well, so let's try to find out! I have removed all Mods which is easy using OvGME. In order to simplify testing, I reduced the target group to one vehicle. If that vehicle is destroyed, the group is < 50% alive. Can we agree on that? If yes, then the triggers "GROUP ALIVE LESS THAN" with parameter = 50% and "GROUP DEAD" should both have the result TRUE when the one vehicle is destroyed. Correct? So I created a test mission "Test Trigger 3.miz" which uses the trigger "GROUP ALIVE LESS THAN" with parameter = 50%. When that condition is TRUE then it should display the message "Oilers > 50% dead!". And I created a control mission which is the same, but uses the trigger "GROUP DEAD" and displays the message "Oilers dead!" when the condition is TRUE. I executed both missions, killing the one vehicle with bombs each time. The results are captured in the attached tracks "Trigger Test 3.trk" and "Trigger Test 4.trk". "Trigger Test 3.trk" shows, on my rig, that the trigger "GROUP ALIVE LESS THAN" does not fire. I hope you can reproduce the result! Trigger Test 3.trk Trigger Test 4.trk Edit: I upload a track "Trigger Test 5.trk" where I use "GROUP ALIVE LESS THAN" with parameter = 50% with a target group that has 3 vehicles. Using guns, I destroy 2 of the vehicles and the trigger works, displaying the message "Oilers > 50% dead!". This confirms what I stated earlier: The trigger works if I kill > 50% of the target group's elements, but it fails if I kill all elements in one attack. Trigger Test 5.trk

The trigger "GROUP ALIVE LESS THAN" is bugged as I have demonstrated in my post https://forum.dcs.world/topic/355492-trigger-group-alive-less-than-not-working-any-more/#elControls_5497431_menu That's nothing to do with mods. If it isn't fixed I can live with that, as I can easily work around it by adding an OR clause.

Does that mean that the trigger "GROUP ALIVE LESS THAN" will not be fixed?

@Lord Vader: As @frontRR suspects (post above), the problem is almost certainly caused by the bug I reported on August 6. The mission uses he trigger "GROUP ALIVE LESS THAN" with a parameter of 90%, and this trigger no longer works correctly. Whether it works or not, depends on how many elements of the group you have destroyed. In my mission the parameter is 50%. But I sometimes kill the target group completely in one attack and then the mission does not progress. Edit: My work-around for my mission: I added an OR line with condition "GROUP DEAD"

As there is no response from the moderators, ED hasn't even acknowledged this bug. @NineLine please take this issue up!

Yes, a pressure change in liquid propagates at very high velocity, so a pressure drop will propagate through the liquid volume very quickly. However, I'm not happy with the second statement. If the system went "all steam" very quickly you would see a brutal pressure increase (because the volume cannot increase by a factor of 5000 in the confined space of the cooling system) which in my layman's assessment might tear the cooling system apart.

I might have a "memory leak", but I don't recall an official statement from ED regarding the WWII fighters in the last 1 or 2 years. No news, in this case, is not good news. ED is not treating us like one should treat customers and that worries me. I own all warbirds so far, but I'm not going to be seduced to buy the F6F Hellcat if it's ever released, and I will hold back on any other new module announced with big trara as long as ED continues to ignore us.

That's overdue! There is nothing about the ARC-210 radio in the manual. And the CCRP HUD display for the likes of GBU-38, CBU-105 etc. still show the old version. When I recently came back to the A-10C III trying to use the CBU-105 (which was one of my favorite weapons eralier) I was lost. In my desperation I ran the training mission, only to find that this mission also shows the old CCRP HUD. In the end I happened to find the right way of course, but the reference material should be updated when new features are added or existing features change! And the A-10C is not the only subject where user manuals are outdated. And to @Yurgon's point: yes there is a lot of information about the A-10C, but it's all over the place; and even though I'm a retiree, I don't want to spend my time searching for scattered information not even knowing whether the various pieces I find are correct. And the didactic quality of what I find is mostly questionable to say it politely.

Sounds strange! Have you done any LUA editing? When you scroll through the lines in Options/Controls, do you see any warning flags, or lines of code highlighted in a reddish or orange colour?

I changed the option "Canopy Reflections" on the "System" to 0 (zero). This reduces the reflections significantly. With that setting I would expect no reflections at all, but it seems to make a significant difference anyway.