lmp

They are available for Poland, each with two skins.

I don't think it is written anywhere and it didn't work like that earlier but it used to be like that in the original Black Shark release (don't know if it changed since) which gave me the idea to try it. It does make sense if you think about it, them engines are loud.

There are several ways to do this. I flip the RADIO/ICS switch to ICS and use the ALT + \ menu. The SPU-7 intercom system is described in detail on page 108 of the manual, I recommend reading up on it.

I'm not 100% sure but I think you have to talk to them over the interphone after the engines are started.

Did Iran ever use the MiG-23? Any version at all?

Interesting points, I haven't thought of switching to TLG mode. To the best of my understanding the TLG setting should be the equivalent of BFO mode?

I can't get the ADF ammeter to display any current. From what I understand I should be seeing a current when the ADF is tuned to an NDB, but it's always stuck at 0.

In Russia they (used to) give you QFE rather QNH and meters instead of feet: http://www.fly-corporate.com/flying-russia-heres-what-you-need-know/ https://ops.group/blog/big-change-russia-finally-moving-to-qnh/ The ATC needs work but in this regard it's not a FUBAR.

If he wants to blow stuff up, F-15. If he is ONLY interested in flying, you might want to consider - and I'm surprised to be saying this - the Yak-52. I'm generally not of the opinion that you should start out with a trainer (you should start out with something cool that'll not bore you) but in this case the slow speed and the pleasant handling characteristics of the Yak really help. My 9 year old landed it after not even coming close in any of the jets cause things were happening just too quickly. Or he could get one of the civilian sims and learn the basic Cessna. That'll work too.

It's interesting we've been given almost no info up until release pretty much.

I typically don't have buttons to spare on my HOTAS. I'd prefer a solution which addresses the problem rather than works around it. Perhaps making the menu more transparent or allowing players to choose between several styles?

Hi, I did a quick search and surprisingly couldn't find anybody mentioning it. The radial menu looks nifty and all, but isn't anyone bothered by the fact that it covers so much of the screen? Right now I can, say, tell my wingman to cover me without losing sight of the banding I'm trying to follow. The comms menu is small, in the corner of the screen and generally not getting in the way of anything. The Jester menu will practically guarantee losing sight of your target.

No problem. Thank YOU for matching all those numbers to functions. I wasn't looking forward to doing it myself ;). To be honest, I haven't tried the last bit yet (adding an aircraft to the AircraftList.lua list) but I have made it work with the Mi-8 and L-39ZA, as in my example. There's one other bit of experience I can share that might be helpful to you or somebody else. I haven't yet tested all the buttons, but I used the FPL button for my initial tests. When I mapped it like this in my Arduino sketch: DcsBios::Switch2Pos fpl("NS430_FPL", 2); It clicked in game on the button press and again on the button release. I fixed it by mapping it like this instead: DcsBios::ActionButton fpl("NS430_FPL", "TOGGLE", 2); This way it only registers once in the game. Also a small delay (50 - 100ms) between the DcsBios::loop(); calls seems to be needed to debounce tact switches. I don't believe the DCS BIOS Arduino library has any "built in" debouncing? Sorry if this is basic stuff to you, I only started playing with DCS BIOS yesterday evening ;).

Thanks for the list Capt Zeen. For anybody who wants to use the NS430 in more than one aircraft, it might be worth it to put those commands in a separate DCS BIOS module, like this: NS430.lua BIOS.protocol.beginModule("NS430", 0x5400) BIOS.protocol.setExportModuleAircrafts({"Mi-8MT", "L-39ZA"}) local documentation = moduleBeingDefined.documentation local document = BIOS.util.document local parse_indication = BIOS.util.parse_indication local defineFloat = BIOS.util.defineFloat local defineIndicatorLight = BIOS.util.defineIndicatorLight local definePushButton = BIOS.util.definePushButton local definePotentiometer = BIOS.util.definePotentiometer local defineRotary = BIOS.util.defineRotary local defineSetCommandTumb = BIOS.util.defineSetCommandTumb local defineTumb = BIOS.util.defineTumb local defineToggleSwitch = BIOS.util.defineToggleSwitch local defineToggleSwitchToggleOnly = BIOS.util.defineToggleSwitchToggleOnly local defineFixedStepTumb = BIOS.util.defineFixedStepTumb local defineFixedStepInput = BIOS.util.defineFixedStepInput local defineVariableStepTumb = BIOS.util.defineVariableStepTumb local defineString = BIOS.util.defineString local defineRockerSwitch = BIOS.util.defineRockerSwitch local defineMultipositionSwitch = BIOS.util.defineMultipositionSwitch --NS430 added by Capt Zeen------------------------------------------------------------------------------ definePushButton("NS430_PWR-VOL_PUSH-SQ_POW", 257, 3001, 1, "NS430", "PWR-VOL_PUSH-SQ COM Power") defineRotary("NS430_PWR-VOL_PUSH-SQ_VOL", 257, 3002, 0, "NS430", "PWR-VOL_PUSH-SQ COM Volume") definePushButton("NS430_VOL_PUSH-ID_PUSH", 257, 3004, 3, "NS430", "VOL_PUSH-ID VLOC Push") defineRotary("NS430_VOL_PUSH-ID_VOL", 257, 3005, 2, "NS430", "VOL_PUSH-ID VLOC volume") defineRotary("NS430_BIG_LEFT_BTN", 257, 3007, 4, "NS430", "NS430_BIG_LEFT_BTN") definePushButton("NS430_SMALL_LEFT_BTN_PUSH", 257, 3009, 5, "NS430", "SMALL_LEFT_BTN Push") defineRotary("NS430_SMALL_LEFT_BTN_ROT", 257, 3010, 6, "NS430", "SMALL_LEFT_BTN rotate") definePushButton("NS430_COM_FLIP_FLOP", 257, 3012, 7, "NS430", "COM flip-flop") definePushButton("NS430_VLOC_FLIP_FLOP", 257, 3013, 8, "NS430", "VLOC flip-flop") definePushButton("NS430_CDI", 257, 3014, 9, "NS430", "CDI") definePushButton("NS430_OBS", 257, 3015, 10, "NS430", "OBS") definePushButton("NS430_MSG", 257, 3016, 11, "NS430", "MSG") definePushButton("NS430_FPL", 257, 3017, 12, "NS430", "FPL") definePushButton("NS430_PROC", 257, 3018, 13, "NS430", "PROC") definePushButton("NS430_RNG-UP", 257, 3019, 14, "NS430", "RNG-UP") definePushButton("NS430_RNG-DOWN", 257, 3020, 14, "NS430", "RNG-DOWN") definePushButton("NS430_DIRECT-TO", 257, 3021, 15, "NS430", "DIRECT-TO") definePushButton("NS430_MENU", 257, 3022, 16, "NS430", "MENU") definePushButton("NS430_CLR", 257, 3023, 17, "NS430", "CLR") definePushButton("NS430_ENT", 257, 3024, 18, "NS430", "ENT") defineRotary("NS430_BIG_RIGHT_BTN", 257, 3025, 19, "NS430", "BIG_RIGHT_BTN") definePushButton("NS430_SMALL_RIGHT_BTN_PUSH", 257, 3027, 20, "NS430", "SMALL_RIGHT_BTN Push") defineRotary("NS430_SMALL_RIGHT_BTN_ROT", 257, 3028, 21, "NS430", "SMALL_RIGHT_BTN rotate") definePushButton("NS430_PWR-VOL_PUSH-SQ_POW_STOP_ACTION", 257, 3030, 1, "NS430", "PWR-VOL_PUSH-SQ COM Power stop action command") definePushButton("NS430_VOL_PUSH-ID_PUSH_STOP_ACTION", 257, 3031, 3, "NS430", "VOL_PUSH-ID VLOC Push stop action command") definePushButton("NS430_SMALL_LEFT_BTN_PUSH_STOP_ACTION", 257, 3032, 5, "NS430", "SMALL_LEFT_BTN Push stop action command") definePushButton("NS430_COM_FLIP_FLOP_STOP_ACTION", 257, 3033, 7, "NS430", "COM flip-flop stop action command") definePushButton("NS430_VLOC_FLIP_FLOP_STOP_ACTION", 257, 3034, 8, "NS430", "VLOC flip-flop stop action command") definePushButton("NS430_CDI_STOP_ACTION", 257, 3035, 9, "NS430", "CDI stop action command") definePushButton("NS430_OBS_STOP_ACTION", 257, 3036, 10, "NS430", "OBS stop action command") definePushButton("NS430_MSG_STOP_ACTION", 257, 3037, 11, "NS430", "MSG stop action command") definePushButton("NS430_FPL_STOP_ACTION", 257, 3038, 12, "NS430", "FPL stop action command") definePushButton("NS430_PROC_STOP_ACTION", 257, 3039, 13, "NS430", "PROC stop action command") definePushButton("NS430_RNG-UP_STOP_ACTION", 257, 3040, 14, "NS430", "RNG-UP stop action command") definePushButton("NS430_RNG-DOWN_STOP_ACTION", 257, 3041, 14, "NS430", "RNG-DOWN stop action command") definePushButton("NS430_DIRECT-TO_STOP_ACTION", 257, 3042, 15, "NS430", "DIRECT-TO stop action command") definePushButton("NS430_MENU_STOP_ACTION", 257, 3043, 16, "NS430", "MENU stop action command") definePushButton("NS430_CLR_STOP_ACTION", 257, 3044, 17, "NS430", "CLR stop action command") definePushButton("NS430_ENT_STOP_ACTION", 257, 3045, 18, "NS430", "ENT stop action command") definePushButton("NS430_SMALL_RIGHT_BTN_PUSH_STOP_ACTION", 257, 3046, 20, "NS430", "SMALL_RIGHT_BTN Push stop action command") -- end of NS430 added by Capt Zeen---------------------------------------------------------------------- BIOS.protocol.endModule() the first line contains the module name and the base address (take care not to overlap with addresses from other modules). The second line lists all the modules you want to use with the NS430. Then you also have to include the module in BIOS.lua by adding: dofile(lfs.writedir()..[[scripts\dcs-bios\lib\NS430.lua]]) before dofile(lfs.writedir()..[[scripts\DCS-BIOS\BIOSConfig.lua]]) If your aircraft of choice is not in the AircraftList.lua, you will also have to add it there.

As long as you don't have to, lets say, clear an obstacle right in front of the LZ. At some point you're going to have to deal with hovering out of ground effect. But it's true that there's no point in making every landing a vertical descent from 200m.

I use a half of the rudder axis on my twcs throttle. To do that, set the axis to "slider" and give it a 50% deadzone. You may also have to invert it, I can't remember.

I have probably more hours in the Mi-8 than all the others combined, so... Mi-8 for me. I'm surprised so many others picked it as well over the cool and capable jets. There's a lot of us "truckers" out there.

Power isn't measured in units of frequency. The RWR in the video is the SPO-15 and while some Mi-24Ps have it, this one seems to have the older SPO-10: https://www.jetphotos.com/photo/7624573 BST hasn't told us much about their Mi-24, other than that it's a P. I hope we'll get a well equipped one, but I'm not hyping myself up just yet.

I know where the frequencies came from, but why did you name two of them "VHF FM" and "HF FM" when they're not FM frequencies? They're AM frequencies. You can't use the R-828 (FM only) radio set to talk to the ATC over any of the "VHF FM" frequencies. You need an AM set. Same goes for the HF frequencies which were introduced with the MiG-15bis. You can talk to ATC over those frequencies using the RSI-6 radio which is AM only.

I'm pretty sure all the ATC frequencies are AM only.

Thanks!

So the behavior in the Yak is incorrect?

What does the lever do? It controls the RPM governor. What does the pilot want when he moves it? To set the RPM. Thus - RPM lever. At idle/low throttle moving the lever forward (beyond the RPM the engine can achieve) will not change the RPM... nor the prop pitch! The prop pitch will be at the fine stop. As soon as you pull it back to the point where you are changing pitch with it you are also changing RPM. So if that argument makes it not the RPM lever, it also makes it not the prop pitch lever. I don't know what do you want to call it at this point ;).

Engine RPM lever is technically more correct cause that's what you're controlling with it - the change in prop pitch is just the "mean to an end". But calling it the prop pitch lever is really no worse than calling the engine control lever of a modern jet the throttle lever.

The L-39 is easy to start up but it is also quite challenging to fly as jets go. Dynamic stalls are vicious, the engine is slow to spool up and generally underpowered, landing is challenging due to bad forward visibility, taxiing requires finesse... not an easy aircraft to learn at all and with a limited pay off at the end. The combat capabilities are pretty token and there's barely any content (missions, campaigns) included in the package. And yet people keep recommending it as a first purchase to new player. It baffles me why... The purpose of the freebies is to let you get a feel for the variety and possibilities of DCS and the two planes we have now do a fine job. Keep in mind that SSM aircraft are and will continue to be a part of DCS, whether they are your thing or not. If there's anything missing from the free lineup, it's a helicopter. This is where DCS really shines compared to the competition and it's a shame they aren't showing it off. I like the original idea to allow people to join the crew of an aircraft they don't own. Would definitely give the Yak and the Alb more purpose.