Frederf

It depends. There is a "hot mic" switch option which provides constant open communication on the intercom direct from pilot voice. There is also a PTT switch. In previous DCS versions you could open the intercom menu by pulling the HM switch out and it would pop up the intercom-based F1 menu. It doesn't anymore. Otherwise "\" represents just speaking normally. So with HM out and "\" you would simulate talk to ground crew over hot mic intercom. Technically if you had HM in and "\" to speak you shouldn't be heard by ground crew but in DCS it works both HM in and out. The MIC switch on the throttle, forward direction, can do VHF or INT PTT depending on rotary position. FM and HF positions shouldn't do anything. Any of the 4 rotary positions in DCS plus MIC switch forward will get you ground crew. The VHF position will be the "VHF AM" device, INT "Interphone" device, and FM/HF the blank/none device.

Outside of AGM-154A I don't know of any. I'm a bit confused by "the block 50" since that encompasses a lot of different airplanes, nations, and time.

The interphone connects the pilot to the radios. It's the "local streets" that transports voice around in the airplane. The radios are the "highways" that go outside. If the intercom breaks the radios are useless in the same way the highway is useless if transport across local roads is impossible. However communication via intercom is possible with everyone that's physically connected with it. This includes other crew, ground crew plugged in, and AAR boom operators.

The modeled airplane cannot employ Harpoon or JDAM.

Notice it says "TO BNGO" which in track's case is 2000 lbs. If I set fuel bingo to 0 pounds I get more time. Know that there's more to bingo than just the pilot-set "fuel bingo" value. There is also the "home bingo" warning which is based on fuel level at the selected home point (HMPT) being less than a fixed amount. The CRUS EDR page only displays the time to "fuel bingo" so "home bingo" may occur earlier.

F-16 with AGM-65L was not a thing.

JSOW has GPS. I've looked and ED's choice of what weapons to include and not appears perfectly accurate. The point of the simulation is to simulate the item as it is, not how you need it to be. Capability gaps are not a mistake

Your opinion and I disagree.

"Would create a conflict" so would such a thing happen in reality. Simulation is not about avoiding conflicts but simulating reality. Linked, sprung controls (cyclic) could be additive so that input would represent force, not displacement. Pilot and copilot apply 10 pounds of force in opposite directions, stick remains. Pilot applies 20 pounds then stick position is biased to his displacement input. Stick in a center results in a null input from that user. Linked, unsprung controls (collective) could be most recent command with a blending delay. Pilot could use cyclic with Independent controls (brakes) would just be a 4-input condition to an aircraft system. There's no issue. If the pilot and copilot humans have difficulty coordinating their inputs that's not an issue with the simulation. The "transfer of control" paradigm is not a good one relative to reality especially with the permission setups.

Middle of bomb pattern = aimpoint, true in all computed delivery methods. No delay for CCIP release. Well there are a few milliseconds due to the rack operation but the airplane knows that (plus custom adjustment since mechanisms vary) so the pipper represents this tiny machine delay into the future. The goal is for the absolute minimum amount of time between button press and bomb a way. The weapon consent button needs to be held for every bomb release so lifting early will halt the release sequence before completion.

The DCS -21 doesn't like -0.5 to +0.5g for any length of time regardless of throttle setting. You're cool at -0.6 or +0.6g tho.

The Ka-50 has such tables that are pulled from map data. Because the RSBN isn't from map data it's not like it would matter but you could get map identity data and pull up a pre-made table image for that map identity.

There are configs with 120s inboard of 9s, but most are the other way. I think it's some aero interaction with 3/9.

I was checking how the real airplane is and agreeing there is a bug. SMS OSB1 label should be: Blank in SMS OFF dispaly "STBY" in NAV or in INV with not zero stations selected [1] "S-J" in selective jettison "E-J" in emergency jettison "AAM" in AA master mode with missile selected [2] "GUN" in AA or AG master mode with gun selected [2] "MSL" in missile override mode [2] "DGFT" in dogfight override mode [2] "A-G" in AG master mode with not gun selected [2] *OSBs 16, 17, 18, 19, 3, 7, 8, 9, 10 and 20 for stations 1-9 and cannon respectively **Not in INV with any stations selected DCS behavior which seems not correct: OSB1 "NAV" label in NAV master mode should be "STBY" OSB4 blank label flashes reverse video when pressed in NAV, should not OSB4 reverse video "INV" label vanishes when SMS in MSL or DGFT mode, label should be "INV" in reverse video identical to AA and AG modes It's minor but in real airplane the white rectangle which highlights near the label to show pilot he has pressed the OSB is not aligned with the label text perfectly. It should be a little lower for OSB1 and 4 (pilot can see the flash below his finger). I know it's not attempted but when in INV it should be possible to highlight the 10 weapon stations and change or clear the inventory to other weapons. I hope this feature is added like A-10C and A-10C2. F16 SMS INV details.trk

