[small issue.....Mission editor,ABRIS SOFTWARE/HARDWARE failure not working.(and potential cause)]

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

[ABRIS RMI2 pointer not showing up]

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.

[ABRIS "Distance to go to STP" and "Cross track error" are in the wrong format when large value is displayed causing symbol overlap]

bump

Distance to go to STP.trk

[Question on Chuck's guide controller setup]

Looks like it's 95% mapped with buttons/switches on the real Ka50 stick/collective.

The only thing missing is

Quote

ADJ FREE–TUR” Control selector for re-adjustment of the free-turbine (rotors) RPM governor. To low [RAlt + Numpad -] and to nominal [RAlt + Numpad +].

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.

Quote

“MAN-AUTO” (Manual/Auto weapon control switch). Placing this switch in the up "MAN" position commands manual weapon and sensor control, and placing the switch in the down "AUTO" position commands automatic control. When in manual mode, computed launch authorization, automated gate tracking size, and vertical compensation Vikhr launcher to target are absent. You should only use the manual mode when the automatic mode is inoperative. [A]   (below Master Arm switch,let u override FCS launch authorization,so u can launch ATGM slightly out the FCS calculated range,u can usually launch it about 0.5km out range,it can still reach the target,pretty useful against SAMs like sa15 or tunguska )

Quote

Laser designator reset button   (reset LA,below HSI,personally I push it a lot since the laser on ka50 is quite easy to burnt out)

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.

[关于猪杆某些按键在游戏中不起作用的问题困扰求助]

4 hours ago, cityparker said:

感谢大佬答疑，懂了！！顺便请问，哪里有A10c2的中文手册下载

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

[关于猪杆某些按键在游戏中不起作用的问题困扰求助]

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

[A simple way to point Shkval at a known target in mountain areas]

8 hours ago, LorenLuke said:

Just a quick addendum to note that if one saves targets via a mix of methods (both keypad entry and via shkval), any targets saved using the shkval and laser rangefinder will have their altitudes shifted as well, so if you go to engage those targets, be sure that your altitude is set to the same value when you stored the targets before caging the sensor to engage.

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)

[A simple way to point Shkval at a known target in mountain areas]

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.

[Shkval system altitude which pulled from static tube is not affected by atmospheric pressure change (it was affected in BS2)]

Hi

 in the current version of the dcs,Shkval seems always know the aircraft altitude perfectly,thus whether change have 0 effect on it,when uncaging it to the targets which are input manually it,it can always aways points perfectly at sea level regardless of whether pressure change.Looks like the "system altitude" for Shkval is pulled directly from game engine,instead of anywhere else.

Here are the tracks for current version

740mmhg.trk780mmhg.trk

 

But back in the old version of black shark 2,Shkval calculates it's "system altitude" from static tube which acts like another altimeter but always set at 760mmhg(the incockpit altimeter setting have no effect on it),so the change of whether pressure will have an effect on Shkval "system altitude" calculation accuracy,thus make it points slightly higher/lower than the sea level as a result.

Here are some tracks test using DCS 2.5.3.24984(the version was kept to support VEAO hawk,BS2 was stable and no new BS3 things in it)

740mmhg2.5.3.24984.trk760mmhg2.5.3.24984.trk780mmhg2.5.3.24984.trk

 

Here is also a video showing the difference between them.

（all caused by atmospheric pressure change,not in-cockpit altimeter setting,I didn't touch in-cockpit altimeter setting in the testing)

https://youtu.be/fPxbuzY8-co

 

