LeCuvier

sorry, I was in too much of a hurry. Here is the correct tracert result.

@MAXsenna: I have run tracert, see attachment. What can I conclude from this? I tried to go to the site with this IP address (76.223.54.146) and it goes to a site that's for sale. No comprendo...

Well, the provider of the box is my ISP and is also my cellphone service provider. And from my cellphone, with mobile data, I can get to the ED server.

ED could certainly fix this. I suspect wold not be in "clickabledata.lua" but in the software that uses it.

sure, that was one of my first actions. I will try to persuade my internet provider to replace the LiveBox.

I can turn off my iPhone's WiFi and connect to the DCS World web site while I'm at home. And I can even get to the user support page and start creating a ticket this way. So maybe the problem is caused by my Live-Box...

I do not have access to another provider, and a friend's house is not practical. Tried to connect to my iPhone's hotspot, but that does not work. Thanks

I'm a long-time user of DCS World and know how to help myself most of the time. But since several days I'm stuck As the title says, I cannot connect to the ED web site and therefore I cannot even contact support. I do get to the site sometimes after a long time, but mostly it times out. And I never make it to the support page where I could log a support ticket. For the same reason, I cannot get authorization when I start the game, and have to wait forever before I can play offline. And soon I won't even be able to play offline. I have checked the firewall for blocked sites and see nothing. I have ven disabled the firewall temporarily but it made no difference. No problem connecting to any other web site and internet access is generally fast. I would appreciate if someone could make support contact me.

@Munkwolf: I re-created the file adding blocks of lines and testing step by step. Now got it working with the comma. I suspect that one line was problematic and I left it out. Please allow an off-topic question: am I the only one not able to get authorization? I also find that I cannot open http://www.digitalcombatsimulator.com although I have good internet access.

Yes I used the skeleton format you show. And I got several blocked joystick commands. And after I removed the comma the problem went away. The funny thing is, when I use your "default.lua" (A-10C II, joystick), I don't get the problem. I will have to do more testing later. It's a nightmare right now as I cannot connect to the authorization server and every game load takes forever.

I'm moving to use the input injector and my first module was the A-10C II. I want to just migrate the custom bindings I created over time to the Injector format rather than adopting the huge files Munkwolf laudably produced. My collection includes some axis commands, so I added these lines: axisCommands = { -- Enter axis commands here {action = 3001, cockpit_device_id = 49, name = _('Engine Instruments Lights Axis')}, {action = 3002, cockpit_device_id = 49, name = _('Flight Instruments Lights Axis')}, {action = 3003, cockpit_device_id = 49, name = _('Auxiliary Instruments Lights Axis')}, {action = 3005, cockpit_device_id = 49, name = _('Flood Light Axis')}, {action = 3006, cockpit_device_id = 49, name = _('Console Light Axis')}, {action = 3011, cockpit_device_id = 54, name = _('UHF Radio Volume Axis')}, {action = 3005, cockpit_device_id = 55, name = _('VHF AM Radio Volume Axis')}, {action = 3005, cockpit_device_id = 56, name = _('VHF FM Radio Volume Axis')}, {action = 3013, cockpit_device_id = 38, name = _('Yaw Trim Knob Axis')}, } and, following Munkwolf's structure, added a comma to the line above so it looked like this: }, With this, my added key commands all worked; but several joystick commands showed red warnings in Options/Controls and they were not functional. When I removed the comma the problem was gone. So my question is: If I want to add an axis section, should the key section be terminated wih a comma?

Look here https://forum.dcs.world/topic/270487-quaggles-dcs-input-command-injector-mod-v109-store-custom-input-commands-safely-in-saved-games-instead-of-merging-them-with-developer-changes-each-update/#elControls_4651461_menu

that's smart!

Understood. But there is nothing I can do there. All the multiposition switches of the sensor panel have that problem. Probably due to WIP.

Try these: {action = extlt_commands.formation_lt_knob, cockpit_device_id = devices.EXTLT, name = _('Formation Lights Axis Axis')}, {action = extlt_commands.pos_lt_knob, cockpit_device_id = devices.EXTLT, name = _('Position Lights Axis')},

These CW/CCW commands are already there, they just have funny names like "AN/APG-70 Radar: OFF/STBY/ON/EMERG" and "AN/APG-70 Radar: EMERG/ON/STBY/OFF". Same for INS mode. Problem is, these commands don't work. Bugs or WIP?

1. No, I'm saying that a "rotating knob" must be defined in the "clickabledata.lua". 2. There is already an axis binding for radar antenna elevation. What other radar commands are you looking for? Please state explicitly! Edit: To my surprise I could produce an axis binding for the INS Mode knob although it's really a multi-position switch: {action = snsrctrl_commands.ins_knob, cockpit_device_id = devices.INS, name = _('INS Knob Axis')}, and same for the Radar Mode selector: {action = snsrctrl_commands.rdr_power_sw, cockpit_device_id = devices.AN_APG70, name = _('Radar Mode Selector Axis')}, But I guess you are looking for CW/CCW button commands. Not sure if I can produce these. Will try.

