Bailey

Or you can make your DiCE changes and then in its special options check the box that has DiCE close after DCS starts.

That is unfortunate. Let Hollywood know. I don’t have access to that feature of VAICOM.

Added the DISS computer and a fair amount of front seat stuff. I tried it in MP and it pretty much had everything except for "Fire". Here are some pics of what the profile looks like at the time of this post. Check the first post for the download. I'll also upload it to ED User Files...if I have the time. The position of the buttons roughly represent where they are located in the cockpit relative to one another. Once you use the profile for a bit you may get used to it. If you want to change it up, feel free to do so. Remember: You have to use the Mi-24P.lua for this to work. https://github.com/asherao/DCS-ExportScripts/blob/master/Scripts/DCS-ExportScript/ExportsModules/Mi-24P.lua

I have tried exporting the map to no serious avail. All I got was a 1x2 cm rectangle debug-like overlay in the top left corner and the actual map in the cockpit was broken. Oops. Edit: whatcha using the Stream Deck for when you fly?

Done. https://www.digitalcombatsimulator.com/en/files/3317103/ First post has been updated.

I have seen this phenomenon to be true for years. From my recollection the prevention of runways starts is intentional.

No

You can download the profile here: https://www.digitalcombatsimulator.com/en/files/3317284/ Even though the local file upload in this post was going strong with 40 downloads, the file has become too big to remain in this thread (more than 5MB). A few people have started their Hind DCS-ExportScripts with some difficulty, including myself. A few hours ago Ctytler started investigating a potential problem with the Stream Deck Interface app (https://github.com/charlestytler/streamdeck-dcs-interface/issues/35). The issue has been fixed in the latest Stream Deck Interface App version. https://forums.eagle.ru/topic/230609-new-streamdeck-plugin/page/17/?tab=comments#comment-4719490 Thanks @ctytler! In the meantime I have been making a Mi-24P.lua to include dials and lights. I used the Clickable Data Extract tool (https://github.com/charlestytler/dcs-clickabledata-extract) to make a spreadsheet of the clickable stuff. I then added that to an `Empty-DCS.lua`, renamed it to `Mi-24P.lua` and through shear experimentation started labeling the lights and dials while in ModelViewer. You can see the result here: https://github.com/asherao/DCS-ExportScripts/blob/master/ExportsModules/Mi-24P.lua . I hope that we can get a relatively central place to chat about Mi-24P DCS-Export info. Feel free to add stuff to the git or simply here in the thread. Expect changes. I have so far replicated the Autopilot panel and the Signal Flares on the Stream Deck, the results of which are working well. I took pictures of the buttons ingame, referenced some numbers, and voila, there it was. The rest of my SD profile in still in construction. Liberal use of the Delete key is ok . Remember to put `Mi-24P.lua` in your `Saved Games\DCS\Scripts\DCS-ExportScript\ExportsModules` before you start. Note: DCS-BIOS has quite a number of Hind stuff, much of which I am using for my VoiceAttack profile. If that will satisfy your Stream Deck needs, please feel free to use it. It is a little simpler for simpler needs. Take a look at at DCS-BIOS (https://github.com/DCSFlightpanels/dcs-bios) along with DCS Control (https://forums.eagle.ru/topic/204733-streamdeck-plugin-for-dcs/).

Here is the link for the DCSFlightpanels fork. This DCS-BIOS was updated just 4 hrs ago with more Hind stuff. https://github.com/DCSFlightpanels/dcs-bios

Hello! A few of us Hind'ers are having trouble with getting the ID Lookup working with the Mi-24P. Here is my Export.log when compared to the Mi-8: As you can see, it seems that here is "No module found". @ctytler, do you know what may be causing this or a solution/workaround? (I have a working Mi-24P.lua in ExportsModules, but I don't think that is related to this specific problem. The export file tool worked great btw.) Edit: I see you are already working on it. Thanks! https://github.com/charlestytler/streamdeck-dcs-interface/issues/35

Upload is pending review on ED userfiles.

I do.

Thanks for helping again @Grimes, it is really appreciated.

Caucauses has always had zoom for me. PG and Cyprus have never had zoom in for me. This was observed in at least 5 missions on each map.

Maybe. I'll think about it. Thanks for the idea.

Thanks Dagger. With some more tinkering and some tips from yours, my autostart now has the below: I even have the RWR test beep at me to signal that the autostart is done. And if I miss that, the fans will also tell me visually. First post has been updated.

Karuptsock's method works well, but as you can see is kinda dangerous

This works with a hot start, but I cannot get it working with a cold Autostart. Can you? Any suggestions?

"So you can translate to left/right/forward and give a visual heading turn, but not move backward." I think I saw somewhere that moving/hovering backwards is a prohibited maneuver irl for this aircraft. Interesting.

