LeCuvier

A-10C and FC3 seem to be the exceptions. On all other aircraft I tried, F4 view is forward-looking. In most modules from the right-hand side of the fuselage; but in some from the left-hand side. The command name "Look back view" is certainly misleading.

@Icebear: You say that ""Waffenauslöser" doesn´t exist in both files". Where is it defined then? It can only be defined in a "default.lua" or an equivalent device-specific .lua like the "Throttle - HOTAS Warthog.lua". The .diff.lua don't define commands, they only store what you have bound to commands.

Sur le forum anglais on trouve ceci: As soon as you click, it closes, but also starts the engine. If your engine doesn't start then, means you forgot something else. On dirait que tu as omis une manip avant.

Ich habe selbst noch nie die .diff.lua die unter Saved Games liegen von PC zu PC transferiert, spreche also nicht aus eigener Erfahrung. Aber nach dem was ich in anderen Threads gelesen habe muss man die GUID (Globally Unique ID) im Dateinamen der kopierten Datei ändern. Beispiel: VPC-MongoosT-50 {7F204EB0-8E49-11e7-8001-444553540000}.diff.lua Die GUID ist die Zeichenfolge in geschweiften Klammern. Der PC (oder DCS?) vergibt für jeden neu erkannten Game Controller eine GUID. Die von Dir transferierte Datei enthält aber die "alte" GUID, die man ersetzen muss. Um dann nicht 2 gleichnamige Dateien zu haben muss mon die vom PC generierte .diff.lua natürlich vorher in einen Backup schieben. Wie gesagt, ich habe das selbst noch nie gemacht, ich habe mir das aus dem gelesenen zusammengereimt. Viel Erfolg!

I have copied these files from from "Open Beta" to "Stable" and there was no need to rename the "....diff.lua" files. I'm fairly sure you can just copy the files over to your new computer. These files are under "C:\Users\YOURNAME\Saved Games\DCS.openbeta\Config\Input\AIRCRAFTNAME"

The duplicated orange lines are not necessarily a sign of trouble. They indicate normally that, between the "default.lua" under "\joystick" and the one under "\keyboard", you have commands with the same name but different function. Are you sure that the command "Waffenauslöser" has exactly the same detail definition in both files? What looks funny to me is that the devices "microhelis..." and "BU0836A..." seem to be considered as keyboards. I say that because they can only be bound to the command version defined under "\keyboard". I wonder if DCS has a problem with additional keyboards. Could you somehow modify their interface so that they don't appear as keyboards? PS: I think you can bind your cyclic to the lower one but not the upper one. You stated the opposite. Further: have you tried with the Waffenauslöser bound to one of the button boxes (upper line)?

I have added a lot of commands to this file, but generally the value_down and value_up statements have values like 1.0, -1.0 or 0.0. I do not believe that your values like 0.1 and 0.2 will work. Further, you can handle most of your desired additions without going into "clickabledata.lua". For example the IFFCC 3-position switch: {down = iCommandPlaneAHCPIFFCCOn, up = iCommandPlaneAHCPIFFCCTest, name = _('IFFCC switch ON/TEST'), category = _('Armament HUD Control Panel')}, {down = iCommandPlaneAHCPIFFCCOff, up = iCommandPlaneAHCPIFFCCTest, name = _('IFFCC switch Off/TEST'), category = _('Armament HUD Control Panel')}, You can handle the ALT SCE switch in the same way. So you don't need to experiment to find the right command values. For HUD Mode Day/Night I use this line: {down = 3006, up = 3006, cockpit_device_id = 7 , value_down = 1.0, value_up = 0.0, name = _('AHCP HUD Mode 2-Pos DAY/NIGHT'), category = _('Armament HUD Control Panel')}, The last line in your post cannot work, because you omitted the "," at the end of the line. I will call it a day, it's nearing midnight here.

No. Changes to this file pass Integrity Check, no problem at all. I have more than hundred such additions. I created two lines of code, you decide which one you want to use: {down = iCommandPlaneGearUp, up = iCommandPlaneGearDown, name = _('Landing Gear Control Handle 2-Position UP/DOWN'), category = {_('Left Vertical Panel')}}, {down = iCommandPlaneGearDown, up = iCommandPlaneGearUp, name = _('Landing Gear Control Handle 2-Position DOWN/UP'), category = {_('Left Vertical Panel')}}, The first one retracts the gear when the switch transitions to ON and extends it when the switch transitions to OFF. The second line does the opposite. When you open the file "default.lua" with Notepad++ you see these lines at the beginning of the file: The line of code you want to add must be below line 7. I recommend you add it in line 8 so you can easily find it. Note: 1. The line numbers are not in the file, Notepadd++ adds them in the view. 2. DCS Update or Repair restores the original file. Therefore, save a backup copy of the modified file. If you have multiple modified files it's a good idea to use OvGME to manage updates.