I took a shot at it and created axis commands for most of the rotating knobs. I added the lines below into the "default.lua" under "DRIVE:\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-15E\Input\F-15E\joystick" -- added HWF -- Interior Lights {action = intlt_commands.console_lt_knob, cockpit_device_id = devices.INTLT, name = _('Console Lights Brightness Axis')}, {action = intlt_commands.inst_pnl_lt_knob, cockpit_device_id = devices.INTLT, name = _('Instruments Panel Lights Brightness Axis')}, {action = intlt_commands.ufc_bcklt_br_knob, cockpit_device_id = devices.INTLT, name = _('Gauges/UFC Backlights Brightness Axis')}, {action = intlt_commands.chart_lt_knob, cockpit_device_id = devices.INTLT, name = _('Charts Spot Light Brightness Axis')}, {action = intlt_commands.flood_lt_knob, cockpit_device_id = devices.INTLT, name = _('Storm FLood Lights Brightness Axis')}, {action = intlt_commands.chart_lt_lamp, cockpit_device_id = devices.INTLT, name = _('Chart Spot Lamp Brightness Axis')}, -- Volume Knobs {action = volctrl_commands.caution_vol, cockpit_device_id = devices.TEWS, name = _('Caution Volume Axis')}, {action = volctrl_commands.launch_vol, cockpit_device_id = devices.TEWS, name = _('Launch Volume Axis')}, {action = volctrl_commands.ics_vol, cockpit_device_id = devices.ICS, name = _('ICS Volume Axis')}, {action = volctrl_commands.wpn_vol, cockpit_device_id = devices.PACS, name = _('WPN Voume Axis')}, {action = volctrl_commands.ils_vol, cockpit_device_id = devices.ILS, name = _('ILS Volume Axis')}, {action = volctrl_commands.tacan_vol, cockpit_device_id = devices.TACAN, name = _('TACAN Volume Axis')}, --UFC {action = ufc_commands.UFC_VOL_R1, cockpit_device_id = devices.UFCCTRL_FRONT, name = _('UHF Radio 1 Volume Axis')}, {action = ufc_commands.UFC_VOL_R2, cockpit_device_id = devices.UFCCTRL_FRONT, name = _('UHF Radio 2 Volume Axis')}, {action = ufc_commands.UFC_VOL_R3, cockpit_device_id = devices.UFCCTRL_FRONT, name = _('UHF Radio 3 Volume Axis')}, {action = ufc_commands.UFC_VOL_R4, cockpit_device_id = devices.UFCCTRL_FRONT, name = _('UHF Radio 4 Volume Axis')}, {action = ufc_commands.UFC_BRT_CTRL, cockpit_device_id = devices.UFCCTRL_FRONT, name = _('UFC LCD Brightness Axis')}, I did not test every item because I have only one slider I can mess with. Generally, they use only half of the available input signal range, and you need to invert them. The lines need to be inserted in the axis commands part of the file near its end. I inserted them right underneath the line s for Hud Control. The commands added to this file work only from the pilot's cockpit. If you want to use them also from the WSO cockpit, you need to add them the the file under "...\Mods\aircraft\F-15E\Input\F-15E_WSO\joystick", and you need to bind them again. Anything else you want please let me know specifically by item. I did not find any missing knob for Radar and I did not find anything for INS. My method works only for rotating knobs. If the cockpit has a rocker switch I cannot turn that into an axis.

I have held back because I think we are having a "very early access" and there will be lots of additions by Razbam, but also I need to learn more about this bird.. But if you secifically list a reasonable number of high-priority items I might be tempted to get started.

This is a very common issue when you create an axis using information from "clickabledata.lua", and in that case you can't complain because you have customized the function. But if this happens on an axis in the stock file it's a bug and should be treated as such.

I have never tried the Quaggles injector, but if they are in the injected repository and in the updated stock file you will have duplicates, won't you?

It should be no problem. But I hesitate to start making additions at this early point in time, because I expect RAZBAM to add a fair number of bindings through Early access, and then I have to clean up by removing the duplicates. The same consideration applies to the many axis bindings that are no there yet.

Thanks for the feedback! I think it's a lousy design. Even when I play offline, ED should respect the current settings that I have made in "options-lua". I have found a way to manage these settings in a database from which I can re-create the correct options.lua. This also allows me to simply switch to different monitor setup (export) settings . I have now added the "takeoff assist = 0" for all warbirds to this tool.

I had set all takeoff assistance to 0%. As I just found out by checking something else, all warbirds (except TF-51) had their Takeoff Assistance set to 100% again. I don't know which update did this, but it's a real pain in the butt that we have to go through these settings again to void unwanted changes from updates.

Axes for HUD brightness and Contrast are available, but yes, many axes are missing. This is the first cut of Early Access, so I would not see this as bugs but Work in Progress. I will therefore not waste time creating axis bindings myself.