bingbean

I think it would be best if ED reverted all 2.8 changes for Ka-50 and do not touch BS2 anymore and applied all new "features" only for BS3.

Then it's really interesting that it took ED 13 years to correct this mistake. And now 90% of players will use mod that returns it to B&W because they are already used to it.

I probably didn't restart the game or something after i did the change in the lua file, so the change did not take effect. So when i tried it again after re save the mission with ["C-8"]=30, then the different was noticable a lot. For me the default value 3 is not enough so for now i am testing 8 and it looks fine for me.

I did change the ["weapon_missing_mesage"] = true When i shoot guided misille AT-6 it wrote AT-6 is missing, but it doesnt wrote anything when i shoot S-8 rockets. Does it mean the S-8 are included? If yes, then the script does not do too much, because i still need direct hit to damage something. I dont found S-8 in the list, there is only C-8 , C is actually S in azbuka so it is probably the same, but even if i increase the number from 3 to 30 still no difference, so i don't know what is wrong.

Did you figure out haw to do it? I have personally complete steering wheel and i am able to use T3PA pedals as rudder when they are conect in to wheel. In this case all pedals throttle clutch and brake are as separate axis in range 0-100%. In DCS axis setting is possible combine two full 0-100% range axes into one -100% - 100% range axis. You set up X saturation of both axes to 50%, one of them invert and it works. It is nice to have additional buttons available on steering rim, but still it would be more comfortable if i can just connect the pedals in to TWCS throttle. What i actually can, but in this case the throttle and brake pedals are as one axis and clutch is next full axis. I want to use throttle and clutch as rudder so i need in DCS axis setting combine one half axis with one full axis and cant figure out how to do it. Theoretically if i disassemble the pedals and reconnect clutch and brake pedals between each other it would work without any additional setting, but it will messed up setting in my racing games so i won't do that.

Does this work for Mi-24P unguided rockets? I tried it but not notice any difference. From some of posts above is clear, i should be able add some missing weapons myself, but i have no idea how can i do it.

Is any chance we can get AT-2 MCLOS missile? I don't see in gunner seat any joystick for control MCLOS type of missile, so Mi-24P variant of Hind probably can't operate AT-2 MCLOS missile. Anyway, it would be fun to control them. Hitting something would probably be difficult, but all the more satisfying when you succeed.

@LuseKofte After you get the list of targets you select one by short up or down petrovich command, but then you need acknowledge the select by short right command.

The isue of AP heading mode and his full 100% autority is that your phisical rudder (real pedals) and logical rudder (in game pedals) are not same at same position after AP set new trim pedals position. So you can go in to situation when you will have your phisical pedals 100% to the right but in game pedals will be only 70% to the right, however to stop helicopter to spin left you need 80+% right logical rudder input. To prevent this situation you need often manually TRIM pedals or not use TRIM and don't allow AP use TRIM at all. If you have spring centered pedals, and you want to use YAW AP chanel then you have two option. a). microswich logic> Disable by return to Neutral and Pedal TRIM button Y In this set up, microswich will be automatically activated , when you physicals pedals will be out of center position and AP will be in damper mode. When your pedals will be in center position , microswitch will be inactive and AP will be in heading hold mode. When AP in heading hold mode change TRIM of pedals , you can manually retrim pedals by Y buttons. After i tried several different options and even make my own Freepie script, i find out this in game set up works best for me now. b). microswich logic> Automatic MicroSwitch Off and Pedal Trimmer Off In this case you will set up microSwitch for toggle switch on your HOTAS if you have one and keep it in active position all the time, so AP YAW will be only in damper mode. So AP will not have full 100% authority and don't change TRIM position of pedals. You can try another combination , but for now prevent to use Micro Switch Logic: Enable/Disable by absence/presence of pedal movement, because this one is broken and doesn't work as intended. Read the AeriaGlorie AP manual. There is pretty nice discribe how it works in real live and how works diferent option what we have in game.

