rge75

Another one missing (DCS 1.5.7) is "Schalter Navigationsbeleuchtung - HELL" (Navigation Light - bright). The bright option is available for formation light (bright, dimm, brighter) but not for navigation light (only brighter, dimm available).

Is there a way to set more than one push-to-talk button for the Common PTT? The Puma control has a modifier, so my "push to talk" button on the cyclic might be "Button 1", "Button 11" or "Button 21" - depending on the switch position. So it's quite bad if you always have to set the switch to the right position to talk to other people. I was thinking of using Voice Attack to simply send Button 1 to SRS when Button 11 or 21 is pressed. However, since I already set up Voice Attack to send the commands to DCS, I can't send other commands to SRS. Edit: On the other hand, I just noticed that there are some more settings in VA - so maybe I can still use this as a workaround.

With the last version of your mission, I encountered a strange problem and I wonder if this is just on my PC or in general. I first thought it might be a mod, so I disabled them. However, I then noticed that this problem only occurs on this mission. I don't have this problem with the other Huey missions. As you can see, the pilot view is almost in the window by default and I have to zoom out a lot ot see the instruments. And co-pilot position is completely off... in the cargo room (see screenshots). Anybody else has this problem with this mission? And even more important: how to correct it?

Das gute ist, dass man den Puma unter dem Pult gar nicht sieht...Deine Frau würde es nie erfahren :D Aber ich denke, Du wirst mit Deiner Lösung sicher auch zufrieden sein. Leider bin ich auch kein Stromer und kann Dir bei Deinem Problem nicht weiterhelfen :(

Gute Idee und vom Layout schön umgesetzt. Einziger Nachteil, den ich bei den "deutschen Übersetzungen" sehe - wenn ich online fliege und alle Englisch sprechen, muss ich mir zwangsweise eh die englischen Bezeichnungen einprägen. Insofern wäre natürlich perfekt, wenn man ein Manual hätte, bei dem bei der Panelbeschreibung immer Deutsch und Englisch aufgeführt wäre. Wie aber andere schon gesagt haben; wenn man den Huey schon lange nicht mehr geflogen ist, dann ist es ganz praktisch in dem pdf kurz nachzuschlagen, wie man ihn aufstartet. Vor allem die Farbcodiernung der Konsolen empfinde ich als sehr hilfreich. Insofern - gerne mehr davon!

Im ersten Post hiess es, Geld spielt nicht so eine grosse Rolle...insofern, warum sich nicht einfach den Pro Flight Trainer Puma gönnen? Ich bin damit sehr zufrieden und möchte nicht mehr auf einen "normalen" Flightstick zurück. Wenn ich aber noch Jets fliegen würde, sähe es sicher anders aus. Nur geht es hier ja um einen Stick für den Huey ;-)

Oh yes, their harsh changes of speed and altitude didn't make it easy to follow them. Congratulation on finishing the campaign.

Yeah, I noticed the 4th position...I also forgot about that first. So when I switched it one more time, the Course Devitor Indicator started working but it didn't lead me to the ship. Assafm25 fixed this now though.

Hmm, good question about the mods. I can't remember if I had the Black Sea mod enabled or not. Either way, it's running smooth on 1.5.6 and not on 1.5.7 (and I was using the same mods on both versions at this time). Well, I anyway won't replay it until DCS 2.5 ;-) So hopefully it will run smooth there again.

I can feel with you! It simply needs patience. You could either edit the logbook.lua or you could simply load the mission and play it like a single player mission again. Just wondering - did you play it with 1.5.7 or 1.5.6? And if 1.5.7...didn't you have performance problems during sling load (well, maybe ED fixed it with the last couple of updates). Speaking of VRS crash...just happened to me today in the "Border Campaign". 2 simple sling loads and not payed attention for a very slight moment...I was able to recover, but the cargo was dammaged.

Well, I was using 40.00 as mentioned....but I'm pretty sure the mistake is somewhere on my side.

Thanks, I just had a look at the file in the mission editor to check out the location of the ship. I must have missed the ship in my attempt yesterday for whatever reasons. Maybe I made a mistake with the Homing. I'll give it a try later on again.

There's a wrong frequency for Fort 4 (I think it already was wrong in mission 10). The fort does not respond on 128.000 as said in the briefing and on the kneeboard. You have to set the radio to 128.500 to make the trigger work. Please change it to 128.000 to make it fit with the briefing/kneeboard (and also check the same issue for mission 10 - Escort). Thanks. I was lucky to figure it out. When I set it to 128.000, nothing happened but I anyway deployed the first cargo. When flying back, I wanted to change radio back to 142.500. So when I changed the last 3 digits (128.500) first, I suddenly heard Fort 4 talking to me....