Ya know, I forget. It might.

Checked, INV subpage of SMS should be accessible and its label displayed in all master modes except the jettisons and BIT. In NAV mode the INV subpage is automatically selected.

Airfield coalition must match group coalition (blue, blue). White or red won't work. It's possible for the airfield to be out of fuel (not likely) but they should say "negative" back to you in that case. Thing about "\" is that it can simply be your pilot voice speaking without any microphone. The canopy is thick and ground crew cannot hear you just speaking. You want to use the radio or intercom. There is a telephone that plugs into the side of the airplane so ground crew can communicate with the pilot but it takes battery bus no. 1 power. For intercom you need either the hot mic switch set or press either radio transmit button on the throttle (those radios don't have to be on, but it's the PTT for the intercom). Or you can simply open the canopy (engine might need to be off) so your voice can leave the cockpit.

They must not have done the math right for the fixed leg case.

I don't remember if DCS Viper has a specific default control set or it's the generic. First thing you should do is go to the axis section and clear category for every controller column or in your case your pedals if that's the issue. Basically DCS assigns roll to the X axis of the controller... every single one of them. This is also true of a bunch of other axes and buttons. This is obviously dumb and causes all sorts of problems. The exception to this generic binding is if there is a specific .diff.lua file for your specific controller, then it's as set in that non-generic file. DCS Viper comes with specific controller settings for 19 devices. This includes the Throttle and Joystick Warthog controllers, but not the pedals. The fix is simply to delete the assignments from your controller that you don't want. E.g. if Pedals "X" is bound to roll, highlight the box at the intersection of the "Roll" row and "Pedals" column and use the Clear button on the bottom. The "build number" is a unique five digit number on the splash logo, lower left corner or main menu, lower right corner after the version number. Updates are checked for automatically, but there is a way to manually prompt a check although I've rarely seen it needed. You'll know if an update is available. There are two branches, Release (normal install) and Open Beta. The OB branch is updated more frequently and then when the programmers are satisfied that it's good enough the stable branch. You can convert between the branches with a special command line which is a lot better than uninstalling/reinstalling everything. Currently my Open Beta branch is on 2.7.15.26783. Of course you can assign and adjust one or two things without having to reassign everything. Out of the hundreds of commands I probably only use 20-30. Make good use of the category filters, folded view and the list won't be so scary. Good luck, have fun, ask questions.

Yes, 3/9 constraint for PWII just like the A-10C. Bug.

The PB destination in the mission is in the middle of two ships 3nm apart. When both ships have been hit (dead) and then a PB HARM is launched between them, the PB missile steers toward one of the ships as if it's emitting. The PB missiles are attacking a dead non-emitting unit 1.5nm from the PB destination when the unit hasn't been emitting or alive since before the PB launches. FA18 PB track dead unit.trk

Often in nav (not AA or AG) the altitude reference will be more old school compared to attack modes. I don't know if the F-18 does that or not. Maybe F-18s don't do RVSM. Also you can usually look up the raw pressure alt data in a display from the air data computer somehow directly even if it's not the value on the HUD. Heck I wouldn't be surprised if Airbuses did all those adc corrections too.

The HUD is from ADC (CADC is F-16) and ADC gets its Kollsman setting from standby altimeter but not the altitude. Basically ADC calculates altitude from the air data probes, standby Kollsman, temperature, Mach, etc. and calculates a number to send to HUD. Standby is purely mechanical so it shows an old school value not subject to all the adjustments of the ADC and that's why it differs.

The "BSGT" is inhibited unless the missiles are currently point tracking. Make sure it's an AGM-65D or G model.