LeCuvier

In the mission "Death Valley" which tends to run for an hour or more, I get the triangular shadow every time.

I saw something very similar in the Shkval display in Ka-50 III, in the Caucasus map, in 2.8. No VR. I wanted to report, but could not reproduce it. I suspect it's an artefact of the graphics software that appears under some odd circumstances. Edit: I was just running a mission with the Ka-50 III (Death Valley) and after about an hour into the mission, the phenomenon came back. See attached screenshot. Normally I would have reported this under BS-3, but given the similar posts above I don't believe that it's a BS-3 problem.

The A-10C has a pair of files which have the same function as the "default.lua" but are specific for the two MFD's. They are named "F16 MFD 1.lua" and "F16 MFD 2.lua" respectively. They define which commands are available for left and right MFD resp. The Hornet and Viper don't have that kind of files and are therefore more flexible. You might try to re-name these two files, but I cannot guarantee results (I don't have MFD modules). Even if it works, you will have to repeat that operation after each update or repair, because ED will restore the original files. It might be less trouble to not try to swap the MFD's .

This keybind exists already for the TM Warhog throttle. I suspect you want it for use with a different kind of game controller. ED have disabled the related line of LUA code in the file "default.lua" by adding "--" at the beginning of the line. You could easily enable the line by removing the "--" using Notepad++ It's line 261 in my rig and it currently looks like this: --{down = iCommandPlane_HOTAS_MIC_SwitchUp, up = iCommandPlane_HOTAS_MIC_SwitchOff, name = _('HOTAS MIC Switch Up (no function)'), category = _('HOTAS')}, Notepad++ shows the entire line in green because the "--" comments it out.

@Chaos_Out: Yes, I can do exactly what you describe and use LAlt + ' instead of a bound button,. This brings up the "Mission Ressources" pop-up where I define the loadout I want and hit OK. Then the ground crew acknowledges my request and executes. However, I have to switch the radio to the "GRND" position in order to speak to the ground crew. I don't understand why you "refuse to believe...". This is a simulation, and it simulates how the real thing works. The menu is a game feature that you can use if you want to.

@TAIPAN_How do you know the anti-skid is not working with your added LUA lines? I would not rely on the light in the Caution Light Panel. The related table in the flight manual has a note for this indicator saying "No function". Also, the function defintion for "electrically_held_switch" in "lclickabledata.lua" says that the animation isn't working properly. -- TODO: to check animation, it doesn't work properly with the handling code function electrically_held_switch(hint_, device_, command_on_, command_off_, arg_, animation_speed_) local animation_speed_ = animation_speed_ or anim_speed_default_2_pos_thumb

Sorry, I was obviously on the wrong track. I've deleted my post to avoid unnecessary confusion.

There is a setting in ME where you can choose Auto, HMD or NVG. It seems to be pre-set to Auto in all missions provided by ED and also those the user has created by copying an existing Ka-50 BS-2 mission and changing the chopper to -3. I have no idea by which criteria the Auto decides what to configure. The instant action "Cold start" in Caucasus comes up with NVG, while the one in Nevada comes up with HMD. I copy the instant action missions to Saved Games and set them up the way I like.

The Spitfire (and the Mig-21) has pretty much the same braking system, and my first attempts at taxiing or even landing, using a pedal for the brake axis, were simply disastrous. In the end I managed somehow most of the time, but it's totally counterintuitive. Now I have a Virpil stick with an analogue brake lever and it still feels strange (because I fly the Spit and the Mossie rarely), but it's no problem. If you want to fly any of these birds and have fun, I can only recommend you get a joystick with an analogue brake lever.

Tried to reproduce the issue. I bound the command to a button on my old joystick, and it works. I cannot imagine why it wouldn't work for you. Only explanation I can think of, that you might be trying to re-bind a button that's bound to UI Layer or "General".

I reported this issue for BS-2 and I never found the cause of the issue. It still occurs when I run auto-start in the mission "Death Valley" with the BS-2. However, I made a copy of the mission and switched the helicopter to BS-3. Auto-Start now executes perfectly. As I will not fly the BS-2 going forward, I consider the issue as closed.

I do use a Virpil Stick , the Original Mongoos T-50. But it does not control anything related to engine start. I don’t have access to my rig this week. When I’m back home I will check if I have a duplicate binding on the rotor brake. However this seems unlikely because in my case only one of the engines fails to spool up.

you hit the nail on the head, thanks!

I just completed all the bindings and did my first test flight. It went well, except I cannot get it to hover. In BS-2 I have absolutely no problem with that. In BS III, stabilized and speed down to 5 km/h, AP channels for Pitch, Bank and Heading activated, pushing the "Hover" button has absolutely no effect. Is there a change in the sequence of operation for Hover?

Cannot confirm. The commands are still there and they are working with the AP 3-position switch on the Warthog throttle. The commands are not under "Special for Joystick" but under "Instrument Panel" and "FLCS".

@Flappie: my compliments to the team, they did a sterling job providing almost all the bindings for 2- and 3-position switches. Unlike for the BS-2, I only had to add two lines of code: {down = device_commands.Button_6, up = device_commands.Button_6, value_down = 0, value_up = 1, cockpit_device_id = devices.AUTOPILOT, name = _('Autopilot Altitude Hold Mode 2-Pos BARO/RALT'), category = _('Autopilot Panel')}, {down = device_commands.Button_3, up = device_commands.Button_3, value_down = 0, value_up = 1, cockpit_device_id = devices.NAV_INTERFACE, name = _('Autopilot Desired Heading/Desired Track 2-Pos DH/DT'), category = _('Autopilot Panel')}, They make more sense to me than the 3-position switches provided by ED, because these are not 3-position switches in the cockpit, and, most important, I don't have that many 3-position swiitches in my gear.

Well it's a 2-position switch in the cockpit so we can't really criticize them for providing matching bindings. I understand of course, if you don't have enough 2-position switches you'd be better off if they provided separate ON and OFF commands. They would be easy to create, and if you are willing to edit the "default.lua" I can provide them.

ouch! I did not search for "Directional..."

No luck. I could create new trim commands using information from "clickabledata.lua". But I could not slow the trim "speed" down.

@AeriaGloria: thanks for this information! I didn't realize the WeaponsTable LUA is gone! It seems then that in the process of restructuring the weapons data they have changed the effectiveness of the weapon. When I used it earlier it was a single-hit killer for all IFV's, APC's, Shilkas and the like. Now it's fairly useless.

@AeriaGloria: As far as I know, the destructive power of armour-piercing projectiles is not derived from the mass of explosives alone. The M282 has a penetrator warhead which allows it to penetrate light armour like that of IFV's and create havoc from the inside. So comparing just the mass of explosive neglects a major piece of the equation.

commands like "iCommand..." do not take parameters. I see that the trim commands are available in "clickabledata.lua". It might be possible to create custom commands. I may have time to try later.

@NineLine: I tested, and it's not working. Normally you should be able to switch to the test position either using the CW/CCW vommand, or using the button input for "Test". Both methods fail. This is clearly a bug and should be reported. If somebody really needs this function, e.g. in a sim pit, I found a work-around by creating a new command. This requires a dedicated pushbutton input for the "Test" position. I added the following line of code into the file "default.lua": {down = fuel_commands.FuelQtySelSwTEST, pressed = fuel_commands.FuelQtySelSwTEST, up = fuel_commands.FuelQtySelSwTEST, cockpit_device_id = devices.FUEL_INTERFACE, value_down = 0.1, value_pressed = -0.1, value_up = 0.1, name = _('FUEL QTY SEL Knob - TEST Button Special'), category = {_('Instrument Panel')}}, The new command appears as "FUEL QTY SEL Knob - TEST Button Special" and you need to bind it to a pushbutton or equivalent. This command works in 3 steps. From any switch position, when you depress and hold the pushbutton, the switch will first go to the "Normal" position and then immediately to the "Test" position. This happens so fast that you hardly see the stop at "Normal". When you release the pushbutton, the switch goes to the "Normal" postion. I had to implement this 3-step approach, because there is currently no way to make the switch go directly to "Test".

@Flappie: We are actually talking about two issues: Changing the Elements reference in "clickabledata.lua" to all uppercase allows you to rotate the button in the cockpit with he mouse. The additions to "default.lua" which I posted above provide key bindings so you can operate the knob from a game controller (or the keyboard if you add the lines to the "default.lua" under "...\keyboard"). For full desirable functionality you need both.

I understand you are not a developer, but I suppose an organization like ED has a "suggestions" process. Here are the two lines of code to be added to "default.lua", for use with a pair of pushbuttons or an up/down toggle switch: {pressed = gyromagcompass_commands.F86_CockpitDeviceCommand_Heading_Correction, cockpit_device_id = devices.GYROMAG_COMPASS, value_pressed = 0.005, name = _('Gyro Compass Correction CW for Pushbutton') , category = {_('Instrument Panel')}}, -- for pushbutton {pressed = gyromagcompass_commands.F86_CockpitDeviceCommand_Heading_Correction, cockpit_device_id = devices.GYROMAG_COMPASS, value_pressed = -0.005, name = _('Gyro Compass Correction CCW for Pushbutton') , category = {_('Instrument Panel')}}, -- for pushbutton For a rotary encoder, you need much higher "value_pressed", like this: {pressed = gyromagcompass_commands.F86_CockpitDeviceCommand_Heading_Correction, cockpit_device_id = devices.GYROMAG_COMPASS, value_pressed = 0.03, name = _('Gyro Compass Correction CW for Rotary Encoder') , category = {_('Instrument Panel')}}, --for rotary encoder {pressed = gyromagcompass_commands.F86_CockpitDeviceCommand_Heading_Correction, cockpit_device_id = devices.GYROMAG_COMPASS, value_pressed = -0.03, name = _('Gyro Compass Correction CCW for Rotary Encoder') , category = {_('Instrument Panel')}}, --for rotary encoder