CHPL

Know exactly what you mean. But are we spared? Most of the stupid things I did, I did out of arrogance. Especially when I was younger. Sometimes it scared the hell out of me, but it didn't save me from the next stupid thing.:music_whistling:

Take it easy guys :smilewink: It's all about passion :bash:, which makes it not easier at all. And there is always a big difference between theory and practice. I remember Frank Robinson (Founder of Robinson Helicopter) saying: " My biggest fault was to encourage my engineers to get their private helicopter license. After getting a helicopter pilot they would like to increase safety margins over the top." But in the end, we all like to have the most realistic simulation that is possible. :thumbup: :thumbup:

Right now "Take off from ramp" is the only option, even for helicopters. Not teste jet but maybe possible. First set a static object and then after 3 minutes ( option new in ME ) remove it and replace it with AI. There are lots of things quite natural for helicopters but actually not possible in DCS. Simply more things to do for the programmer, but unfortunately helicopters have not that high priority :cry:

Sometimes strange things happen. :noexpression: If everyone has the same experience, please let me know, so we can look into it. Mission 1, 2 and 3 are updated, but only in the 2.56 update if you have the beta installed also maybe you can copy the mission files from 2.56 to 2.55.

As a former R22 Flight Instructor I have something to say about this VRS myth. In my times we are required to "show" the student a VRS situation, to demonstrate how it feels and how to recover from it. Of cause at a safe altitude :smilewink:. But even close to max gross-weight with a tailwind, it wasn't that easy to get into that VRS situation. In fact, it requires a lot of intentional efforts to get into it. I am pretty sure that it is really unlikely for a small to medium size helicopter to get into VRS under normal circumstances. Of cause, there are some exceptions. If you do some kind of air work as a commercial pilot or a military pilot with less outside reference, or you need most of your concentration for your task and not being aware that other things getting out of control it may be possible but in my view still unlikely. But these are also no normal circumstances. Settling with power is the most likely reason for all these crashes, while VRS is a common excuse and diverts from the actual pilot error. Vibration at low-speed is a natural thing and coms from the transverse flow in the rotor system and is not automatically a sign of beginning VRS. Also, during hover and slow speeds, there is always VRS at the rotor tips to some small degree. So it is not a question of his existence, it is a questuíon how big the VRS gets and how much of the rotor disc is affected by the reduction of the angle of attack and the resulting loss of lift. I am sure any RL Pilot has his experiences with something similar to settling with power in different situations. I remember my transition from the Bell 206 to the Hughes 500. It was nearly impossible for me to assume the actual approach speed without the instruments. I was always much faster than I thought, but luckily, in the end, there was enough power and rotor efficiency available to stop in a hover. Especially in a PC simulator like DCS, where you have no feeling (body response) when it comes to acceleration or more important deceleration, VRS is nothing else as an excuse for the harder truth - Pilot error. And of cause VRS is this invisible suddenly hitting danger the hero pilot has to face on. :lol: If you a Mi-8 pilot? That is a different story :music_whistling: Heavy transport helicopters with huge rotors and a hell of a downwash are more often subject to VRS. But in the end, when it comes to a crash you can't blame VRS. Its still a pilot error. :doh:

Do you use 2.55 or 2.56 Are you talking about taking off at Tango/Bravo Checkpoint?

:helpsmilie: Seems to be a lack of understanding from my side :doh: Please tell me what the event handler is all about :book:

Sorry but that's not the case. Our campaign suffers due to several bugs with trigger actions or conditions. Also sunrise and sunset are for any reason earlier in 2.56 than in 2.55. At the moment most problems belong to AI Ground units. The appear but refuse to move when spawned on a bridge or on uneven ground. Not to forget troop transport is broken as well, which braces a lot of helicopter missions regardless of SP or MP. Right now we go through all missions to check out what problem brakes the mission first. Only after these problems solved we can move on check it again and hope no additional bug uppers later in the mission. For fast progress, we send actual reports and test missions to NinLine.

In 2.56 the sun rises about 20 to 25 minutes earlier than in 2.55. Did a passing planet hit the earth and I missed it?