It is probably still same issue so i post it here. GUV 8700 HMG on pylons 3 and 4. GUV 8700 AP-30 on pylons 2 and 5. Weapons swich in position GM-30. After pressing trigger, FXD MG 12,7 mm is shooting and dont selected AP-30 grenade launcher. When the MG 12.7 mm goes out of ammo, then AP-30 grenade launcher shoot no matter of the weapons switch is in position GM-30 or FXD MG 7,62+12,7 or FXD MG 12,7 mm. guv.trk

I bet you will try it once or twice and then, you will switch back to pilot seat when you want to use canon or unguided rockets, because it is much more easy. I did do that way. By the way, you can turn on small crosshair on front glass in special option. In emergency situation for quick aiming is pretty accurate for short distance.

O.k. thanks. Then i ask different. Can i use your map , to replace incomplete 0.25M raster chart default map? If yes , how? If no, can you ask the devs to use for Mi-24P complete 0.5M raster map until they finish the incomplete 0.25M raster map? I find the 0.5M pretty detailed.

Does the Mi-24P use this map for zoom in scale? If yes , is there a way how can i replace this incomplete useless piece of ××× , with another layer of map what covers all areas?

Not big deal, but it would be more cool, if actually the kord gun can be hidden inside when door is closed.

In changelog is: Fixed: Kord gun is not moving inside when rear cargo bay doors are closed which is quite different than the cargo bay doors being unable to close when the Kord gun is attached.

+1

Made a video was a good ideal. When i was look the track before and notice there the AP goes to heading mode, i was thinking it was by accident because the button problem. But actually you released the pedals microswitch button on purpose. So the problem is not the AP goes in heading mode when he should not, but the auto trim when he is in heading mode. If you wont the AP desynchronize physical and logical pedal position, then the solution is don't use heading mode at all or get some force feedback pedals. If you have mechanical switch what can hold the pedals microswitch on, then there is no reason for you use modified lua file.

It looks like hardware isue. Do you have VKB gladiator NXT, and the microswitch mapped to one of the HAT switch? I like my Gladiator NXT , but those THAT buttons doesn't like press and hold position. I have to push the button really hard to keep it in active position. Probably your joystick have same problen in this case. You did thinking you hold the microswitch buttons all the time, but actually it was not active all the time. Try to map the pedals microswitch for another button on your joystick or use my default.lua file. I did modify input lua file for keyboard. Pressing and release Y key will hold the microswitch in active position. For deactivate pedals microswitch you need press Lshift+Y. The file is located in : ....\DCS World\Mods\aircraft\Mi-24P\Input\Mi_24P_pilot\keyboard default.lua

I accidentally found this topic and start thinking about whether it can be useful in this case as well. And it seems it can. I opened the default.lua file in D:\DCS World\Mods\aircraft\Mi-24P\Input\Mi_24P_pilot\keyboard and found the line {combos = {{key = 'Y'}}, down = autopilot_commands.RudderSignal, up = autopilot_commands.RudderSignal, cockpit_device_id = devices.AUTOPILOT, value_down = 1, value_up = 0, name = _('Autopilot Yaw Channel Rudder Align, button - ON/OFF'),category = {_('Ins Rudder'), _('Flight Control')}}, then i backup the originall line by add -- at the begining and mede a two new lines where i delete the "up" comands and value. Set up for pressed Y key value_down=1, for Y+LShift value_down=0 and it works. --{combos = {{key = 'Y'}}, down = autopilot_commands.RudderSignal, up = autopilot_commands.RudderSignal, cockpit_device_id = devices.AUTOPILOT, value_down = 1, value_up = 0, name = _('Autopilot Yaw Channel Rudder Align, button - ON/OFF'),category = {_('Ins Rudder'), _('Flight Control')}}, {combos = {{key = 'Y'}}, down = autopilot_commands.RudderSignal, cockpit_device_id = devices.AUTOPILOT, value_down = 1, name = _('Autopilot Yaw Channel Rudder Align, button - ON/OFF'),category = {_('Ins Rudder'), _('Flight Control')}}, {combos = {{key = 'Y', reformers = {'LShift'}}}, down = autopilot_commands.RudderSignal, cockpit_device_id = devices.AUTOPILOT, value_down = 0, name = _('Autopilot Yaw Channel Rudder Align, button - ON/OFF'),category = {_('Ins Rudder'), _('Flight Control')}}, What is interesting it doesn't affect rudder trim function if it set up for Y key in special option, what is actually good for me.

It looks like lots of thing was changed after a yers in this case and i am totaly lost in information in this topic. Where are now locate the .lua files where i can edit the combos for specific button? If i want to do some changes for Mi-24P pilot buttons behavior what file need i edit? What i want to do, is change of behavior one button what need to be press and hold to be active, to toggle behavior , so when i press and release the button the action go on and hold, until i press the same button to go the action off. It is even possible?

I meen toggle option as : Press first time it goes on , press second times it goes off. I don't have any switch style "button" on the HOTAS what can be in on or off position all the time. I have only buttons what need to be press and hold to have the button active. There are only few HOTAS on the market that have switches, and they are quite expensive ones.

After some investigation and testing i know describe now what is wrong. 1. "Enable/Disable by absence/presence of pedal movement" mode in “Pedal Micro Switch Logic" does not work es was intended. Instead of simulating pressing and holding the microswitch the entire time the pedals are in motion, the microswitch is pressed and released rapidly. Actually it was wrong even before update 2.7.18.30348 Open Beta. On stable version it is wrong as well , but not so noticeable , because AP doesn't have yet 100% authority there. To fix this issue , there have to be add 1 second delay or so before the microswich is released after the pedals stop to move. "The Disable by return to Neutral" Pedal Micro Switch Logic mode seems to work correct. 2. Second problem is new 100% authority of Yaw AP chanel and how the AP move the pedals and set a new trim position. Since most players do not have pedals with force feedback, AP trimming desynchronize physical (real players pedals position or whatever he use for rudder) and logical (in game pedal position) axis value. What i know lots of people doesn't like to much if physical and logical axis does not match, because of issue of don't have enough authority from logical axis while the physical axis is already at max position. For example : AP move logical axis 30% to the left. My physical axis is still in the center 0% position. Now i come in to situation when i need 80% rudder input to the right. However even if i press my physical axis 100% to the right, the logical in game axis get only 70%, because i was spend already 30% of physical axis to move the logical axis to the center. So in this situations would be nice to have some automatically system what will start relatively increase logical axis, when the physical axis reache max value. The relative increase speed can be the same as i can set up in special option "sensitivity of button controlled pedals". So for now the AP YAW chanel work correct for people who own force feedback pedals with micro switch what is like 0,1% of all players or even less as that. So the question is, if the rest of players who just use spring centered pedals or joystick twist, can get some better solution as stop use Yaw AP chanel or use 3th party software to force pressed Y key if they don't have toggle switch on his HOTAS. Before some more sophisticated solution at least toggle on/off option for Pedal Micro Switch would be good start.

What have actually Micro-Switches does before the last update? What was different if the micro switch was on or off? I just try to figure out why the auto Micro-Switches mode work before and don"t work now.

So far as i remember: Operation medvedev II was withou any issue. Gorgian oil war is similar campain as for Su-25T. You result in each mission influence , what mission you will get next. The problem in this campaign for me was difficulty. For my taste to much AAA units. Because lots of enemy to kill, you will expect some support from AI wingman, but you get any because for my experience Ka-50 AI is most stupid AI in the game. Deploymen - I several missions are enemy unit completely hide in forest. Impossible to kill them , but mostly killing them is request to mission accomplished. So you need open the mission in editor, make some trigger zone to destroy trees in the zone.

There is definitely something strange at the current state. I can't describe what is wrong , but there is not correct something.