LeCuvier

No. With the line I added you have to use two pushbuttons. Alternatively, you can use a maintained ON/OFF switch and bind Cage to the ON position of the switch, and Uncage to the OFF position. Only ED can provide a Cage/Uncage toggle. And, I guess you can create it with some external software like TARGET (?)

I do use that button of course.

I like to use the F10 view to get a picture of the situation, at mission start and during the mission. For most missions, the F-10 view does not show the map as I saved it in ME. I need to re-position it and adjust the zoom in order to make it useful. Sometimes it's completely off. I usually save the mission with the map in the right position and zoom, and I would like to see it that way when I use F10.

Works as expected for me. I normally use the speedbrake switch on the TM WH throttle. But the key commands work as well: B extends the brake as long you press the B key. Movement stops when you release the key. LCtrl + B starts the retraction movement. The movement continues after you released the key, except if landing gear is down... LShift + B stops the retraction movement I have managed to add a keyboard command that does this: RCtrl + B retracts the speedbrake, but only as long as you keep the keys depressed This requires adding a line to a LUA file and is obviously not to everybody's liking.

In the 20-Oct update to 2.9,0 ED has added most of the lighting axes: -- Lighting dials {action = device_commands.Button_21, cockpit_device_id = devices.LIGHT_SYSTEM, name = _('Engine Instruments Lights'), category = {_('Lighting Panel')}}, {action = device_commands.Button_22, cockpit_device_id = devices.LIGHT_SYSTEM, name = _('Flight Instruments Lights'), category = {_('Lighting Panel')}}, {action = device_commands.Button_23, cockpit_device_id = devices.LIGHT_SYSTEM, name = _('Floodlight '), category = {_('Lighting Panel')}}, {action = device_commands.Button_24, cockpit_device_id = devices.LIGHT_SYSTEM, name = _('Console Light'), category = {_('Lighting Panel')}}, {action = device_commands.Button_25, cockpit_device_id = devices.LIGHT_SYSTEM, name = _('Formation Lights'), category = {_('Lighting Panel')}}, {action = device_commands.Button_26, cockpit_device_id = devices.LIGHT_SYSTEM, name = _('Refuel status indexer LTS '), category = {_('Auxiliary lighting control panel')}}, But, as far as I can see, they forgot Auxiliary Instruments Lights.

You are right. I was misled by one of the posts above that talked about axis settings. I tried "my" method but it does not work in the F-15E. Possible reason: In the Strike Eagle the LUA code uses the "down" command, while the F-16 uses the "pressed command.

The fix I posted in that thread for the F-16 works with the POV hat there. This thread here is about the TDC axis settings. Therefore "my" fix cannot help here.

I do not agree that this would be so great, and I do not see a lot of support for your suggestion. On the other hand, I do not believe in calling other people's suggestions "nonsense". Yes, the 90's were a long time ago, but basic rules of politeness still apply.

Where is that option set? I do not see it.

For Rotor Tip and Anti-Collision Lights, it's possible to create separate ON and OFF pushbutton commands, or commands for 2-position switches, by simple LUA editiing. For the multi-position commands I don't see a way to do that.

As the OP states, it works like in the Hornet. And I suppose that's how the antenna elevation control works in the real thing. As far as I'm concerned, I use the coolie hat switch on my TM Warthog throttle and I'm happy with that. I also tried using the slider on my throttle and that worked fine for me. But if your slider doesn't provide tactile feedback of its center position you would not be able to set it to center and the antenna might creep up or down. So I guess it's logical for Razbam to implement the realistic function (rate of change axis), but they should certainly implement a binding for an absolute position axis as well. I would find it even better if ED provided an axis functionality that supports both for absolute position and rate of change.

I've had this problem recently and it lasted several days, so my saved authorization was no longer valid. Using the tracert utility I found that my internet provider had created a routing nightmare with multiple stations and some showing long delays. This caused a time-out and access to the authorization server failed. Somebody suggested a work-around which worked for me: Use VPN and select a location really different from where you are.

I guess everybody would have this issue if they wanted to use VOIP on the original A-10C. The file "Throttle - HOTAS Warthog.lua" in the folder "...\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\A-10C_2\Input\A-10C_2\joystick" contains some lines that are missing in the file for the A-10C: -- start VoIP radio global commands -- in case you need to open commands in the cockpit {down = iCommandVoIPRadioPushToTalkEnableDisableVoice, up = iCommandVoIPRadioPushToTalkEnableDisableVoice, value_down = 1.0, value_up = 0.0, name = ('HOTAS MIC Switch Down (VOIP)'), category = _('HOTAS')}, {down = iCommandVoIPRadioPushToTalkEnableDisableVoice_2, up = iCommandVoIPRadioPushToTalkEnableDisableVoice_2, value_down = 1.0, value_up = 0.0, name = ('HOTAS MIC Switch Aft (VOIP)'), category = _('HOTAS')}, {down = iCommandVoIPRadioPushToTalkEnableDisableVoice_1, up = iCommandVoIPRadioPushToTalkEnableDisableVoice_1, value_down = 1.0, value_up = 0.0, name = ('HOTAS MIC Switch Forward (VOIP)'), category = _('HOTAS')}, -- end VoIP radio commands The file "default.lua" for the A-10C does contain these lines and that's why you can bind them to any game controller that doesn't have a dedicated .lua file. You can wait for ED to fix this omission, or you can help yourself by copy & pasting these lines into the file for the A-10C. If you want to do that: 1. use the free Notepad++ editor and set "Language" to "Lua". 2. insert the lines just after the line that reads keyCommands = { 3. Note that the file will be overwritten by the stock file if you do a Repair or Update. Therefore, make a backup copy of the changed file.

Remember: any changes/additions to the "default.lua" in the game folder are lost when you update or repair. As a minimum, make a backup copy of the changed file. Best solution is to use the Quaggles tool referred to some posts above.

@Lanser: It seems that you are tryig to do something with DCS BIOS. This thread is not about DCS BIOS; it's about editing the "default.lua". For DCS BIOS there is another subforum I believe. Edit: Adding lines to "default.lua" I can create a pushbutton command that will raise the cover and set the switch to ON. Example: {down = engctrl_commands.left_eng_master_cover, up = engctrl_commands.left_eng_master_sw, cockpit_device_id = devices.DEEC, value_down = 1.0, value_up = 1.0, name = _('Left Engine Master Cover and Switch UP'), category = {_('Right Console'), _('Engine Panel')}}, I can also create a command for a maintained ON/OFF switch. HOTAS switch ON will raise the cover and set the engine master switch to ON. HOTAS switch OFF will set the engine master switch to OFF. However it will nat close the cover. I can only initiate 3 actions with one command. Example: {down = engctrl_commands.left_eng_master_cover, pressed = engctrl_commands.left_eng_master_sw, up = engctrl_commands.left_eng_master_sw, cockpit_device_id = devices.DEEC, value_pressed = 1.0, value_down = 1.0, value_up = 0.0, name = _('Left Engine Master Switch and Cover UP/DOWN'), category = {_('Right Console'), _('Engine Panel')}}, You can use the same approach for the Right switch of course.

That confirms my experience. I cannot override server-imposed restrictions like "no labels" in MP.

I'm not quite as stupid as you seem to believe. I know I can change the mission. But mission files can be quite complex. And I do not want to waste my time trying to figure out where ther mission settings are bothering me.

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