CHPL

You are absolutely right. The LZ is right at the mountain ridge. The safest and correct way is to land on the upslope side. Get contact with the front part of the skids and then settle down with the tail. So you have a nose up situation on the ground. Unfortunately, the AI in DCS refuses to do so I believe because of collision warning and only lands on the backside of the ridge with an unsafe nose-down condition. :pilotfly: When flying with your wingman it is always a good idea to stay to the left of him and slightly behind. Even during a landing or on the ground. This is a good way to keep always visual contact without the need for looking out of the side windows.

There are many things to do, and it is easy to miss something. As mentioned in the tread bevor. If your radio is switched on is also hard to see. But if you see airport actions this should be fine. On the Air to Air Radio below, you need either the correct frequency, or the preset 2, and you have to switch it on. I'm out of office over the weekend but I believe you have to switch the intercom select switch as well to "2". Do you set the Inverter switch in the overhead console to MAIN ON? This is one of the main triggers in any mission.:smilewink:

@Alpenwulf It is fine for me if you move me to the Gazzele L, so one of the guys waiting for a Huey may take part in my Huey.

Hey, we have extreme desync on the dedicated server. No Graphic on that machine. Everything else works fine but players aircraft warping through the seen. Windows Server Prozessor is by 20% and RAM at about 5 to 6 out of 15. Any ideas what may cause the phenomena. To mani Ai units in the game? Is the sync the first that breaks when the system is to week? It works fine when hosting from my windows 10 PC I am flying at the same time.

GOOD NEWS GOOD NEWS We got a message from ED, that the bugs fixed internally and the fix will be part of the next BETA update. :pilotfly:

The good news is. We get the information from ED that the bugs in mission 1 and 2 are internally fixed and the fixes are part of the next Beta update. The explosion in mission 1 is not a bug, you are just to close and the blast of the explosion on the ground blows you out of the sky. But actually, there is a bug - close at the end of the mission, as stated fixed soon :smilewink:

Many thanks for the description. I'm out of the office over the weekend so I can't check it but according to the timeframe, I would suggest it is related to the formation requirement. On the way to and from the Air Carrier, you are required to stay in close formation and at the same altitude as WOLF 1. If you do not you get first some advice but later on, the mission will fail by technical problems with your aircraft. This requirement ends shortly bevor the first bridge. You can avoid that requirement by: I am a little bit confused, about the explosion, we choose the main gearbox failure in the Missio Editor as a logical event for mission abortion. :noexpression:

I am out of the office but out of my memory: Stet the frequency to the channel told at Batumi Apron and the mission will work without any problem. We already fixed that issue internally, and it will be updated in a few weeks, to eliminate the confusion. But many thanks for the information. Al info even about smaller issues is appreciated. As well as any feedback to the campaign or single missions. Many thanks and always happy landings :pilotfly:

Hey just answered that question in a separate thread:smilewink: https://forums.eagle.ru/showpost.php?p=4269544&postcount=27

If you use The trigger list at the beginning of the thread? Be aware several devices numbers have changed. You find the actual list in your DCS Main folder C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\Uh-1H\Cockpit\Scripts File name = devices.LUA

It is possible to open the back doors separate: Using that in our WORLDS APART Campaign extensively. :pilotfly: Cockpit instrument 9 Comand 3035 for the left door and 3036 for the right. Values are 0,1 for open and 1,0 for closed. The front doors can be open only together. There are 2 Commands but with the same effect Cockpit instrument 12 Comand 3005 or 3006 Values are 0,1 for open and 1,0 for closed. Good Luck :smartass:

Avoid catching groundfire. Your pilot is some kind of bulletproof, but the damage model will state "Pilot dead" anyway and abord the mission if you get to many howls in your Huey :thumbup::pilotfly:

It's an already known bug in 2.56:cry: The HUMWWE (TAXI) doesn't move. Working fine in 2.55 but in 2.56 already some issues with ground unit behavior. ED is working on it! It may be possible to skip the mission over F-10 again, but personally, at the moment I would install the Stable only with the Caucasus map the Huey and the campaign. Most of the files already on your computer in 2.56 beta so it will not take that much time.

