Xtorris

At higher altitude, a bandaid fix for now is: Disengage Autopilot Retrim Reenable Autopilot, AP Vector, AP Altitude Hold, AP Heading Hold, but do not press the AP reference / NWS toggle button. Or just disable AP, and fly by trim. Almost seems like the AP isn't self trimming. *shrug*

For high altitude, it's hosed at the moment. It can even be activated outside of the +/- 200 fpm limit again. The last update mentioned, "WIP" so we'll just need to wait for a fix to be applied. Personally, I'm using this to practice trimming a little more.

No worries then. The functionality just seemed a bit odd.

It's dim during the daytime, and changing instrument brightness only adjusts the (red) backlight. Working as intended, or bug?

He probably meant this:

Disable or remove Bowwave.fx I could load into any base, but I crashed every time loading into a carrier. I hope you have the same luck.

Im able to copy the Lantirn key binds from RIO to Pilot, and use them without issue. Which mod are you referring to?

Oh man! Good times ahead...

https://www.digitalcombatsimulator.com/en/files/3318485/ For information on modifying the cockpit settings via Mission Editor, to your liking, refer to https://docs.google.com/spreadsheets/d/1ay__vxqkxFbvtSQ-CUvN8EoV-OkVHLhwwrI9tGPbt-8 I really enjoy practicing AAR. However, after dozens and dozens of AAR's, I got tired of flipping the pertinent switches for AAR missions. I just wanted to get in and practice AAR in different conditions, so I made these missions. I hope you enjoy it. The scripting of certain tasks, is not an attempt to make AAR easier. The flying and contact is left totally up to you. I just wanted to make multiple AAR practices, less mundane. Pre-configured cockpits via triggers. If you wish, you can edit the values to your liking. NOTE: I could not edit the starting HUD brightness of a few aircraft because the brightness is configured as a button, and not an axis. A-10A, A-10C, A-10CII, F-15C, F-16C, SU-33 Automatic rejoin requesting to the nearby tanker, Tacan channel tuning, and Tacan mode selection. For nighttime refueling, each aircraft had their specific HUD, displays, and gauges dimmed. All aircraft external lights activated All four tanker types: KC-130, KC-135, KC-135MPRS, S-3B 12 Different aircraft types: A-10A, A-10C, A-10CII, AV-8B, F-14A, F-14B, F-15C, F-16C, F-18C, JF-17, M-2000C, SU-33 Straight & level or racetrack tanker orbits. Left side and right side (wingman will be on your left) refueling available on KC-130 and KC-135MRPS tankers. Maps and conditions: Georgia Caucasus, Clear 18 January, 0830 Hours Georgia Caucasus, Poor Visibility 18 January, 1430 Hours Mariana Island, Clear 8 April, 1400 Hours Nevada, Clear 22 August, 1820 Hours Syria, Poor Visibility 26 April, 2245 Hours Persian Gulf, Clear 26 October, 0130 Hours

A small update. By trimming only pitch and roll, but NOT the rudder, I got the DISS-15 update light to illuminate with a pretty high success rate.

I had the EXACT same issue! 1.) Go to \Saved Games\DCS.openbeta\Config\View 2.) Open the file SnapViews.lua 3.) Do a search for the following string, in the SnapViews file: SnapViews["F-14B"] 4.) Scroll down and find (note: your values for [13] may differ slightly from mine): [13] = {--default view viewAngle = 54.000000,--FOV hAngle = 0.000000, vAngle = -3.050000, x_trans = 0.085000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, cockpit_version = 0, 5.) Change the value of viewAngle, so it reads, viewAngle = 85.000000,--FOV 6.) Change the value of vAngle, so it reads, vAngle = -12.0000, Hope this helps. For reference, the clean install values should read: [13] = {--default view viewAngle = 85.000000,--FOV hAngle = 0.000000, vAngle = -12.0000, x_trans = 0.085000, y_trans = 0.000000, z_trans = 0.000000, rollAngle = 0.000000, cockpit_version = 0,

After a few hours of tinkering, I've managed to get the DISS-15 data to map light, to illuminate pretty consistently: 1.) The 'Autopilot Altitude Channel (B)' must be ON. Every time the DISS-15 data to map light illuminated, if I turned off Channel B the light would go out. The light would illuminate again, if I quickly reactivated Channel B. *Yaw, Roll, and Pitch SAS are all ON as well. 2. After takeoff, ensure the Hind is trimmed as well as you can 3.) DISS-15 data to map light has varying degrees of luminosity. I have no clue what the brightness means. DISS-15 signal strength? Accuracy of the DISS-15 data to map? Here's a screenshot from my last flight. I was at full throttle, R/P/Y trimmed out, and had a nice bright DISS-15 data to map light.

Another method, is to hit the 'Trimmer - Reset' button prior to increasing the Throttle Collective and/or Flight Collective.

To make the compass more transparent, find the following lines, in the same file: compass_cross.material compass_base.material compass_scale.material compass_arrow.material compass_marks_white.material compass_marks_yellow.material mode_holder_white.material mode_holder_yellow.material speed_holder_yellow.material speed_holder_white.material alt_holder_yellow.material alt_holder_white.material course_holder_white.material The final 255 in each line respresents the alpha, so a lower value will make the objecti more transparent. 255,255,255,255 Example: compass_cross.material = MakeMaterial("Mods/aircraft/Mi-24P/Textures/ai_compass_cross.dds",{255,255,255,050}) If you don't feel like sifting through the file, and changing all of the alphas, I included a modded LUA with the above alpha values set to 50. HelperAI_page_common.lua Screenshot for comparison: Modded (left) vs. Default (right)

Go to the folder: \DCS World OpenBeta\Mods\aircraft\Mi-24P\Cockpit\Scripts\HelperAI Open: HelperAI_indicator.lua Find the highlighted line: For compass_pos = {0, -0.45}, the '0' is X and the '-0.45' is Y Example: {-0.15, -0.55} is left and lower than default Whereas {0.20, -0.25} is right and higher than default Try it out, and see what value(s) work for you.

The blue highlight will turnoff the RWR (no alarm, no lights on the RWR dial). The red highlight will simply silence the alarm.

Good point!

Another way, is adding in -- so (it nils the argument, which removes any country restrictions) countries = {"UKR","GRG","RUS",} becomes --countries = {"UKR","GRG","RUS",} Some livery files have the countries argument like this: countries = { "UKR", } I just change them, so they all have: --countries = {"USA", "RUS", "FRA", "UKR", "SPN", "NETH", "TUR", "BEL", "GER", "NOR", "CAN", "DEN", "UK", "GRG", "ISR", "ABH", "RSO"}

The UN livery has the following country restriction: countries = {"UKR","GRG","RUS",} Two options: 1.) Add Russia, or Ukraine, or Georgia to the blue side, in the mission. 2.) Download a livery unlocker. Specifically one that includes the Mi-24, to remove the country restrictions.

