Akiazusa

No,I think it's based on missions. Some missions may have your default device set to NVG.It could be changed by the mission creator.

Thank you!

Привет. АЛМАЗ не считывает «Опасность вибрация двигателя» (есть только «СМОТРИ ЭКРАН»), даже если переключатель «ВКЛ – АВАР» установлен в положение «АВАР». Это правильно? Опасность вибрация двигателя.trk

The A-10C II development including bug fixes basically got frozen just a few months after the initial release due to lack of development resource.And the development just continued recently in the late 2022. The A-10C was my favorite model before the A-10C II got released,because it was development for military training,and the level of system completion/detail/damage model is well above the F18 ,F16 and most other dcs models. But a lot of things just got messed up with the update,also some of the features got buggy out or removed with the update(such as engine hung start,and the reverse clearing for the GAU-8, the click logic of a lot of switches also got messed up and only got fixed recently) What I am afraid is the same thing also happens to the BS3. Especially after they announced that the Chinook is on the way to DCS,so the Heli team of ED needs to take care of the Apache,the Mi-24,the BS3,the Chinook,and the muti-crew of Mi8,and fixes for long standing bugs on the Mi8 and Huey. The Apache just recieved the MTT feature recently,and it works the same way as the Ka50. Only object lock,no contrast lock,and can't lock on objects like tress. If they could just adjust the magic object lock system range more reasonable(not a obvious big object sitting above 20km on a flat open ground and you have no way to lock on it),then make it affect by tress.I would be pretty happy to be honest.

What kind of stick trimmer mode are you using? It is under aircraft special options tab where you select your cockpit language. The helicopter trimming mechanism will change the joystick nature position when trimming,so it is not suitable for most flight sim joystick,where there is a spring to push the joystick to the only nature position. There are some in-game solutions, aka "stick trimmer mode" If you are using the default instant trim mode,when you push and release the trimming button,the last position of your in-game virtual stick will become the nature position of your physical joystick. So if you don't what that sudden pitch/roll when trimming,you need to immediately return your physical joystick back to the nature position right after you releasing the trimming button.If you don't do this,the nature position will change to your last input value and you are still inputting the same pitch/roll command, your input will be doubled. If you are using the central position trimming mode,most thing is still the same as instant trim mode,but after your trimming button is released,your joystick will ignore any further input until your physical joystick return to nature. This can help you avoid that sudden pitch/roll jump.But the problem is if you don't return it to center,everything will be ignored,sometimes may lead to crash when you are flying NOE And there is also another option so you can remove your spring on the joystick and make it works like the real heli cyclic stick. Also something specific to the Ka50 (and maybe also the Apache),on the Ka50,the trimming is linked to autopilot/SAS system,when you releasing the trim button,it will change the "attitude/heading/speedauto-hover position" reference of autopilot holding functions to your aircraft current "attitude/heading/speed/auto-hover position". If you forget to turn off some of the holding system,(auto-hover in most cases),after you release the trimming button,you input a new hover position right below you,if you are moving forward then, the autopilot may pitch up to counter that forward movement. Hope these can help.

Hi,just trying to help. Based on my personal observation. I think the FBW pitch will change from ground logic to flight logic when the noise wheel is lift off. When the FBW is in ground logic,it'is very sensitive,the control surfaces will reach their full limit even with just a very small control input. So before the noise wheel is lift off,you pull the control back a little,but the FBW in ground logic will deflect control surface to their full limit. As a result,the initial rotation rate will be very high if you pull the stick too late above the calculated VR. And this may surprise you, so you may push the stick. After the FBW change to the flight logic,it will try to maintain your AOA,so it will automatically adjust the control surface to hold your initial rotation attitude if you just keep your stick there. If you push the stick too much now,it will be FBW command correction plus your manual correction,double correction,then you are doomed... TL/DR 1.The FBW will change from ground logic to flight logic when the noise wheel is lift off, in the ground logic the control is very sensitive 2. rotate at the right rotation speed,too late is not good,the initial rotation rate could be very high if you rotate above Vr, 3.after noise wheel is lift off,just hold your control stick their,only make tiny correction,don't push the stick too much if the rotation rate surprise you,the FBW will handle that as soon as it switch to the flight logic

If you change the cockpit language to Ru and read the label,then you will find identical switch/advisory light in the DCS Mi8 manual

Yeah. On the Shark there are things simulated/polished in a depth well above other models,but at the same time there are also a lot of things not working at all or really buggy. But I really love the Shark because it's the only one man attack heli,so I don't have to deal with those desync issues and the annoying AI,I can have control of everything in the cockpit.. I really hope they can finish this model and polish it well.

The game manual doesn't include this,so we don't know... I remember someone from the ED team on Ru forum saying that the PVI800 don't use DTC to upload things,so it should be more like the INS on the Mirage and Tomcat(instead of the A-10C F16 or F18 on which the initial position was read directly from DTC,but you can still change it manually if you wish to) On the Mirage or the Tomcat it is manually input by pilot. But that's just my personal guess,only the Dev knows the answer.

It would be wired if we can only input initial position by that way IRL. Maybe it's still Wip?

Sorry for that.. I though he post the performance document made by Russian intelligence at the beginning.. Someone posted that a lot of times on Razbam discord..

I hope ED could move the alignment settings from mission editor to "the aircraft special options",so we could choose the alignment style we like in any MP mission... But regarding to settings like this,DCS now focuses too much on PvP balance these days.