Congratulation :thumbup: The problem in mission 3 is related to the damage model of the UH-1. If you catch enough bullets it counts your pilot out, even when it has no obvious effect in the game ( still flying) the trigger we set gets activated. So obviously you managed not to get hit so many times :thumbup::thumbup: This is also the way it should be. Avoiding to get shott down has always the priority :megalol:

Many thanks for the info. :thumbup: There are no ground or fewer units with late activation in that mission and The Units they are there have no influences on triggers. At the moment it seems most of the problems related to just one major problem in the core of DCS and we are optimistic ED will solve that soon. :smilewink:

Please refer to the following thread https://forums.eagle.ru/showthread.php?t=265726 The campaign itself runs fine in 2.55, but 2.56 has some issues. We hope ED will fix all the issues before moving the stable to 2.56. The problems are related to the mission editor are core features of DCS and for us, there is nearly no way to fix it. The only way, as we did in Mission 3, is deleting triggers and related ground units, but that is not the way we want to go because of its impact in the story and immersion, and ED has to fix the problems anyway. We also right now test all missions in 2.56 to identify issues and problems and report them with a reliable description and test miz to ED. At the moment we can say that ED is committed to solving all of the problems as fast as possible, taking them seriously and we are in close contact.

We deleted the pilot dead Trigger option in mission 3, which causes the actual problem and already send a new version to ED to update them in one of the coming Beta updates. This is the fastest solution to the problem and has no negative effect on the mission itself. Many thanks for your patience and assistance in solving the problem. :thumbup:

I rechecked the mission in 2.55 , and everything works fine. DCS is sometimes mentioning that your pilot is dead, but that's without any effect of the mission. So I report the bug in 2.56 to ED :director: Do you know that you can skip to mission 4 via the F10 Radio menu after the first half of the mission?

This is really at the very end of the mission and makes it all the more annoying. :(

Unfortunate there are many issues with 2.56 :cry: If you can play the campaign in 2.55 STABLE there you will have no issues. At the moment we go through all missions to identify problems and report them to ED, so they can fix that soon for 2.56. I will check mission 3 in 2.55 anyway just to be sure it is not am a mission issue. We open a new thread related to 2.56 issues where we inform you and all the others about the actual findings and missen status. https://forums.eagle.ru/showthread.php?t=265726 :book:

GOOD NEWS APRIL 16.2020 ALL ISSUES WITH 2.56 BETA SOLVED IN THE LAST CORE UPDATE !! :thumbup: :cheer3nc: :beer:

Sorry for your frustartaion. :cry: Do you use 2.56 Beta?

Thank you very much for your confidence in our work. :thumbup: We hope that all errors in the ME will be fixed quickly. Furthermore, we hope that ED appreciates the potential and the unique selling proposition of the ME and Campania more. There is no other flight simulation that can tell such movie tire stories.:thumbup:

Because of all issues related to broken waypoint action triggers, it is up to ED to fix them. We have to be patient, but I will inform everybody when it's done. :book:

I just checked the spam folder. No mail received. grizzly_dcs@outlook.de

d0ppler is right About the HSI. Unfortunate manny trigger Actions are broken in 2.56, so most of the missions may not playable in 2.56 right now. Please use the stable Version 2.55 there is etheriting working, and wy are not sure if ED may fix all the problems with 2.56 in the upcomming update. Usually not, when it Comes to Mission edditor issues.

So you made changes in the miz file? I am sure that is because of copyright protection. Don't do this :music_whistling: And tell nobody about it :smilewink: :lol: There may be an official version in the French language later this year. J'utilise DeepL.com pour la traduction. Gratuit et très bon. Oh Il y a déjà quelqu'un enregistré comme Tanuki44 sur DISCORD. Je pensais que c'était vous. Veuillez m'envoyer un courriel à grizzly_dcs@outlook.de et je vous enverrai les fichiers.

Do you use discord? There is already a group of French pilots translating. If yes please let me know and I will add you to the translator's group.

Concerning the Gazelle L issue with the Gunns not aligned to the crosshairs, I got a replay from Playshop. So they have already a fix for the problem, but they not sure if it will be released in time because testing by ED takes some time. :music_whistling: