Rongor

I can't find a comment in the manual confirming this as correct. While in one of the two Override modes, DMS right (assuming we have the FCR on the left MFD) is ignored, preventing switching between SMS and the HSD. DMS up, left and down are working normally. Switching pages on the non-FCR-MFD is still possible by navigating through the respective OSBs, yet naturally you won't be in the mood to hit some OSB when in a dogfight (override-situation), as we have HOTAS for stuff like this. If you switch to HSD by OSB, navigating back to SMS won't show the INV as an option in the stores main page. You still can select it via OSB 4.

Currently it can't be edited, regardless of within or outside aligning. Also opposite to the manual, the values don't have to be entered/acknowledged, regardless if STOR HDG or NORM alignment. Even Wags doesn't do it in the Cold start training mission. This is what the manual says: If anybody managed to edit the SALT, please tell us how. Also if you bother to ENTR all the three data lines in the DED, you can simply stop doing so. Alignment will complete to 10 just normal.

This is exactly what I wrote in point 2. It is, PNEU is the initial mode when starting up the F-16. Following the Cold start checklist beginning on page 103, there is no item telling me to switch it to ELEC. in ELEC mode, the values match, but still it's not possible to edit the DED SALT value by the ICP keypad as demanded on page 79

During NORM INS alignment on the ground, we have to verify LAT LON and the SALT, acknowledging present values for these shown in the DED. If necessary, we can edit the numbers with the ICP. 1. I am unable to edit the SALT. Whenever I enter numbers on the ICP, pressing ENTR simply returns the SALT value to the number shown before in the DED. Therefore I can only acknowledge but not edit the SALT number. 2. SALT value seems to be affected by the Altimeter setting. Turning the QNH knob on your Altimeter not only adjusts the Altimeter readout but also the SALT value in the DED. 3. SALT number is shown higher than the Altimeter. There is a mismatch of around 50-60 ft. You can't bring them both to the same value, ideally this would be the current ground elevations as shown in the F10 map All three described items: Why? and: Bug? 4. SALT value is showing correctly only after completing alignment by turning the INS knob to NAV.

I don't think you got what I was saying. Hind was given into early access in June. Now after several updates, we have it almost in release state, yet the manual didn't receive updates, so sadly despite all the additional implementations we still can read up how most of the stuff is working.

I mapped switching the Yaw channel on and off onto my HOTAS for this. To the question regarding realism... we don't know. After half a year, the Hind sadly is still basically at release state and the meager documentation given along doesn't explain most of stuff.

Well at least now you save 3 button positions

Oh, then it actually could have a use on a HOTAS. Hope you get these additional bindings implemented then.

is what i'd wish for any update for the Blackshark. It's very shallow right now and also unrealistic. Battery doesn't seem to drain, you can fly without any hydraulics left and you can safely RTB or even continuing attacking the enemy with the shark's behind being chopped off behind your seat (no tail, actually the most frequent visible damage I get)

interesting point. Something to be tested.

Multi-engined helicopters are often equipped with different sizes of feeder tanks. This is a kind of built-in life insurance for the most careless of pilots, who failed to manage their fuel correctly and eventually are even up to ignore the fuel warnings. The idea is to have the crew land within a specific amount of minutes after the low fuel warning (as will be defined in the checklist/AOM). If the crew still carries on, one tank will empty before the other, so the shutting down of one engine will be your last and final warning. The first engine shutting down would normally be the left engine (number 1) with the Blackshark, as it is fed from the front fuel tank, which has a capacity of 705 kg. The rear tank bears up to 745 kg, so you will have around 40 kg left on the right engine (number2) to bring the helo to an instant but safe landing. If the rear tank is empty first while the front is not, something has gone wrong. The applicable emergency action would be to open the crossfeed valve to keep both engines supplied from the front tank and keep an eye on the fuel meter to verify front tank fuel level isn't suddenly dropping as well. Consumption from front tank will increase now of course.

May I ask how this is disappointing? It's a dial on the rear auxiliary panel which you would only ever use when rearming with a different rocket type, so not that often. You do that before taking off. Of course it's your individual choice but why would you waste a 5 way switch on a HOTAS for something you won't ever need in flight and even very rarely when on ground? Left and right will turn the dial left and right as in the real thing. To map all 5 positions onto different button signals would be unrealistic and invite wrong settings if you unintentionally hit one of these during flight.

The RWR starts to deedle the moment a radar is put into the inner circle range. Especially on MP servers enemy AI radar can track you pointlessly for minutes and the RWR in the Hornet is totally annoying in this case, constantly and unbearably deedling at you. I have no idea how the designers of the RWR could come up with the idea to increase the pilots stress level so much by playing this deafening deedle tune in critical situations like these. Yeah I know I can turn it down but this defeats the whole RWR concept in some way. The "you are being tracked" RWR sounds in other aircraft are much more bearable and less occupying for your nerves. Actually the default RWR track warning sound is one of things I hate most in the Hornet.

Exactly, that is why I wrote Basically the region exists on everybody's LOMAC, FC and BS1 disk. Someone take this data and transfer it to the current beauty. No need for any actual accuracy. It's clear that ED can't do this.

terrain: 3rd party map of Crimea addon for Caucasus please (trailer-song: 'Football's coming home') module: MRTT multirole transport tanker, Boeing, Airbus or else, adjustable in rearm/refueling ground crew window for either transport or refueling role. Hours of endurance, player to player refueling and cargo transport for MP...

- Add an option to change frequencies for radios with preset channels in the rearm/refuel window (ground crew), would help immensely on sandbox MP servers - a unified generic roundel/bort number system for Multiplayer. multitude of standardized generic liveries and paintjobs which are selectable by everone. roundels for every country selectable as decals onto the selected livery. same for the bort number.

could we get an official response for this? The manual in the game files is outdated. The current RC6 manual doesn't mention BROU at all. As visible on the posted screenshot, the target is in 2 NM distance and delivering normal radar returns for a firing solution. Target data reads normally, as if there was no jamming situation. So even if BROU is telling about some jamming, why would it be displayed here when we obviously burnt through already? This could as well be a bug at this stage.

Playing in 2.7.8.16140 I am currently learning the front seat, doing everything by the book. On page 54, the official "Mi-24P Quick Start Manual EN.pdf" provided with the module tells us to turn on OBSERVE on the operator panel. Th L3 light should then start to blink and after 10-15 seconds the L4 light should illuminate. Then the ATGM sight doors are expected to be open. When I do that, the L3 light doesn't exactly blink, it's more like a flickering as if the light bulb has to be replaced. The L4 light never goes on. The sight doors though are opened. Function of weapons emplyoment was not affected

I can confirm this being an issue in 2.7.8.16140

Sometimes I think "need track replay" just comes in handy to not having to bother with the explained issue too soon. 2.7.8.16140 track attached. yawchannel.trk

The Ka-50 doesn't have to be a match. As these are helos, they are not exactly meant to go at each other. It's not like nobody will fly the Hind or any other helo anymore when the Apache comes out. We don't 'need' a Ka-52 to counter the Apache. It would be big fun to have a multicrew Ka-50 with IR/E/O. The Apache doesn't matter. Certainly, people will focus on the Apache some time. Yet whoever likes the Blackshark will still continue to fly it and stay interested in a dual seated Ka-50

correct, and in SRS it controls the R-800 volume

The SPU-9 isn't implemented in the DCS Blackshark. These guys at SRS decided to help us out with that shortcoming.

There you go: