Holton181

Does this mean that I am supposed to be able to request refueling/-loading with the version I have, or will you update the pads, or do I misunderstand you somehow?

Yes, with the cyclic perfectly centered this is possible due to a tiny deadzone hard-coded to the Gazelle (no, my controllers doesn't have any deadzone). This deadzone can unfortunately not be removed by us (but reduced with careful tweaks), making hovering unnecessarily harder, but not impossible. The deadzone is unfortunately also felt during cruise flight, killing some of the immersion. To me this deadzone is almost the only thing I have against the often criticized FM. Other than that it's quite nice to fly.

I suspected something like that. Guess the ATC works by different criteria.

Yes, and as mentioned, with the grass single pad the ground crew answered but not with the invisible and "H" (everything else identical). ATC answers with all three.

Thanks for this addon and for the updated version, Upuaut! I have a question though, about the different helipads available. Of course anyone with insight may answer. I was relay looking forward to be able to create more real life, civilian, temporary landing sights with the invisible pad, i.e. putting some read flags in a circle in the snow as the landing spot and placing the mandatory vehicles (not very civilian though) nearby. I was able to get the ATC to respond, but not the ground crew for refueling/ground power. I switched the invisible pad to the single grass one (only change I made), and now the ground crew responded. Again, switched to the "H", ground crew stopped responding. So obviously there are functional differences between available pads. Is there a reason for this (i.e. something prohibit some pads to have full functionalities)? I'm afraid there is nothing that can be done to enable full functionality for the invisible pad (and similar), or is it?

I'm pretty sure he refers to to the DCS UH-1H manual, not the real life one.......... dum di dum.......

No one having two (or more) versions installed to test this out even further? I have 1.5.7 and latest OB and even BS 1.0.2 installed, but not in a position to test myself for a while. But when you mentioned it, I do feel that the nose has to point to the left in trimmed flight (ball centered). If it's a new behavior I can't say though.

No worries, easy mistake to make, often done similar ones myself.

I realize I mixed 2 and 3 in my previous post, but does really the VHF FM radio work for the ATC?! I was pretty sure it was supposed to not work, and I even think I tested it long ago without success. Good to know that it might work.

As Frederf said, you should set the barometric altimeter to QFE, i.e. 0m while on ground before lift-off. Then the barometric altimeter and radar height will follow each other rather closely during your climb to 325m (as long as the ground is rather flat below you during that part of your flight). When you get above 300m radar height the HUD will stop showing radar height and instead show barometric altitude above your starting position (where you turned in QFE). The jump in reading on the HUD won't be that big. The jump to 600m in your start post indicates that you didn't set the barometric altimeter correctly to QFE. Edit: Snipped by Ramsay

Indeed! Intercom, 2 (VHF AM) and 3 (UHF) are the only ones used (for voice com) in DCS what I know of, the other three isn't (if I'm wrong I hope someone correct me, with some proof).

I know you are ;-)

WOW! How could I miss this!? UltraMFCD and Sgt_Baker are both back in business! Happy to see you! Locking forward to what you will bring to the (hopefully near) future!

https://forums.eagle.ru/showthread.php?t=220052 Pretty sure it should work for 2.5.6, haven't verified yet.

[emoji106]

No problem, just wanted to share some Swedish trivia. And now to something completely different...sort of... To connect to directionles velocity VS fonetiks and to some degree fast jets, during my evening shower, after my comment above, I realized how ironic the expression "Need for Speed" really is... Time to go to bed...

I am looking for a shrubbery...

Actually kinda funny when we got it explained, at least for me as a Swede. But just in case, and me being a bit of a wiseacre, in Swedish double consonants makes a preceding vowel short/fast ("two horses pull a wagon faster than one"), so the 'i' is pronounced much shorter than in 'vegan'. Like the 'i' in The Knights Who Say "Ni!" (not to be confused with The Knights who say "Ekke Ekke Ekke Ekke Ptang Zoo Boing!". Completely different guys)

To be fair, it's a rather stupid implementation to have this two step procedure for changing language. I can't see the point, and it's confusing. I guess it's a relic from old days before clickable cockpits (i.e. no need to understand what was written for the buttons/switches in the cockpit) and only a few avionics had translations. No need to feel dumb.

[emoji106]

Just a thought, when you got the gray screen, where did the small targeting circle on the HUD point (marking where the camera is pointing)? If it pointed above the horizon, i.e. on the sky, that would be the explanation. Pointing the Shkval up in the empty sky indeed makes the display gray.

Yes, I have experienced similar thingd in the past with other settings for other modules. There was a setting (don't remember which) for the Ka-50 that had to be toggled (unticked, restart DCS, reticked, restart DCS) after each update. Though it was long ago. One can not fully trust the settings being what they seem to be... Happy you got it working.

Thanks! Just needed the information to keep track of changes you did to keep the file up to date whenever ED make any changes to it. Will save a copy of the original most resent one, on which you based the most recent modded on, to be used for comparisons.

Thanks for the update Mustang! One question: In the original terrain.cfg.lua there are several instances of '.min' files that in your modded terrain.cfg.lua are the "same" files without the '.min' ending. Is this by purpose?

I think you also need to have the autopilot option enabled in the Special/UH-1H section of the settings.