It does not exist for the Hornet. It would be easy to create it by adding a simple line of code to the file "efault.lua". Note: I created this command for several aircraft, but stopped using it. That's because, if you don't have the switch in the right position at mission start, you wil find your fighter dropping on its belly in a mission that starts on the ground, or your landing gear extending in a mission that starts airborne.

In a cold-start mission you must first move the two throttles back over the "hump" from IDLE to OFF, then back to IDLE before they will respond to any movement. Going from IDLE to OFF activates the switches JOY_BTN29 and JOY_BTN30 in the throttle that should be bound to "Right Engine Throttle set OFF" and "Left Engine Throttle set OFF" by default. Re your statement " If I start in flight one throttle works and the other only goes from 0% to 100%.", I don't understand what you are talking about. Can you be more specific?

Yeah, no more pre-purchase! ED will like that.

If ED had a "money-back" or "return for credit" option, I would return the Mossie immediately. The incredible inertia makes it very hard to control it and target something, and the horrendous cockpit layout (realistic though) confuses me. It makes a nice big target though.

I fully agree. Get rid of this useless ballast!

I use version 2.7.10.19473 and the right wing gear indicator does have the red band. Do you use a custom texture?

I flew her for about 20 minutes, and the radar antenna elevation was always controllable. I suspect you have duplicate binding(s) on that axis. Go to Options/Controls, select F-16 Sim, select "Axis Commands" and remove all unwanted bindings.

The AI fighters mostly let you target them head-on and they don't shoot in a head-on situation. I just tried this with a Dora vs Spit AI set to "Ace", and it was like target practice. I know that in the (somewhat distant) past they would engage me head-on and quite often got me, especially at the higher skill levels. I agre that this tactic would not work in MP, the guys are generally too good for that. Unfortunately I cannot fight in MP due to my poor eyesight.

How to Create Macros_2019-07-26.pdf

In addition to what @Diimasaid: 1. VoiceAttack can produce series of button presses from a single voice command. I have tried VA a bit and it's fairly basic and therefore stable. 2. One can add one (without failing the IC) macro to the "Macro_sequencies.lua but that requires a bit of basic programming. Auto-start and auto-stop is done that way. I use such a macro to turn all interior lights up, for several modern fighters. 3. I can produce up to 3 button presses from a single push button binding by adding commands in "default.lua" I do not find much info about the use of the ECM panel, and I wonder: Is there really a scenario where you would push all 6 ECM buttons in?

Why are you loading a profile? The A-10C and A-10C II come with default profiles for the TM WH HOTAS. You can just fly it.

During the update process I got this message that it cannot delete "edCaptoGlove.dll". I wanted to attach the autoupdate log, but cannot find it. The update ended unsuccessfully. I deleted the dll manually and then could update successfully.

Seems to be the same problem as with the Mustang. We have separate profile files for the two versions under \Saved Games, but we cannot the select version in Options/Controls. For the P-47D we have version-specific categories for the D-30 and D-40. Hopefully ED will introduce that solution for the Spit and Mustang as well.

No, you will just get red or orange lines in Options/Controls as a warning that you have bindings with different functionality but same name. But it's certainly better practice to add new "slow" bindings. And make sure the slow bindings names are different from the names of the original bindings.

Out of curiosity I tried to create a single command binding that would set the switch in the cockpit very briefly to "OFF" and then to "Anti-Skid". And it seems to work. It requires addition of this line of code to the file "default.lua": {down = gear_commands.AntiSkidSw_EXT, pressed = gear_commands.AntiSkidSw_EXT, cockpit_device_id = devices.GEAR_INTERFACE, value_down = -1.0, value_pressed = 0.0, name = _('ANTI-SKID Switch To ANTI-SKID via OFF'), category = {_('Left Auxiliary Console')}}, This will create a new command "ANTI-SKID Switch To ANTI-SKID via OFF" which you need to bind in lieu of the original command "ANTI-SKID Switch - ANTI-SKID". It's a deviation from realism, but given the fact that most of us don't have spare 3-position switches it won't weigh on my conscience.

@352nd_HossI can help you kick possible .lua solutions around, preferrably one issue at a time. For the P-51 Cold Air to RAM there is a solution in this post: https://forums.eagle.ru/topic/267849-p-51-ram-air-missing-after-patch/#elControls_4682233_menu I'm using this fix. It shows the animation and I see the effect in boost pressure.

The anti-skid switches in the Hornet and in the Warthog also have the OFF position, and there is probably a reason for it. There may be operational situations (e.g. a defect in the anti-skid system), where you need to disable the anti-skid function and where you do not want to switch to Parking brake. The F/A-18C guide for example states that anti-skid is not used in carrier operations. I did a test: For the Viper, I bound each of the 3 switch positions to a pushbutton and found that there is an interlock. You can go from Anti-Skid directly to Parking Brake, but you cannot do the reverse. From Parking Brake you have to go to OFF first, and then you can go to Anti-Skid. That's why you cannot switch to Interlock with your preferred set-up- Strangely, this interlock does not exist when you operate the switch with the mouse. PS: I could think of a lua edit that might make the 2-way switch work, but it's probably not worth it.