I also tried set mission time to 1900(no GPS time),mess up INS and K401 gyro,test in when hovering in mountain area(so radar alt won't match baro alt),it seems it can always points perfectly to the sea level no matter what I do. looks like it pulled the aircraft altitude directly from the game engine. instead of static tube (or GNSS, radar altimeter,INS ,or whatever it is)

 

It seems was caused by this fix:

(Don't get me wrong I don't mean it should point to the target altitude set by QFE knob,or u can enter target altitude in PVI-800 )

I just mean

1. in the old old BS2,the system altitude was pulled from static tube,which is another built-in altimeter but always set at 760mmhg,the in-cockpit altimeter setting have no effect on it

2.when the above datalink bug appears(during bs3 update),there was a mis-implementation where the the system altitude was pulled from in-cockpit altimeter which was affect by QEF knob thus causing all kinds of problems.

3.when the fix for the above bug was applied,the system altitude for some reason now seems is read directly from the game engine,instead of "the built-in altimeter",it also doesn't looks like was read from any other sensors.

(if the BS2 behavior were restored,u still have to find the enemy vertically by yourself,just like what it is now)

 

I really like the simulation of BS3,this thing is not a big deal,but just feels really odd.......hope the team could take a look

thanks.

 

[Bullet Impacts on glass]

 

Looks like the textures of damaged glass are already in the game now,maybe just needs some coding to have them set up for the damage model.

[ABRIS before 1994 (no GNSS) question]

It works like a more advanced NS430,so GNSS is required,it talk and exchange some data from some aircraft systems,but mainly datalink and combat stuff,sadly I guess INS position is not one of them.

The best thing u can do is set ABRIS heading from true to mag in the option page,so it still shows ur heading on it.  correction:ABRIS true heading is from Doppler Nav System,doesn't require GNSS,if DNS fails it will revert using flight gyro(HSI heading)

 

[ABRIS,changing fuel quanity on MENU/PLAN/EDIT/FUEL page doesn't update fuel quantity on MENU/PLAN page and NAV FPL page]

Hi,I noticed that the ABRIS FUEL quanity displayed on the MENU/PLAN page,NAV/FPL page and NAV/SEARCH/INFO page doesn't get updated or match what I manually entered on the MENU/PLAN/EDIT/FUEL page.(They don't match fuel meter either)

Fuel quanity I entered:

What they showed in MENU/PLAN page,NAV/FPL page and NAV/SEARCH/INFO page.(after save and re-activating the new flight plan)

(updated title,content and re-uploaded the track because after more testing I find I made some mistake previously.I guess all the things in the previous long post are related to this one.)

Ka50 ABRIS NAV FPL FUEL REM.trk

Thank you in advance.

[Latest Update Broke Ka-50's Hover Mode]

Maybe the auto startup starts up the plane so quickly and the doppler nav device can't have enough time to warm up? IIRC when using fast alignment some nav datas are actually not provided by INS but by doppler nav system.  So without doppler the nav system will fall back using air data to provide nav information,and some functions will be degraded.

[How to input INS initial positon before alignment]

I recently noticed that if u do a pos fix before turning on the INS,u can change the SELF COOR to any position in the world,but in flight u can only do a pos fix within a certain range to the fix point(18km maybe?). So with this logic all things make sense to me now,just do a pos fix before turning on the INS powe...maybe a east and west design difference.

[Rear panel backlights not working]

Hi, in a night mission,I noticed the backlights for the rear panel seems not working.

(I mean this switch and knob by the way) 

No matter how I adjust the knob or turn the switch,it always looks like this,only the WCS BIT lights up in the dark.

 

I searched some videos online and I think maybe it should look like this when it's turned on?(pic from old BS2 video)

 

Here is a short track.Ka50 back panel lights.trk

 

Also here are my graphics settings in case if they are useful.

 

This one may cause some headaches for cold start during night,hope for a fix.

Thank you.

[ABRIS VNAV cue only works when waypoints are added by mission editor]

I guess I'm not the only one who got confused a lot when trying to use vertical navigation VNAV on the shark.

It seems that the VNAV cue which is circled in the pic above,only wokrs when the waypoints are created using mission editor.

If the waypoints are created in game using ABRIS itself,the VNAV cue will never follow the VNAV plan u created,it will just stay(guide u) to the aircraft spawn altitude. Or if u use the ABRIS in game to change the VNAV altitude of waypoints which u created using mission editor,the VNAV cue will still follow the plan created by ME and will not affect by the changes u made on ABRIS.

2 tracks:

The first one,waypoint is created using ME at 500m,and the VNAV cue guided the aircraft passing it at 500m as expected.

Ka50 VNAV using Mission editor.trk

The second one,waypoint is created using ABRIS at 500m,and a VNAV plan is created using ABRIS,but the VNAV cue didn't follow the VNAV plan,and keep guiding the aircraft to the ground.

Ka50 VNAV without using Mission editor.trk

 

 

Not really a big deal,but since all other functions of VNAV pages and supages are all working as expected,only this VNAV cue on NAV page/ARC page/HSI page is not working.so anychance for a fix when there are free time? Thanks.

Ka50 VNAV without using Mission editor.trk

[PCM indication boxed on the VTB]

It's known,and the fix file should be already on ed's hand 2 month ago,it's actually a new feature,which should show a red PCM on radar screen when ECM is working ,but sadly ed only pushed parts of the new files in the last update,causing the problem,according to the discord.

["PCM" in radar since latest patch]

It's known,and the fix file should be already on ed's hand 2 month ago,it's actually a new feature,which should show a red PCM on radar screen when ECM is working ,but sadly ed only pushed parts of the new files in the last update,causing the problem,according to the discord.

[Pickle and canon trigger]

IIRC that might be some leftover things from the old version of the Mirage,where due to lack of classified info,something was implemented not as accurately as the current version,and they got updated/fixed/reworked after the collaboration between the Razbam and the French Airforce

As razo said,binding the MICRoB trigger second stage is already enough. you can also bind the first stage if you what to use the virtual gun tracers.

Other triggers are not used,just leftover bindings,they don't have functions.

[MAIN CAMPAIGN Critical errors in caution panel and poor maneuverability]

Might because of the cold weather in the CAMPAIGN mission,try turning on the pitot heat,giving it sometime to warm up,finally resetting the FBW by the reset switch,it should fix the problem. (If you set up a cold weather in the free flight mode,you will most likely end up in the same situation.)

 

Also check whether your dcs world is up-to-date,there was a bug in the previous version of the mirage causing problem during crosswind take off,but it should be fixed already.

[Nosewheelsteering Fck-Ip]

I think this bug has already been fixed in the last update...... I can take off with 25kts(the crosswind limit of m-2000c) crosswind now with no problem.

It has already been fixed,but just not mentioned in the game change log.

Also I think the reason of Mirage 2000 is still getting update after the mess is because

Spoiler

the developer behind it is also a Mirage 2000 lover and gamer who loves and flies his own baby.

 

[Trackir will not work with the Mirage]

Have you checked these in your Axis Assign settings? Make sure they are assigned correctly.

 

Or maybe you can try deleting the M-2000C folder in C:\Users\username\Saved Games\DCS.openbeta\Config\Input then run the game,let the game recreate one(which should reset all input settings related to Mirage back to default),and see if it fix the problem.

[Trackir will not work with the Mirage]

Maybe try doing a repair? I'm playing the Mirage on 2.9.7.59263 and TrackIR works fine on my computer.

[QRA ? Alert Network ? Scramble ?]

16 hours ago, virgo47 said:

I don't see any more current QRA-specific topic, so I'll revive this.

During the cold start, I clicked this switch, it went up, all the cockpit stuff went off like there is no battery - and the switch is stuck there and I can't click it back to down.

Is it normal?

If the GPU is connected,some systems which are powered by the QRA bus will still be powered after after you clicking this switch(like the INS system for example).

Since it's a new feature been added recently,there is little info about it in the game manual,I'm not sure if it's normal for the can't clicking it back part,maybe there is a safety lock or something,but if you start the engine then(QRA style start up),that switch will jump back automatically and your electric power will be restored,the INS will be ready since there is no need to realignment, and you are good to go.

 

[A problem with the radar]

On 7/3/2024 at 11:49 PM, Silent Film said:

sometimes there is like two-three times more chevrons than the aircraft

This is because when the radar of the Mirage is scanning with 2 bars and 4 bars selected,those bars are actually overlapping each other a bit,the overlap of different bars can lead to duplicated contacts. You can use 1 bar search to avoid this.