Akiazusa

iirc,u switch to IFA only if there is gps available so the GPS can keep updating ur INS position,since ur mission is in 1989,so no gps in ur mission,u need to keep it in NAV after alignment. But if it initialized as IFA mode for hot/inflight start by default in non-gps era I think that's a bit odd.

Buddy-lasing for another type from ka50 probably won't work, since it's been changed and nobody knows the code(or if it's even a NATO PRF code anymore),I guess buddy-lasing now works only between ka50s. But for now 1113 still works for su25t. If u want an answer from dev about ka50,maybe u can try Ru ka50 sub-forum using a translator,looks like people who actually did the coding sometimes answer questions their.

It has been changed ,1113 won't work anymore.

yes,create one if there is no one mission.miz(actually a zip)\Mods\aircraft(no "s")\Ka-50_3\Cockpit\Scripts\ARK\ARK.lua waiting for ur good news.

Sochi doesn't work for me either,odd...but for some airport it works,(I tried NDB in Maykop-Khanskaya) But if u don't mind modding the game file a bit,I find a way to make the plate displaying things u manually entered. First u need to delete line 152 and line 166 from ARK_MAIN_page.lua,but this file seems can't be packed into the .miz file,so modding the game file is needed. (those 2 controllers seems keeps overriding what u entered from ark.lua using their own logic.) And here is my ARK.lua,u can pack it into the .miz file without touching the original game file. ARK.lua in my ark.lua,u could change the name and callsign(in red circle) to what ever u what and the plate in cockpit will display them. for the beacon_id:(airfilexx_xx or world_xx),u can ignore them,I haven't figure out how to use them yet,and they don't seems affect anything for now To edit ADF frequencies,use mission editor,change them to whatever u want(but no automatic update for the the ADF plate after modding),then u can manually change beacon "name" and "callsign" in my ark.lua to match them(or anything u want to be displayed on the plate) .(also u can try adding more functions to it,or merging those theatres into one section) For Syria,I guess it's not called "syria" for lua variable,as "elseif theatre == 'Syria' then" doesn't work for it,but when I change that to "else",things start working.

On Caucasus and Nevada map looks like if that as long as the NDB is in Beacon.lua,all u have to do is to change the ARK settings in ME to match the frequency in Beacon.lua and the plate will be automatic updated to match their names and callsigns. I tried messing with ark.lua to make it works the same way for Syria but sadly no luck either...............I will try more tomorrow........................ maybe using a kneeboard is easier.

In my memory it's modeled. I think the test button only lower the "protection kicks in" threshold a bit, u still need a relative high power to get that light on(like .in normal operation the light comes on at 100% red line temp,but with test button pushed it comes on at 80% red line temp) I can't find test procedure of it for mi-8 in any manual. But here is the procedure for ka50,which uses a similar engine,I remember on mi-8 it's similar.

Hi. This is a hidden one,trivial thing,nothing really hurt. also I think I find the potential cause of it. There are lots of failures you can set for ka50 using mission editor. But those 2 failures:ABRIS SOFTWARE/ABRIS HARDWARE,seems broken. If u set them in ME,then it won't trigger the failure in game. track.....(I set ABRIS software failure in ME,within 1 min,100% probability,but I guess in the track nothing really happened,the failure is not even displayed in the after mission report) mission editor ABRIS failure settings .trk I checked \DCS World\Mods\aircraft\Ka-50_3\Cockpit\Scripts\Devices_specs\ABRIS.lua and other lua files. Looks like every other failure has an "element" assigned to it,but only those 2 don't have them. I tried adding "elements" to them and things suddenly start working. after adding "elements",abris software failure triggers a blue screen,also hardware failure works too. It works okay in old dcs world version without "element",but I guess some updated new core system changed it,looks like now an "element" is always required? I don't know what exact those element are,(maybe linked to DM? I don't want get a blue screen every time when hit by7.62 bullets) ,so better let the team know and find a suitable fix.(when free of course) Thanks in advance. (sorry for reporting so many things,I guess I'm addicted to this heli recently...fly it a looooot. nice sim product) mission editor ABRIS failure settings .trk

Hi...another small bug,minor detail. ABRIS RMI2 pointer (Red pointer on ACR and HSI page)can show "TO STP" "FROM STP" and "RADIO" information depending on setting. It's default to "RADIO" which shows information from AKR-22 ADF When no ADF signal is received,it will not showing up of course. It works fine if u change the setting with ADF signal being received. Also if u are already in "TO STP' or "FROM STP" mode,and then the ADF signal is gone,the RIM2 pointer will continue working fine. But if u change it's setting from "RADIO" to "TO STP' or "FROM STP" when no ADF signal is received,the RIM2 pointer will not show up,until u have ADF signal being received and got the setting cycled back through "RADIO". RIM2 not showing up.trk Just a minor detail,hope for a fix when free,thanks.

bump Distance to go to STP.trk

Looks like it's 95% mapped with buttons/switches on the real Ka50 stick/collective. The only thing missing is which is a switch on the collective,pretty useful if u want to descend rapidly.(evade radar missile) I guess there aren't many switches on the real ka50's stick/collective to fill up the Warthog HOTAS. I personally uses these panels/switches(which are not on the real ka50 hotas) quite often when flying/combat. also these 2 panels: (especially the 4 blue buttons on the left,also FD button will change the autopilot mode from holding to damping, pretty useful for hand flying,also u can just hold trim button for that,will do the same) (mainly the 5 green buttons,(the reset one is already mentioned in Chuck's guide),and the laser arm switch(u can't always leave it to on,since the laser on ka50 is quite easy to burnt out) ) u could bind the remaining controls to them if u like.

好像没中文的，看英文的吧，，，，其实和1比基本没变，就是HOTAS功能小改，新加的头瞄,雷射指导火箭弹还有个数字电台这几部分不一样，光看这几页就行了。。。。。

A-10C 2出来的时候，老A-10C 和 A-10C 2的HOTAS按键都根据真飞反馈更新了下 这是新的HOTAS功能

Thanks for the addendum. I did some testing tonight,it seems that the in-cockpit altimeter setting in the current dcs build have no effect on the targets saved using LFR,even changing altimeter setting after save,Shkval can still points to the correct altitude when uncage. (iirc u are correct for the build which BS3 was first came out,but it was changed after an update) I guess only LOS line for the ABRIS is taken from the in-cockpit altimeter,and the Shkval is actually using another altitude source as it's altitude reference.(a built-in altimeter which is always set at 760mmHg)

Hi. just to share a simple way to point Shkval at a known target in mountain areas,some of u may already known,but in case u don't 1. A known target,u need to know it's coordinates and elevation(in this case,the target(actually a friendly LAV25)is at 579m) 2.Enter it via PVI-800,as a target point,and select it via PVI-800.(note PVI800 uses Lat Long Decimal Minutes format,u can use LALT+Y to change the coordinates format displayed on the F10 map) 3.check ur local QNH,ur can check briefing in most case,but if the mission is using dynamic weather,u may want to find it urself.(ie.landing on a place which elevation is known,and set cockpit altimeter to match the ground elevation,then the altimeter pressure setting will be ur QNH) 4.use any calculator(u can find a lot via google),input target elevation and QNH(lines), convert them into target QFE (circle) (meter and mmHg is used for ka50) 5.Input the target QFE in ur cockpit altimeter 6.!!!!!!FLY ABOVE 300 METERS AGL!!!!! (VERY IMPORTENT,since when above 300m AGL the yellow Shkval LOS line drawn on the ABRIS will use cockpit altimeter as the altitude reference,when below 300m AGL,radar altimeter reading will be used,u won't want that unless the terrain is perfectly flat,in that case just starting from step7) 7.uncage Shkval,since u can't enter altitude via PVI800,it will point at mean sea level,the target is lined up only horizontally,u need to adjust on vertical direction by urself. 8.focus on the ABRIS,adjust Shkval vertically,until the end of "yellow Shkval LOS line" is merged with the "blue target box",DON'T use laser rangefinder through out the whole process. 9.Bingo.(note the more altitude difference between u and the target,the more accurate it will be,also there will be some heading error due to INS drift) also after u have found the target u can use range finder to make Shkval LOS fixed at it's position.