Oh come on,we can only carry 2 fox1 and a cannon with only 125 rounds, and u still think this jet is op as hell and need a nerf? This is not that forum that you can upload anything on it. And I can say that China was also plan to buy Mirage 2000 in the 80s and send pilot to test flied it many times, there are interviews from them saying the jet performance was superb on Chinese media. But they didn't have enough money to buy it.

When I try to change the SELF COOR on the PVI800,it will always revert back to the value before editing. The INIT PNT is changeable,but it seems that it has no effect on INS alignment. So I can't find a way to land,turn off the INS,put into correct coordinate and realign it to the right position. Have anyone figured this out?

I think it's okay,because those defense systems are always classified. And I think all those modern DCS aircraft (such as the Apache) are using the defense systems have at least some of the features based on assumptions from dev team. And people only criticize the Ka50 for this. Maybe because of some rumors on the forum that says that Russian bought the ABRIS from a Finnish civilian company as a big NS430 so there was no way it could be integrate into it. But the Finnish civilian company "Transas" was still a Russian company at the time Ka50 was still under development.Also the datalink system is linked to it... For the sling load thing,besides those switches,there is also also an advisory light about it. (please don't remove those clickable switches.......even if you have already removed the sling load feature )

@Flappie Hi,I just find more info on this(an old video) ,any chance to take a look at this again? Would be appreciated.

Hi Flappie,thank you for the hlep Sorry for the late reply,here are my tracks Ka50 HUD fail.trk Ka50 AGB oil pressure via turbo gear.trk Ka50 AGB oil pressure via autorotation landing.trk

I searched the RU forum,some one asked the same question back in 2008. And Chizh from ED team answered it is implemented.I guess this part of the manual haven't received any update since BS1.... IKV heating>>>>>ОБОГРЕВ ИКВ>>>>INU heater

Dear Dev team. I have some problems related to some of the Overhead Panel Warning and Advisory Lamps 1.There are 2 identical "SHKVAL FAIL" lights on the panel now in the sim. From the manual I believe the "SHKVAL FAIL" light which is more to the left is not correct,maybe the texture got messed up. It should be "HMD FAIL" instead of "SHKVAL FAIL" 2. The manual says that the "HUD NOT READY (yellow)" light should lit up in case of HUD failure or not ready,but now it only lits up when the HUD is not ready at initial power up. When the HUD is damaged by enemy gunfire, this warning light never shows up. 3.In the manual,it also says that the "AGB OIL PRESS" indidates "Normal oil pressure in the gearbox with stop valves closed." If it means "Normal oil pressure in the Accessory Gearbox with engine stop valves closed." Then it should lit up if you are powering the Accessory Gear Box via turbo gear.But it won't lit up by doing that in the sim. If it means "Normal oil pressure in the Main/Accessory Gearbox with engine and APU stop valves closed. I tried achieving this by doing a autorotation landing.And still,it won't lit up. Asides from the 2 identical "SHKVAL FAIL" which must be a bug,I really hope you can cross check the remaining 2 problems with your real manual and the game manual.They might be correct as it is,but they really just don't works as what your game manual states. Thanks.

Don't forget the PRED switch on the VTH(HUD) control panel,if you turn it on,the FCR will double box the "target square" when it thinks u should fire,which will help a lot. The gunsight on the Mirage is not that old like WW2 plane,it is similar to "SNAP sight" on the older F-16(what we have in our F16 is the latest "EEGS sight")

Hi, I did some additional tests... But the result is odd to me......... It seems that when you saving the target point via DL,it compares the difference/Delta1 between the aircraft INU position and the Shkval aiming point on ABIRS(the yellow leg),then adds this difference/Deta1 to the aircraft ABRIS/GPS position to create a new target point. And when uncaging the Shkval,it compares the difference/Delta2 between the aircraft INU position and the target point position,then adds this difference/Delta2 to the aircraft ABRIS/GPS position to create a Shkval aiming point,then steers the Shkval to it.... It could explain why there is a 2 km shorter in distance,but it makes no sense to me to be honest..... Also if the target point is crated via PVI800 keyboard,the Shkval will just points to the 0 ASL now, it could be pretty hard to find targets via coordinate if there is no way to input target altitude,especially when your mission is in high elevation area. I also wonder how the system knows the exact altitude of my aircraft.Even if I turn off the ABRIS/GPS,it can still points to an elevation of 0 ASL,and changing the weather settings doesn't affect it neither.

(please ignore this...I accidentally post the same reply twice..)

I have a feeling that this position difference is not due to INS position drift,but because of INS heading drift. It seems that when the system record the target heading,it is using the heading output from the INU, but when it turns the Shkval,it won't use the same heading source. I tried a few times and the system just simply turns that aircraft to the REAL heading of the recorded INU heading no matter how wrong the INS heading have already been messed up. For example,when saving target it records a target at 5km in a wrong drifted heading of 78°(but the target is actually at 5km in a real heading of 76°),then you uncage the Shkval,the Shkval will try to point to a position at 5km in the REAL heading of 78° As a result,any difference between the INU heading and real aircraft heading can make the Shkval pointing to a different position. You could intentionally input a wrong heading to the INU(by messing the MH/gyro/MAN switch),then save a data link target and see the result. By the way anyone noticed the target point elevation is no longer effect by altimeter setting after the update?

I think you can check whether DISS is ready by the Ground Speed readout on the HUD If the GS is displayed on the HUD,the DISS is ready If the GS line is blank(I mean real blank,not read out is 0),the DISS is not ready

ERKAN ALMAZ Despite there are tons of EKRAN/ALMAZ messages in the game file,not all of them are working right now,some of them seems only to be placeholders.