EvilBivol-1

I think all we need to know is contained in the feedback referenced here: http://forums.eagle.ru/showthread.php?p=1836842#post1836842

Although this may not be obvious, the training voiceover is actually a difficult issue to manage. Training missions are an evolving project, especially while the module is in development. So we need actors who are able to go back and re-record pieces of lessons that they had already recorded earlier or maybe record new ones. This makes it a difficult and expensive job to contract. Luckily we had a willing fan (and a good friend of mine) who volunteered for the instructor voices on the A-10C and P-51D. The sheer number of hours those projects required is no longer something he has available, at least not for free, so as a test run I did the UH-1 instructor voiceovers myself. Don't worry, I'm not offended. I find it highly irritating to hear my own voice, so I completely sympathize. :) Probably making it worse is that I had cut down and amplified my recordings in an attempt to get more of an "intercom" sound. For the final versions, I will probably use natural voice recordings and not mess with the audio settings, which is how we did the A-10C and P-51D lessons. We are working on a number of additional training lessons for the final Huey release. I am open to suggestions on how to improve the voiceover. If you think you may be a good candidate for the instructor voice or if you know somebody else, please let us know. Although we may contract this job out eventually, for now we are still relying on volunteers for our VO work. Keep in mind the amount of time and flexibility needed to record (and sometimes re-record) entire pages of material.

Try holding down the MDCD push button down for a good couple of seconds. There are a few cases where the triggers were unable to read the actual display output and depended on catching the press of the button itself. When done quickly, there may not be enough time for the triggers to catch the action.

We'll have some positive news on this front in the next update.

We just created a license transfer option through the website. More info coming in the next couple of days.

The ejection seats were not used. The pilots, although apparently injured with broken ribs in one case and spine in the other, got out of the helicopter themselves after the crash. However one of the ejection rockets fired off later due to heat from the fire. That was actually captured on video: UU7uCFRoQFU It seems like two of the lower rotor blades fired off post-crash as a result of the fire as well. It was one of the company's Ka-52 test airframes and company test pilots. According to current reports, the test flight had to do with testing the air conditioning system intended for the Ka-52K. So far it seems like they lost control on final approach, about 20-30 meters above ground, probably in or approaching a hover before final descent. The helicopter began to suddenly rotate and fall. Unknown if a mechanical problem was the cause or some kind of pilot error.

Thanks for the info. Yes, we did see this come up and have forwarded the error to the modeler. Actually we had substantial support from a number of "on location" Huey SMEs. A couple of examples that have been mentioned on the forums previously: http://forums.eagle.ru/showpost.php?p=1742176&postcount=28 http://forums.eagle.ru/showpost.php?p=1758568&postcount=43 Ultimately however unless the developers are themselves expert in the particular aircraft being modeled, which obviously isn't possible in every case, such errors may occur here and there. One of the benefits of the open beta, though, is just this situation where we have more time and room to find and fix them based on user feedback.

Hover and release. :)

Мы это уже сделали, то есть связались и согласие получили, но до результата еще есть дистанция.

Try a FARP in or around the airbase to make the helo come straight in for a landing on it. Also might want to have an extra turning point closer to home plate to control when the AI goes into approach mode.

http://www.digitalcombatsimulator.com/en/files/109/

My link above is for video recordings of the official training missions included in-game.

Bug. We're checking to see what's going on.

We need some confirmation and at least a mission with the problem. AI Hueys (wingmen and not) seems to be firing here so I cannot confirm it as bug at this point. Yes, I remember the spool up time question as well. Will check.

I completely agree with you and have discussed it with the team, but unfortunately it is not currently possible for us to assign axes to the mouse separately from the view control. This is a universal DCS limitation for the moment.

I believe this must be a local issue on your system now, probably due to some kind of mod conflict. AI Hueys are firing here and apparently for Flagrum as well.

Indeed we did in fact have a small miscommunication. Changelog now includes previously mentioned items again, plus a little mode detail for clarification on the Flex Sight changes.

Yes, should have mentioned it. Added now.

With TrackIR aiming OFF, you can control the Flex sight separately from the camera using the ; , . / keys. However it does looks like we have a "stuck" command issue at the moment. Investigating.

You can now rotate the flex sight using the ; , . / keys while leaving TrackIR to control the view camera. These Flex sight commands can currently be remapped or assigned in the UH-1H Gunner profile layer.

Это может быть глобальным багом. На Кутаиси тоже самое - ловится на высотах ниже маяка.

I believe there was also a trigger zone in the mission that may be causing this problem if you are not within it. We would need a track recording of your flight to be sure. You can save a track of a training mission flight by launching it from the mission editor instead of the training menu.

Very hard to diagnose what happened without a track to analyze.

AFAIK Russian runways are also marked according to rounded-off magnetic headings. However another question entirely is how often these numbers get repainted...