You do not suppose to follow WOLF 1 away from the station and even changing radio frequencies have no effect on the mission at that stage. If you in doubt? Please refer to the following video. If you use DISCORD you may reach us more likely on the Helicopter Pilot Meeting Point on DISCORD https://discord.gg/CXCA7rf You get all the assistance we can provide to make the campaign a challenging but first of all satisfying experience. :pilotfly:

I need more specific description of the occurrence, if possible. But from our few in mission 1 there are 2 possibilities for such an explosion, and it's NOT A BUG :smilewink: 1. When at the power station. The blast of the explosions at the station will take you out of the sky if you to close :cry: 2. Following the cars to the checkpoint. same reason. Both cars explode because of their dangerous cargo. If you too close or right over one of them, again the explosions will take you out of the sky. :smilewink: What is the actual bug status of the campaign? If you fly in the stable 2.55 there are no bugs for sure. There are only sometimes some issues with the AI in mission 2. During the cargo transport mission at the station for example: If you need much time for the task ( i guess 15 to 20 minutes) the AI WOLF 1 slide into the river and explodes. You may prevent that from happening when canceling the transport mission in time. Please refer to the mission documentation. At Tango Bravo Checkpoint, for some reason, the AI refuses to land ( make sure you keep sufficient distance during the approach. We already prevent Wolf 1 from sliding into the water by adapting the mission. We also moved the landing zone at Tango Bravo to reduce the possibility of AI resistance. As you can see in our updated video below we also made many other improvements to mission 2, especially more voice-overs and so on. THE ACTUAL PROBLEM WITH THE SERVICE UPDATE. The missions 1,2, and 3 right now only updated for the Beta 2,56 and some issues in 2.56 just break missions 1 and 2 right away. They work perfectly in 2.55 but you need 2.56 to download the missions. :cry: So if you have a Beta installation as well. It might be possible to download the Mission update in 2,56 beta coping the mission files for missions 1,2 and 3 and use the improvements and better immersion for 2.55. Of cause, this is unsatisfying and frustrating for all of us. :( BUT THE GOOD NEWS IS: ED confirmed yesterday that the issues are bugs related to ground unit behavior in 2.56, and will take care of it soon. We also have a meeting on Friday wit ED staff and we will try to get a campaign only update for the Stable 2.55. If it works out? I don't know. ATTENTION: There is still the possibility that ED is moving the Stable to 2.56 before the bugs are fixed. So please update only after reinsuring you abut the situation here in the Low-LevelHeaven Tread. Many thanks for your patience :thumbup: :thumbup: we also made many other improvements

After landing at Tango Bravo a HUMWWE is coming on the grass field isn't it?

In 2.56? The Huey Problem is fixed, but 10 minutes later it brigs a new bug with it. Glad to hear that it works out for you, but we are still working on the 2.56 issues. Any feedback is highly appreciated. :thumbup::thumbup:

It will take some time. ED still sees the problems as a mission issue. If they don't fix the problem in a short time we will change the missions to circle around the problem. Already thinking about ways to do so.

Hey dOppler Do you use DISCORD? Our Group Mission Server is coming soon and we test it today. 18.00 Zulu. If you are interested in participating in the test, please let me know. :thumbup: Best over DISCORD but still fine here in the Forum. https://discord.gg/CXCA7rf Here you find some information about the mission as well. Just go to the GROUP MISSION SERVER section "mission-descriptions".

normal is 90 minutes

Longways to go this time. It would be great to have 30 minutes more time for that task. Fling to each of the own LZ just once, and back for rearming already takes 90 minutes:music_whistling::pilotfly:

The miz file is missing this time :helpsmilie:

UH-1 / UGLY ANGEL / Grizzly

If you go back to 2.55 Stable save the Missions 1,2, and 3 first. just in case the may be replaced as well with the older ones. :smilewink: We asked ED already for a small mission update for the stable. So let us see what comes first. For us, it is also frustrating that all the work fo the update was useless in 2,56 until now. :cry:

No, the issues with not moving AI units still exist in 2.56. If you have 2.56 beta and 2.55 Stable installed you may copy the Mission files 1,2 and 3 from 2.56 into 2.55. Everything works fine in 2.55.