LeCuvier

maybe game mode and game avionics mode are set active in the mission? Check mission options.

I agree, if we had defined values for ON and OFF this could not happen. But it's still strange that the problem only occurs in the "Death Valley" mission.

Right engine start fails when the right engine cut-off valve should open. The lever goes up, but it seems to me that the valve isn't really opening and so the engine is starved of fuel.

It's not that simple. For my test I removed all additions to "default.lua". When I moved these back in, the problem was back; even with "Synchronise Cockpit Controls with HOTAS Controls at Mission Start" disabled. But that's only in the stock mission "Death Valley". I have created a cold-start mission based in Beslan, and there the auto-start works all the time; also with "Synchronise Cockpit Controls with HOTAS Controls at Mission Start" enabled. These are my additions to "default.lua". None are related to the engine functions: {down = 3002, up = 3002, value_down = 1, value_up = 0, cockpit_device_id = 23, name = _('Helmet-mounted System 2-Pos. On/Off'), category = _('Ins Targeting Mode Controls Panel PVR')}, {down = 3002, value_down = 1, cockpit_device_id = 23, name = _('Helmet-mounted System ON'), category = _('Ins Targeting Mode Controls Panel PVR')}, {down = 3002, value_down = 0, cockpit_device_id = 23, name = _('Helmet-mounted System OFF'), category = _('Ins Targeting Mode Controls Panel PVR')}, {down = 3001, up = 3001, value_down = 1, value_up = 0, cockpit_device_id = 11, name = _('Laser standby 2-Pos ON/OFF Switch'), category = _('Ins Targeting Mode Controls Panel PVR')}, {down = 3017, up = 3017, value_down = 1.0, value_up = -1.0, cockpit_device_id = 12, name = _('Automatic tracking/gun sight 2-Pos AT/GS'), category = _('Ins Targeting Mode Controls Panel PVR')}, {down = 3001, up = 3001, value_down = 1.0, value_up = -1.0, cockpit_device_id = 12, name = _('Master arm 2-Pos ON/OFF'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3006, up = 3006, value_down = 1.0, value_up = -1.0, cockpit_device_id = 12, name = _('Cannon round selector 2-Pos HE/API'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3004, up = 3004, value_down = 0.2, value_up = 0.1, cockpit_device_id = 12, name = _('Weapon mode Burst Length 3-Pos HIGH/MEDIUM'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3004, up = 3004, value_down = 0.0, value_up = 0.1, cockpit_device_id = 12, name = _('Weapon mode Burst Length 3-Pos LOW/MEDIUM'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3020, up = 3020, value_down = 1.0, value_up = 0.0, cockpit_device_id = 12, name = _('Cannon rate of fire 2-Pos LOW/HIGH'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3005, up = 3005, value_down = 1.0, value_up = -1.0, cockpit_device_id = 12, name = _('Weapon Control 2-Pos MAN/AUTO'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3007, up = 3007, value_down = 1.0, value_up = -1.0, cockpit_device_id = 51, name = _('Lighting Night Vision Cockpit Switch 2-Pos ON/OFF'), category = _('Ins Wall panel')}, {down = 3006, value_down = 1.0,cockpit_device_id = 2, name = _('Battery 1 Cover Open'), category = _('MODDED')}, {down = 3006, value_down = -1.0,cockpit_device_id = 2, name = _('Battery 1 Cover Close'), category = _('MODDED')}, {down = 3001, value_down = 1.0,cockpit_device_id = 34, name = _('Gear Lever DOWN'), category = _('Ins Forward panel and gauges')}, {down = 3001, value_down = -1.0,cockpit_device_id = 34, name = _('Gear Lever UP'), category = _('Ins Forward panel and gauges')}, {down = 3001, up = 3001, value_down = -1.0, value_up = 1.0, cockpit_device_id = 34, name = _('Gear Lever 2-Pos UP/DOWN'), category = _('Ins Forward panel and gauges')}, {down = 3022, up = 3022, value_down = 1.0, value_up = -1.0, cockpit_device_id = 12, name = _('Jettison Fuse 2-Pos ARM/DISARM'), category = _('Ins Weapons Status and Control Panel PUI-800')}, {down = 3002, up = 3002, value_down = 1.0, value_up = -1.0, cockpit_device_id = 59, name = _('K-041 Targeting Power 2-Pos Switch ON/OFF'), category = _('Ins Targeting Mode Controls Panel PVR')}, {down = 3006, up = 3006, value_down = -1.0, value_up = 1.0, cockpit_device_id = 33, name = _('Autopilot Altitude Hold Mode 2-Pos BARO/RALT'), category = _('Autopilot Panel')}, {down = 3003, up = 3003, value_down = -1.0, value_up = 1.0, cockpit_device_id = 28, name = _('Autopilot Desired Heading/Desired Track 2-Pos DH/DT'), category = _('Autopilot Panel')}, {down = 3001, value_down = 1.0, cockpit_device_id = 7, name = _('HUD Brightness FULL'), category = _('Ins HUD controls')}, {down = 3001, value_down = 0.5, cockpit_device_id = 7, name = _('HUD Brightness DIMMED'), category = _('Ins HUD controls')}, {down = iCommandPlane_RouteMode, up = iCommandPlane_RouteMode, name = _('Route Mode 2-Pos ENGage/DISENGage '), category = _('Ins Collective Stick')}, -- Macros {down = 300, cockpit_device_id = 60, name = _('Macro all internal Lights UP'), category = _('Cheat')}, {down = 5000, cockpit_device_id = 60, name = _('Macro all internal Lights DOWN'), category = _('Cheat')}, -- in the axis section: {action = 3002, cockpit_device_id = 8, name = _('IT-23 TV Brightness Axis')}, {action = 3003, cockpit_device_id = 8, name = _('IT-23 TV Contrast Axis')}, I have started to add messages to "Macro-sequencies so I have an idea where the start-up sequence is; but that's very tedious work and I have not progressed to where the right engine start fails.

I tested as you requested, and I do not get the failure. This would suggest that I have bound a engine-related command to a switch that's in the wrong position. However, I have not bound any switch to engine functions because I need all the switches I have when I'm in action.

1. the sensor control switch does not control the seeker at all. Its positions LEFT, RIGHT, AFTcontrol which DDI is associatrd with the TDC. 2. For the TDC slew vertical and horizontal axes on the Throttle grip you should set a curve to make it more controllable. I use Curvature = 20 and Y Saturation = 50% 3. If you want to use "Realistic TDC Slew" you will find that "TDC Push" (Button 1) doesn't work well. I have bound a button on my stick to that command. If you are short of buttons you should probably not use "Realistic TDC Slew". 4. I don't think that your stick has any spare axis that you could use for the TDC. And you cannot bind a button to an axis

I have tried the Uncage and Cage on my system and it works fine. Note: I use the "Realistic TDC Slew", so the seeker uncages automatically when I depress the button bound as "TDC Depress". But the Uncage works also if I use the China hat on my Warthog throttle. I wonder if you have assigned the TDC to the DDI showing the Maverick format page (if that page is on the right DDI, move the Sensor Control Switch to the right. You should then see the "diamond" in the upper right of that page). If the diamond doesn't show on the Maverick format page, you won't be able to uncage the seeker.

You are right of course about the time. I'm not happy about the way the end of trial results in a fake authorization error, but I'm not going to make a fuss about it. Thanks for clarifying.

I have reported this same problem in a new thread about a week ago and received no reaction whatsoever. Found this old thread and report it again here. What I find: 1. There is an interesting similarity between my problem and what @KillerDog reported: He had 4 timed-out trials and I have one (the Huey). 2. My DCS Log actually shows successful authorization. 3. The other thing that seems weird: the time stamps in the DCS Log end at about 08:31 UTC. However the file was saved at 10:31 (UTC + 1 Hour) which would be 9:31 UTC. I'm located in France and my PC is correctly set to the UTC + 1 time zone. 4. This has been going on for about a week and the error message continues to say that I can still play for 2 days, 23 hours and 59 minutes My layman's conclusion is that the end-of-trial period causes the problem. Maybe I need to uninstall the Huey, but I will wait for instructions. I attach the DCS Log and a screenshot of the error message. dcs.log

1. Why not in "Saved games" structure? These "default.lua" files reside in the Mods structure. Somebody has come up with a smart "Mods injector" that puts the additions into the "Saved games" structure, using complex additions to another file that I don't understand and therefore don't feel comfortable with. 2. Names in the A-10C II and most other modules I remember have the structure you mention, and so I use that structure. If I'm modifying a file for a module using a different structure then I use that structure for additions to that file. But frankly, I cannot rember the last time I used a different structure.

1. the bindings I created, with the exception of "Canopy 2-Pos OPEN/CLOSE" can be used with HOTAS buttons/switches as well as keyboard keys. The commands you want to use with the keyboard must be inserted into the "default.lua" under "...\Mods\aircraft\A-10C_2\Input\A-10C_2\keyboard". 2. I cannot create a single command that toggles between OPEN and CLOSE. As a minimum, you have to use two key bindings. You have some choices, I will explain what each of the following commands do. 2.1 Open only. When you push the bound key, the switch goes to "Open" and the canopy will open all the way: {down = 3007, cockpit_device_id = devices.CPT_MECH, value_down = 1.0, name = _('Canopy OPEN'), category = _('Systems')}, 2.2 Open/Hold. As long as you push the bound key the switch stays in "Open" and the canopy continues to open. As soon as you release the bound key the switch goes to "Hold" and the canopy stops moving: {down = 3007, up = 3007, cockpit_device_id = 39, value_down = 1.0, value_up = 0.0, name = _('Canopy OPEN/HOLD'), category = _('Systems')}, 2.3 Close/Hold. As long as you push the bound key the switch stays in "Close" and the canopy continues to close. As soon as you release the bound key the switch goes to "Hold" and the canopy stops moving: {down = 3006, up = 3007,cockpit_device_id = devices.CPT_MECH, value_down = 0.0, value_up = 0.0, name = _('Canopy CLOSE/HOLD'), category = _('Systems')}, So you can use 2.1 with 2.3 or 2.2 with 2.3. The combination of 2.1 with 2.3 is how the switch in the cockpit works. So that would be my preferred solution. I hope this is clear enough. Hans-Werner

@orbmis Correct. The 2 lines you refer to will work with a "normal" 3-way switch (ON1-OFF-ON2). If neither ON1 nor ON2 is active, then HOLD mode is engaged. Note: The switch in the simulated cockpit is a special 3-position switch. The positions OPEN and HOLD are stable, but the position CLOSE returns to hold when you release it. The airbrake switch on the Warthog throttle behaves like that, but that's already in use. The 2 lines you refer to will also work with this special 3-way switch if you have one to spare.

Thanks guys! I've installed it and it certainly is an improvement in "crispness)". I have only selected curve and sharpen, and I see no drop in FPS.

DCS World is not on the compatibility list. Somebody using it? Does it pas IC? Do you start the program before launching DCS World, or is it running permanently in the background?

Please explain: what's ReShade?

I find the AI wingmen rather stupid, so I'm not really surprised. I have never used the datalink function. Also, if I instruct them to engage ground targets they tend to go after ground targets farther away and do something stupid. What works best for me is to lock a target and then use "Engage my target". Most of the time then they use a Vikhr from a safe distance to kill the target. But quite often they try to engage the target with gun or rockets although they still have most of their Vikhr missiles. So they get far too close to the target area and there is usually something with at least a machine gun that will kill them.

Yes I had to change them because the "CLOSE" didn't work any more. ED changed the object I'm using in "clickabledata.lua".

I don't know ED's plan for fixing this, so I fixed it myself. Updated Canopy bindings are in my tutorial thread: https://forum.dcs.world/topic/270080-lua-editing-for-additional-key-binds-tutorial-no-discussion-here-please/#elControls_4691602_menu It includes bindings for 3 pushbuttons (OPEN, HOLD, CLOSE), a 3-positions switch, and for a 2-position switch OPEN/CLOSE.

Since today, I get the "Authorization failed" pop-up window. I can still play for 3 days, so no immediate urgency. But I have not seen this announced anywhere, so I thought I should report.

I checked both stable and Open Beta, and the command "toggle VR Zoom" is available for all game controllers. If it's greyed out for joysticks etc that would indicate that the following line is missing in the file "default.lua" under "...\Config\Input\UiLayer\joystick": {down = iHeadTrackerZoomToggle , up = iHeadTrackerZoomToggle , value_down = 1.0 , value_up = 0.0 , name = _('toggle VR Zoom' ), category = vr}, You could add it manually, using a program editor like "Notepad++". But the safest method is to run a Repair. I presume that you have not modified that file.

The buttons/switches on throttle and stick generally cannot be operated with the mouse. You need to bind these commands to buttons on your game controllers or use keybord commands. While the flight manual says that you should put the propeller pitch control in manual mode for engine start, I agree with @Ala13_ManOWar that it's not necessary. And if you forget to switch back to Automatic mode at least after take-off, you will kill your engine.

I believe that the behaviour was intentionally programmed. Only a short button press in your scenario prevents a second start-up attempt. Otherwise you can have several engine starts in a mission.

@-0303-I ran your track and it showed what you described. I believe the mission is "Cold Start (and not "Takeoff from ramp"). Also, I can reproduce what you describe in the "Cold Start" mission. After pressing the "Start" button briefly that button no longer has any effect. Whether that's a bug, or just "how the system works", I don't know. But it might be correct behaviour. The button has a protective cover for a reason.

Edit: I had made 2 minor changes to the file "clickabledata.lua" a long time ago. I found that in the meantime ED had made many changes to that file which were not reflected im my modified file. They had also fixed the issues that justified my changes. I restored the stock file and now the engine start works both manually and in auto-start. Especially the wobble pump has become much more effective so I no longer have a problem with fuel pressure. I learned a lot about the Spit's start-up process. But I have to apologize for muddying the water in this thread.

No. This is not like binding a button to a command.