Clearly the right man, for the job:

I have no idea, if these settings will require any tuning by individual players (hopefully they won't), but I figured I would share these settings anyways 1.) First and foremost, open the default.lua file found in: \DCS World OpenBeta\Mods\aircraft\Mi-24P\Input\Mi_24P_pilot\joystick 2.) Make a backup copy of the default.lua, if you are not comfortable with editing these files 3.) Paste the following lines AFTER join(res.axisCommands, { --Seacrch & Rescue Light {action=ext_lights_commands.HeadLightPilotControl_EXT, cockpit_device_id=devices.EXT_LIGHTS_SYSTEM, name=_('Headlight Up/Down')}, {action=ext_lights_commands.HeadLightPilotControl, cockpit_device_id=devices.EXT_LIGHTS_SYSTEM, name=_('Headlight Left/Right')}, 4.) Save the default.lua file 5.) Load DCS and go to Options -> Controls -> Mi-24P Pilot -> Click the "Assign Axis" button, and you should see a new axis named Headlight Left/Right, and another named Headlight Up/Down 6.) Assign your desired axes. 7.) Both of the new axes will require specific customization, for the search light to respond properly to axis commands. Edit them via the Axis Tune button: Left/Right axis settings Up/Down axis settings Once you are done editing the axes, load into a hot start Hind Mission (preferably a nighttime one), and check the searchlights response to your inputs. ***A few notes*** 1.) If you need to 'invert' either of the axes DO NOT USE INVERT! You will have to swap the numbers around. The deadzones remain unmodified. Only swap the non-deadzone numbers. For Up/Down: 54 = Up 60 = Down 50 = Deadzone For Left/Right 63 = Left 69 = Right 73 = Deadzone 2.) The axis only responds to one input at a time. i.e. left, right, up, down is ok, but the light tends to become unresponsive by combining more than one direction.

The default bindings only defined a "down" action, but not an "up" one. This is what caused the buttons to remain depressed. If you are comfortable with editing the default.lua in the joystick and/or keyboard folder, you can add these lines to the files, and the stabilize / off buttons will now release when you release the key. {down = autopilot_commands.SpeedOn, up = autopilot_commands.SpeedOn, cockpit_device_id = devices.AUTOPILOT, value_down = 1 ,value_up = -1, name = _('Autopilot Speed Stabilize On'), category = {_('Autopilot (SAU-V24)')}}, {down = autopilot_commands.SpeedOff, up = autopilot_commands.SpeedOff, cockpit_device_id = devices.AUTOPILOT, value_down = 1 ,value_up = -1, name = _('Autopilot Speed Stabilize Off'), category = {_('Autopilot (SAU-V24)')}},

1.) Go to \DCS World OpenBeta\Mods\aircraft\Mi-24P\Cockpit\Scripts 2.) Open mainpanel_init.lua 3.) Copy/paste the lines below, and add them to the bottom of the LUA file: args_initial_state = { } local hideStick = get_option_value("difficulty.hideStick","local") if hideStick then args_initial_state[974] = 1.0 end need_to_be_closed = true