I have modified my autostart to include weapon systems, lights, and of course, the fans. Here is how I did it. If you just want to file you can download the OvGME Ready .lua here: https://www.digitalcombatsimulator.com/en/files/3317103/ . Remember, this mod will have to be reapplied after DCS updates or repairs. (This guide was created on desktop using dark mode. Apologies for any format errors on your device.) Let's get started with the knowledge. You will need to play with 2 files. 1. Backup and then open ‘DCS World OpenBeta\Mods\aircraft\Mi-24P\Cockpit\Scripts\Macro_sequencies.lua’ with Notepad++. 2. Backup and then open ‘DCS World OpenBeta\Mods\aircraft\Mi-24P\Cockpit\Scripts\clickabledata.lua’ with Notepad++. Let me teach you the basic format of a single command: push_start_command(0.1,{device = devices.ELEC_INTERFACE,action = elec_commands.RectifierLeft, value = 1.0, message = _("VU left"), message_timeout = std_message_timeout}) - Tells DCS that this commands happens in the AutoStart sequence. Don't change this. - This is the duration of the command in seconds. Typically you will see this as 1.0 (1 second) for switches. - The device name. Think of it as like the name of the avionics panel. It will be found in ‘clickabledata.lua’. - The action to be taken on the device. Think of it as which switch to move. It will be found in ‘clickabledata.lua’, directly after the appropriate device name entry. - The value that you want to give the action. Typically, on a two-way switch, 1.0 = on and 0.0 = off. You may have to experiment with this number. - The message that the user will see. - The time the message will remain on screen in seconds. In this case you can see that it is a variable that was defined earlier in the file. Both ‘message’ and ‘message_timeout’ can be omitted if you desire, like this: push_start_command(0.1,{device = devices.ELEC_INTERFACE,action = elec_commands.RectifierLeft, value = 1.0}) Practical Example: I want the autostart to turn on the fan when it is done. Open the two files mentioned at the top of this guide. In ‘clickabledata.lua’ search for “fan”. You should see it around Line 841. Line 842 says something about the Pilot Fan, so we will focus on that one. Because we wanted to turn the fan on at the end of the autostart, search ‘Macro_sequencies.lua’ for “AUTOSTART COMPLETE”. You should see it around Line 169. We will put our custom command at Line 170. Copy a generic ‘push_start_command’, like this one: push_start_command(1.0,{device = devices.AUTOPILOT, action = autopilot_commands.ButtonTon, value = 0.0}) And paste it under Line 169 to make it Line 170. Now refer back to ‘clickabledata.lua’ Line 842. Copy ‘devices.CPT_MECH’ and paste it over ‘devices.AUTOPILOT’ in ‘Macro_sequencies.lua’ Line 170. Then refer back to ‘clickabledata.lua’ Line 842 and copy ‘cockpit_mechanics_commands.Command_CPT_MECH_FAN_PILOT’ and paste it over ‘autopilot_commands.ButtonTon in ‘Macro_sequencies.lua’ Line 170. Now change the ‘value’ to “1.0” (because we want the switch to be turned on) in Line 170. Your ‘Macro_sequencies.lua’ should now have something like this: push_start_command(5.0,{message = _("AUTOSTART COMPLETE"),message_timeout = std_message_timeout}) push_start_command(0.1,{device = devices.CPT_MECH, action = cockpit_mechanics_commands.Command_CPT_MECH_FAN_PILOT, value = 1.0}) Save the ‘Macro_sequencies.lua’ and you are now done. The next time you autostart you should see the fan turn on at the end. Note that ‘Macro_sequencies.lua’ is read on every load into a mission. This means that you can quickly change, adjust, and diagnose these changes in singleplayer. You can put your modifications near the beginning of the Autostart, the end as we did here, or anywhere else you feel brave enough. - All changes I have made are IC safe so you can use them in multiplayer. - If you make a typo you will likely break the autostart. - These files will most likely be overwritten when you update DCS. You can either keep a copy of it somewhere or use OvGme to replace the file after updates. I suggest updating it by hand because ED may change the autostart file. If you blindly update you will be using an older version and may see unintended results. -You can apply this guide to the F-18 and other modules...if you can locate the correct files... I'll leave that as an excersize for you to enjoy. Here is a pic of what a part of my ‘Macro_sequencies.lua’ file looks like. Here is the code I use in ‘Macro_sequencies.lua’ in full: Enjoy!

Oh! That's just as much as my fault. I have corrected the link and text on that thread. Thank you.

Go to DCS Options, Control Options, select the Mi-24P AI Menu dropdown. You will see them there.

Confirmed on one chopper pad on Cyprus. Whoooo! Ok, I confirmed most of the "old" helipads on the mainland. Most of them work enough that I think it is worth it to close this thread and open new ones for unique cases. Thanks Urga!

"Will that change any of my joystick controls if I import them?" Only if your joystick relies on keyboard key presses. The keyboard.diff.lua will only update the keyboard key presses. It looks like you are using version v1.91, but on the userfiles it is version v1.92, as you can see in the picture I posted the other day with the three arrows. Where did you get your version? I dont think the one you have has those commands! Download the newest version here: https://www.digitalcombatsimulator.com/en/files/3308776/

I got it from the hind quick start guide located here: Some things in my kneeboard may be incorrect. Expect revisions.