Thanks, I finally had a look at it. It's really a lot better now with those space bar breaks!:clap_2: Personally I'm not a huge fan of the yellow "help signs" (they're a bit distracting to me) but they may be helpful for newbies. It would be perfect to be able to turn it on/off, but I'm probably asking for too much now. I encounterd one slight problem though - one of the markers didn't disapper (see screenshot). I of course made the same mistake again and chosed a task on the F10 menu instead of doing the "first flight". So when flying to the ship, I suddenly received an additional task (landing next to the trucks) :joystick: Maybe it would be nice to let the text NOT disappear until you set the ADF to 688? The text vanished a bit too early IMO. So you may miss that info if you didn't pay attention before the text vanished. Anyway, I'll have to do another run without setting the additional task first :music_whistling: Having the briefing now is also a nice addition. And a slight question...how far away is the ship for landing? I flew quite a while and the "Return Home" told me, I'm still on course....and there was nothing except blue dark sea around me for "hours" using time compression. Thus, I started to wonder if the ship really is that far in the sea (I did not have enough patience/time to fly further)? Last but not least - it was so refreshing to fly her again after spending hours and hours in the Mi-8. I completely forgot what a beauty she is. Edit: I forgot, maybe you should add the "set compass" to the checklist (maybe it's in there and I missed it?).

Did you contact the convoy over the F10 menu or did they start on their own? Or maybe it was a problem with the Hind AI. Once the convoy is moving, the commander should tell the Hind to recon the area in front of you (the message you received at Thiskanvili). I did not have any problem with the triggers in this mission and I think it was one of the more interesting missions of this campaign - at least when you play it for the first time. The replayability of this mission might be a bit low because...like you mentioned, the convoy is moving a turtle speed. So you're flying close to "hover" and you have to pay attention to not get into a vortex.

Well, I checked a video on youtube and some other guy obviously had the same problem. However, he simply continued without the Hinds and destoryed all the targets. So that's what I also did. With that said, I at least was able to finish the mission, but I'm sure that's not how it was intended. The briefing clearly says to rendez-vous with the Hind and this is not gonna happen.

I'm stuck in mission 9. After starting up the Mi-8, I fly direction 289 as mentioned. From WP1 I go to the meeting point at WP2. My radio is set to 142.500. However, nothing happens at WP2...no Mi-24 around nor arriving. There's also nothing in the radio menu. Do I miss something? If I continue w/o the Mi-24, of course also nothing will happen at the target area because I did no trigger the previous event. Furthermore, when I start the mission, I get the noise you often hear when a message appears - however, no message is being displayed. So maybe I miss an important information there?

Well, I encoutered another problem...probably simply related to the AI, but anyway annoying. When the two Hind should have landed, only one made it to the camp. The 2nd was "alive" but stuck in a mountain! See 2nd screenshots... you can see the dust from the air/blades. (I only took off to take the screenshots. During the mission I was waiting for several minutes with time compression, but nothing happened). I noticed the 2nd Hind when I switched through the helicopters by pressing F2 several times and when it simply showed the mountain. Therefore, there was no way for me to finish the mission and I'll have to redo it :cry_2: Edit: BTW, it seems like this mission has the map objects forced to "on"? In my options, I have "show map only" but I saw my helicopter as wel as all the friendly objects. IMO it shouldn't be forced on. Let the user decide what he wants to see on the map.

Well, I just completed it at the first run. However, you really need to make sure you pass WP2. Since I disabled all F10 map helps, I probably slightly missed WP2. I landed to get an idea where I am and then went straight west to the city. So I knew where I was and went to WP3 - nothing happend. Therefore, I decided to fly back south to WP2 - and then I received the message about contacting 102nd. When I did not see the flare at first time, I used the F10 menu again until I saw the rockets. For landing at the FARP, I just made sure I took the "original" platform (the one I took of in mission 5 and mission 6). I'm not sure if this would have been needed. Anyway, it gave me "Mission success". Just a short thing to correct - there's a missing translation (see screenshot) when you want to request 102nd. There's only the russian "Menu" text. Of course you can still read/understand it with imagination or the knowledge of the kyrilian letters... and since the rest is in English, Im' sure you can also change this one into English ;-) BTW, I can really recommend to disable the map features in the game options. This forces you to completely rely on your navigation. That was a game changer to me to use F10 map with ruler and markers. That made this night vision even more interesting.

What if the Wingman always gets shot down? And I mean completely shot down...he's not able to land, so there won't be no green smoke. He doesn't seem to be able to neutralize the targets. This happend twice now - and therefore it wasn't able to finish the mission. It's simply stuck if the wingman dies. Looks like I'll have to try the option "do not attack" in that case. Edit: yep, not letting him attack worked out fine.

Damn, I should have read through this thread before exiting the mission. I landed at the FARP and tried all 4 LZ on the north platform as well as one on the middle one. Then, I thought it probably doesn't give me a success because I did not trigger the "attack event" (the wingman flew away when I landed on Podovka). Looks like I'll have to fly it again in that case. However, there really should be an additional trigger which will give a message from the co-pilot saying "land on the south platform" - or it should be a success to land on any of the 3 platforms. This can't be that hard to add to the mission ;-) Just add two more zones and adjust the trigger. Anyway, flying the first mission with having everything turned off on the F10 map and relying on the full navigation was interesting (I only used Doppler as a backup solution but flew visual). That's why I missed the "small attack trigger" though - I slightly drifted to the right. Thanks for the hint about anti icing. I did not think of that anymore. However, this time I had no problems to land/start. Just make sure power doesn't go below 90%. Get into a hover. After that, don't touch the collective anymore. Only use cyclic to gain speed. The Mi-8 will then start to ascend slowly.

I thought there once was a thread about it or a download when somebody made it for the Huey...but I did not find it anymore (googled quite a bit). BTW, I agree with swiss_lipo that some texts vanished a bit too fast.

Thanks, looks like you put quite an effort in all those voice-overs! It's nice to have spoken language in the missions. I think sometimes it's a bit too fast though, especially when the instructor tells you to start up the engine (and especially if english is not your native language). Well, it was no problem to me since I knew how to start it up without the instructor. But following his commands was near impossible and therefore pointless. Maybe it would have been better to put triggers there. Sort of "Set AC phase and ESS Bus". Once both are set, the instructor can give the next set of commands. I liked the liveries of the planes as well as the traffic going on. Some triggers probably could be improved. The first task e.g. is to taxi to the runway and to fly to Batumi. However, I'm already able to chose F10 and a different task. Anyway, I'll give it another try next week (didn't have the time to go through the full practice). As a little side note (constructive critism) - I noticed a few typing mistakes. Also, I'd recommend to add text to the mission briefing. It doesn't have to be much, but having it plane empty feels a bit odd to me. Keep on going with your work. It's appreciated.

Let me put a short resume after having played 5 missions. When I read through this thread, my expectations were pretty low. However, I enjoyed the first 5 missions so far and it doesn't seem that buggy like mentioned in here. I agree that some triggers may be a bit sensitive - or they may not work when you don't do exactly what you're supposed to do so. It e.g. once happened that no bandits were on the roof in mission 2 when I didn't follow the road and went a different way. Also once the special forces did not disembark. Aside that, I did not have problems with the campaign so far. Well, in mission 5 I wasn't sure about that message about "out of ammo" and I thought I have to report when the enemy doesn't fire anymore. I was not amused when it told me "Mission failed". That's probably what people meant with "sometimes misleading". The missions may not be that complex, but there's nothing wrong with that. In fact it's refreshing to have those shorter flights. I don't always want to do 70 minutes missions. Somebody mentioned it's not a real campaign. Well, maybe there's no "big story" behind it and it's "just a bunch of missions" along the border. But again, there's nothing wrong with that. So far I like the variety of the missions. I do not regret the buy after having played 1/3 of the campaign. There are a few things you might miss after having played Oilfield. First, when you start up the Mi-8 - it feels so silent when you don't hear anybody saying "starting APU", "Revs increasing, temperature increasing". It would be a HUGE improvement if this would be implementend. It's no critism though because Border was released way before Oilfied. IMO it simply would add a lot to the immersion though. 2nd, it would be cool to have some of the maps from the briefing in the kneeboard. When you want to work with Doppler, you always have to hit the ESC key and to go to the briefing to see the distances/angles for the Doppler. This takes out a lot of flow. It has to be said that you can fly most missions w/o Doppler though because distances aren't that far and you can do visual flight. Another thing I miss - the frequencies picture is in kyrillian in the kneeboard. Not everyboy can read this. So again, it's hitting ESC and going to the briefing to see the english version. So maybe a solution like in Oilfield where you have both languages in the jpg could be the better solution. These are no game breakers, but adding those things could improve the overall experience. Like I mentioned before, I'm enjoying the campaign though. After having played Spring Tension and Oilfield, I was simply glad to get another 15 missions for the Hip. Edit: PS I like the skin of the Mi-8 in this campaign

In mission 5, when you land at the fort, you immediately get the message COMMANDER: The troops are on board. (see screenshot) It should be something like "Wait for the troops to be on board" because they're not on board yet. The trigger itself is ok because as soon as the troops really are on board, you'll get the 2nd message: CREW CHIEF: Commander, the troops are on board. COMMANDER: Taking off.