Akiazusa

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.

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 target 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. 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 altimeter but always set at 760mmhg,the incockpit 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 cockpit altimeter which was affect by QEF knob thus causing all 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 simulated static tube",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.

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.

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.

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.

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.

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.

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.

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

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.

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.

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.

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.